Tech Notes

As the requirement is to move new feature test cases to build acceptance suite, I think it is important to note, what benefits the build acceptance tests provide usually: ·          Fast feedback to developers, if there are issues in the checked-in code.  ·          Tester gets a working build to start with their activities ·          Application should be usable every time Now for feedback to be faster, following are few points that need to be considered before test cases being moved to build acceptance suite – o     The test cases must be / can be automated 100%, so that later no manual intervention is required. o     The test cases can be executed in less time (its relative term but then fast feedback is also the same) For testers to get a working build: o     The build should be install-able correctly, so installation related test cases o     Basic functionality (e.g. login, export etc.) of new features should be working, so that testers can verify additional

In any performance testing projects, following are commonly performed activities.  These are not the exhaustive list though but covers majority of them. Discovery Phase Identification of critical business scenarios Identification of frequency / workload distribution of known scenarios Finalizing network bandwidth and geo-location for workload distribution Assessment of performance testing tool for the assignment Finalization of performance testing goals and requirements Developing network topology for SUT (system under test) and load generation environment Identifying number of hardware and its configuration Identification of licensed software Design Phase Procurement of required hardware and software Setting up of SUT lab & verification Setting up of load generation lab & verification Performance test planning Preparation of test data being utilized in scripts Scripts designing Population of (production like) test data in the database

What inputs and data will cause application to perform the most processing? Which inputs might fool application’s error checking routines? Setting of complex preferences or visualization, example completely changing the default UI with additional plug-ins / gadgets available etc. Doing things which don’t make sense from end users perspective. Just do it because it is possible to do. Example – Buy expensive item and return immediately, register into the application and request for removing registration immediately. Do things which only few users would do.  Example, create realistically complicated documents, create very complex orders (selection order, # items etc) in shopping cart etc. Identify inputs that are stored and “follow” them around the software. Example – When an address is entered into the shopping site, where does it get displayed? Find features that touch that data and validates the functionality.  In a way, try to find life history of objects in the system, like

As per defined in wikipedia – “A software bug is the common term used to describe an error, flaw, mistake, failure, or fault in a computer program or system that produces an incorrect or unexpected result, or causes it to behave in unintended ways. Most bugs arise from mistakes and errors made by people in either a program's source code or its design, and a few are caused by compilers producing incorrect code. Reports detailing bugs in a program are commonly known as bug reports, fault reports, problem reports, trouble reports, change requests, and so forth.” There might be many fields (information) need to be filled while reporting a bug.  The number of fields, mandatory fields, optional fields etc. differs from team to team.  But few bare minimum fields that are required during reporting a bug in almost all teams are as follows: Title Description Steps to Repro Expectation Severity / Priority Most of the time, testers go and try to provide these information in hurry, with

Catching or preventing errors at client side improve the performance of the application, firstly by providing the quick feedback to users and secondly by reducing the load on server by eliminating unnecessary requests.  The application should be developed by taking this into the consideration.  It doesn’t mean that the validation for input should happen only at client side, the server code should be able to handle incorrect input data as well.  Usually at client side, message shown to end user should be more meaningful whereas server should not behave incorrectly or crash due to negative set of input data. While designing the form of an application, it should be first considered to provide input controls that are smart enough to restrict users to submit only required or correct data, e.g. Calendar control, Combo Box etc.  Secondly, it can have few business rules validation logic at client end also if possible, e.g. Age and Insurance premium requirement validation. Validating

For latest article on this topic, please check here 1.          Project Context   What is the system needed for? (Brief description of project) Who are the end users of the system? Do you have any existing performance concerns? When would you like to start the assignment?  When would you like to finish it? Domain (use þ ) o Retail                        o Insurance                              o Healthcare o Avionics                    o Real time/Embedded             o Enterprise E-Biz o Games                      o Others (Please specify: ____________________) o BFSI Technical (use þ ) Type of application o Client Server                         o Web Application                    o Multimedia                o Consumer Electronics             o Others (Please specify: ____________________) Architecture of the system (2/3 tiers