| || |
Test Case / Test Data for System testing, Integration testing and User Acceptance tes
Do we need to prepare separate test cases and test data for System testing, Integration testing and User Acceptance Testing. If yes, do we have template for
1) Test Case and Test Data -System Testing
2) Test Case and Test Data - Integration Testing
3) Test Case and Test Data - User Acceptance Testing
Otherwise, I request you send sample test cases and test data for all testing.
Re: Test Case / Test Data for System testing, Integration testing and User Acceptance tes
If you are a tester for one of many systems that will be integrated, then the answer is probably yes - you will need three seperate test plans and sets of test data.
For example, let's say you are in charge of testing the order fulfillment system for a company. This software might get orders from the order entry system. Then it would create a list of items that needed to be in the order, the location of the item in the warehouse, the shipping method or delivery date, and the shipping address. Then the fulfillment system might notify the order entry system and/or billing systems upon shipment. It would also integrate with the inventory system to properly reduce quantities of items.
In this case, for system testing, you will have a set of orders fed into your system. However, since you are simply testing your system, you will need to simulate the order entry system on the front end and make sure that all downstream interfaces are turned off on the back end. Later, during integration test, the order entry system might create orders and send them to your system. You would test your system and then pass on the order to other systems. Finally, during user acceptance test, the users would probably want to test everything, creating their own orders, and yet another set of test data.
The test plans would also be different as the emphasis or purpose of the test is different in each case. During system testing,a thorough test should be performed of all pertinent functionality in thesystem requirements. During integration testing, you may only look at major functionality and each unique interface (communication or transaction) with the other systems. During user acceptance testing, the test might be even less detailed, as the users might simply need to verify the business requirements, and not the system requirements.