You can’t test a program completely Possible inputs too large to test Too many possible paths User interface issues
You can’t test the program’s response to everything You’d have to test all valid input You’d have to test all invalid input You’d have to test all edited input You’d have to test all variations on input timing
Testverktyg Test viewer Test manager Test results
WIT Work items Bug –State –Triage –Assignment –Details –Cycle of life
About the Tester The tester’s main goal is to discover and communicate problems with the product that could adversely impact its value. The tester must understand the context for the project and help others to make informed decisions based on this context. A key goal for the tester is to find and report the significant bugs in the product by testing the product. Once a bug is found, it is also the tester’s job to accurately communicate its impact and describe any workaround solutions that could lessen its impact. The tester makes bug descriptions and steps for recreating the bugs easy to understand and follow. The tester participates with the entire team in setting the quality standards for the product. The purpose of testing is to prove that known functions work correctly and to discover new product issues.
1-Define Test Approach Determine the project context. Determine the test mission. Assess possible testing techniques. Define the test metrics.
2-Write Validation Tests Identify the test area and environment. Identify test case flow details. Write the test cases.
3-Select and Run a Test Case Determine which test to execute. Identify the test configuration. Get the build. Execute the test. Analyze the test results. Close the work item.