Test Design Technics

Many people test and write test cases, but not many people use special techniques for test design. Gradually, gaining experience, they realize that continually make the same job, verifiable specific rules. And then they find that all these rules have already been described.

We offer you a brief description of the most common techniques of test design:

  • Equivalent Separation (Equivalence Partitioning - EP). As an example, you have a range of values from 1 to 10, you must choose one correct value inside the interval, say, 5, and one incorrect value outside the interval - 0.
  • Analysis of the boundary values (Boundary Value Analysis - BVA). If we take the example above, as the values for a positive test, we choose the minimum and maximum limits (1 and 10), and values greater than and less boundaries (0 and 11). Analysis of the boundary values can be applied to fields, records, files, or any kind of entities have limitations.
  • Cause / effect (Cause / Effect - CE). This is usually input combinations of conditions (causes) for the response of the system (investigation). For example, you check to add the client using a screen form. To do this you will need to enter several fields, such as "Name", "Address", "phone number" and then click "Add" - this "reason". After clicking the Add button, the system adds the client to the database and displays its number on the screen - it’s "investigation".
  • Prediction error (Error Guessing - EG). This is when the test analyst uses his knowledge of and ability to interpret specifications on the subject in order to "guess" at what input conditions, the system can fail. For example, the specification says: "The user must enter the code." Test Analyst will think: "What if I do not bring the code?", "What if I enter the wrong code, ‘and so on. This is the prediction error.
  • Exhaustive testing (Exhaustive Testing - ET) - is an extreme case. Within this technique, you should check all possible combinations of input values, and, in principle, it should find all the problems. In practice, this method is not possible because of the huge amount of input values.


You would..
Share
Related Documents
  1. Test Case Design for Website File Uploading (1818)
  2. Test Design technique (956)
  3. Advanced Software Test Design Techniques Use Cases (430)
  4. How to Design Test Cases (3104)
  5. TEST CASE DESIGN (3625)
  6. ISTQB : Test design Techiques (1195)
  7. Test Design Document - Template (3115)
  8. Test automation using specific test script language (2050)
  9. Test Design Specification (1494)
  10. Test Design Specification (2297)
  11. Test Design Template - by IIST (1712)
  12. Test Case Design - ppt file (6811)
  13. Test Design Specification (1599)
  14. Test Design Specification (774)
  15. How Do I: Get Started with Test Cases in Visual Studio Test Professional 2010? (1522)
  16. Test Design Template (642)
  17. Improving Software Quality with Microsoft Test Manager, Test Professional, Visual Studio and TFS (644)
  18. Automated Test Case Writing - What's new for Microsoft Test Manager (482)
  19. Test Design Specification Template (3438)
  20. Test Requirements Traceability Matrix (2854)

Written by

Mathi,

Testing executive