Effective Test Cases & Introduction to Hexawise
Download as PPTX, PDF0 likes626 views
This document discusses test cases and the Hexawise test design tool. It defines a test case as a set of test inputs, execution conditions and expected results. Effective test cases have short, descriptive titles; correspond to requirements; and support maintainability. Hexawise allows testing teams to visualize coverage and optimize tests to be varied, minimize repetition and maximize coverage with fewer tests. It is used to select test conditions, document scripts, and improve efficiency. Hexawise generates tests that cover all pairs and triples of parameter values to find defects.
Effective Test Cases & Introduction to Hexawise
- 1. Effective Test Cases & Introduction to Hexawise By Nilenth Selvaraja
- 2. What is aTest Case? IEEE Standard 610 (1990) defines test case as follows: “A set of test inputs, execution conditions, and expected results developed for a particular objective, such as to exercise a particular program path or to verify compliance with a specific requirement.” Also (IEEE Standard 829-1983) defines it as “ Documentation specifying inputs, predicted results, and a set of execution conditions for a test item.” Ron Patton (2001, p. 65) “Test cases are the specific inputs that you’ll try and the procedures that you’ll follow when you test the software.”
- 3. Characteristics of EffectiveTest Cases • Title is short and descriptive. • Test case corresponds with the requirements. • Preconditions, steps and expected results are as transparent as possible. • Test case supports maintaining, update and can be re-used in the future. Most Important of all • Covering the most area of testing with less number of test cases.
- 4. Factors affecting test-case effectiveness
- 5. How to correct factors effecting test case effectiveness • Verify completeness of test specifications which can be done by revisiting and revising functional specifications, which results in revising test case specifications. • Verify coverage of test-cases by the use of traceability matrix to meet coverage needs of the project – ensures that test cases meet business rule. • Understand reasons for missed defects & training testers on proper way to execute tests and verifying test results. • Using tools that are helpful to cover a maximum area with less test cases.
- 7. What is Hexawise? Some of the most challenging questions testing teams are asked include: • Are we testing enough? • Are we testing too much? • What is the level of testing coverage these tests achieve? • What if we get extremely pressed for time…What level of coverage could we achieve in half as many tests as we have planned? Hexawise is a test designing tool which allows you to visualize testing coverage more precisely.
- 8. Why use Hexawise? • Hexawise is mainly used to select test conditions and document test scripts. • Hexawise also improves test execution efficiency and effectiveness.The tests you generate with Hexawise are more powerful than the tests you would select by hand. • Tests generated using Hexawise are optimized to: -Be varied as possible. -Minimize wasteful repetition. -Maximize test coverage in a manageable number of tests.
- 9. DEMO • Sign up, Log in & creating a new plan • Marking valid and invalid pairs • Create tests • Analyze tests feature • Export tests • Auto Script feature • Copy & Share Plans
- 11. Each of the end points on this mind map (like “Fast” and “Spin”) are parameter values.
- 12. In Hexawise it’s represented this way
- 13. What is 2 way interactions? When you click on the “Create Tests” button Hexawise generates a set of 2-way tests that contains every single pair of those test parameter values in at least one of the tests.
- 14. Every single pair of parameter values appears together in at least one of these six test cases:
- 16. It is an extremely efficient way to find defects given that: • Studies show that 84% of defects in production could have been found by testing for every pair of parameter values and • 2-way coverage can be achieved in a relatively small number of tests.
- 17. But what about coverage of combinations involving 3 or more parameter values? • Sometimes, a specific combination of 3 values will be included in your set of 2-way tests. • Other times, combinations of 3 values will not be included in your set of tests. Let’s look at a few examples.
- 19. These 3-way tests contain at least one test for every triple.
- 20. Studies show that 95% of defects in production could have been found by testing using 3-way coverage.
- 21. THANK YOU!