350 SOFTWARE TESTING: Principles, T

350 SOFTWARE TESTING: Principles, Techniques and roots

• Test manager shall install the application and conduct installation testing, smoke testing and sanity testing, Installation may not be required for few applications.

For complete testing Of each iteration, the following cycle is followed.
• Application is installed With all prerequisites. If installation is not required, this Step Can be omitted. • Test cases are executed as per sequence defined.
• Test log is updated with actual results.
• Defects are added in defect database.

• Test Design Test designing is a very important pan of testing which can affect the test plan and the application risk level to a considerable extent. Test designing, if done properly, can help development team n identification Of defects early in life cycle and fixing them, as and When they occur, Test design includes he following.

• What types Of tests are to be conducted while executing a test plan? Different tests may be allocated to different iterations of testing. Generally functional testing is done first followed by UI testing and other special testing.
• What stages Of testing is required during software development life cycle? It may talk about testing at unit, integration, interface and system level.
• Examples of stages are given below.
• Unit testing at unit level
• Integration testing when many units come together
• System testing when entire system is ready
• performance testing
• Usability testing

It also defines how the test scenario and test cases would be designed.

• Test Data Definition Test data definition is also considered as a subset of test design by some people. Test data is defined by testers from unit testing upto system testing and acceptance testing, if required. Acceptance testing may use customer supplied data. Test data is very important for the success of black box testing. If selected properly, it can reduce the risks to the final users. There are various techniques applied for defining test data. Some of these techniques are.

• Equivalence partitioning
• Boundary value analysis
• State transition
• Error guessing

• Roles and Responsibilities Test plan explains the roles and responsibilities of individuals involved in testing process. It includes activities to be done by stakeholders of the project. Roles and responsibilities define who is responsible for which activity at each stage of testing. It is good practice to generate responsibility matrix with people involved in doing different activities and representing different positions in columns while activity list is along each row. Table 14.4 represents a typical distribution of roles and responsibilities for people concerned with testing. It may change from project to project/organisation to organisation/customer to customer.