Procedure to execute test cases : 

Customer gives requirements – developers are developing the features looking at the requirements. The test lead gives a list of features for each TE to write test cases and execute them. The TEs first understand the product by looking at the requirements and then start writing test cases.

Now, let us consider that TE1 has been given loans feature, TE2 has been given insurance feature and TE3 has been given Amount Transfer feature. Now, all these TEs start writing test cases for their respective features. After the test cases have been written, reviewed and approved – they are stored in the test case repository.

Now, by this time – developers have given the 1^st build – in 1^st build, features which have been developed are – Personal loans(half), life insurance(half) and Amount balance. Whenever developer gives builds – create another folder(Tiger_Test Execution Result) – create in that folder B01(1^st build) – copy,paste all test cases from QA – Build1 comes – remove all test cases for the features which are not yet developed – keep only those test cases for which the features have been developed i.e, the relevant test cases – then do smoke testing and all other testing and then fill in the Status columns of the Test Cases – bugs are caught and sent to the development team.

After this, developers give the 2^nd build B02 – here, the features developed are – complete personal loan, complete amount transfer and also complete life insurance – create a folder named B02 – copy, paste the entire test cases in that folder – and the same method as in B01 follows.

Same procedure follows all Builds. Thus we have all the results and can check the results for all the builds.

Build comes in – execute all relevant test cases – by the end of the cycle, summary report must be filled. This summary report is known as Test Execution Report / Test Summary Report.

Test Lead prepares this report. The TE sends the individual features which he has tested and tells how many he has executed and all that statistics.

The Test Lead then sends the report to,

·         Test Manager

·         Development Team

·         Management

·     Customer (depends on whether the project is a ‘fixed bid’ or ‘time & material bid’.

If it is a ‘time and material’ bid, then the test execution report must be sent to the customer as well.

The development team needs,

·         A list of test cases that are failed

·         Each developer needs a list of test cases which are failed for his features.

In each sheet is a list of test case names and everything.

The developer knows only the test case name. then he directly goes to the test case through a link or directly and then sees which test case is failed.

The Test Execution Report is stored in the B01 (respective builds) outside all folders.

For compatibility testing, the Test Execution Report looks something like this,

Again, we can do compatibility testing for browsers on various platforms,