Inscrivez-vous ou connectez-vous pour rejoindre votre communauté professionnelle.
Test cases are also created to prove that the software can handle certain business scenarios. You can think a scenario consists of a set of business requirements put together to generate a different outcome. It is recommended that each scenario should have a separate test case to avoid confusion and better way of analyzing business risk(s).
In Requirement Driven Testing, the following guidelines can be used when creating test cases for scenarios:
1.Who performs day-to-day business activities and how they interact with the system?2.Restrictions on business activities;3.Changes on the existing business requirements;4.Changes on the existing technology or infrastructure .. and so on.
Writing test cases is a good opportunity to review the existing business requirements and scenarios. After all software testing is about using your imagination and creativity how users interact with the system being developed.
CATEGORIES OF TEST DESIGN TECHNIQUES:
1) Specification-based (black-box) testing techniques:
These are also known as 'black-box' or input/output-driven testing techniques because they view the software as a black-box with inputs and outputs, but they have no knowledge of how the system or Component is structured inside the box. In essence, the tester is concentrating on what the software does, not how it does it.
2) Structure-based (white-box) testing techniquesStructure-based testing techniques use the internal structure of the software to derive test cases. They are commonly called 'white-box' or 'glass-box' techniques
3) Experience-based testing techniquesIn experience-based techniques, people's knowledge, skills and background are a prime contributor to the test conditions and test cases. The experience of both technical and business people is important.
Where to apply the different categories of techniques:
Specification-based techniques are appropriate at all levels of testing (component testing through to acceptance testing) where a specification exists.
Structure-based techniques can also be used at all levels of testing. Developers use structure-based techniques in component testing and component integration testing. Structure-based techniques are also used in system and acceptance testing, but the structures are different.
Experience-based techniques are used to complement specification-based and structure-based techniques, and are also used when there is no specification, or if the specification is inadequate or out of date.
This may be the only type of technique used for low-risk systems, but this approach may be particularly useful under extreme time pressure - in fact this is one of the factors leading to exploratory testing.
Hope this answer clarified your question... If not please let me know..
