skill category 7 Flashcards
Test conditions
- describe the specific functional capability, structural design, consideration, features, and validation checks which needs to be validated
- System specs is the primary source for test conditions
Where can test conditions be derived from?
- specifications decomposition
- population analysis
- test transactions
- Business process Analysis
- Structural analysis
Test transaction types
-field record -file -relationship -error -use (outputs) -search -match/merge -stress -control -procedures -attributes -states
what does a test condition indicate?
What to test
Text conditions can only be to ride from requirements?
false
Population analysis
- analyze prod data to identify, independent from the specs, the types in frequency of data that the system will have to process/produce
- this verifies that the specs can handle types and frequency of actual data and can be used to create validation test
Types of population analysis
- files/database/table population
- screen population
- Field/data element population
Structural analysis
- technique used by developers to define unit test cases
- involves path and condition coverage
- benefit – find effects not obvious from blackbox or external perspectives
- con: can’t find defects in software’s fitness for use in a user environment
Use case
- A technique for capturing a functional requirements of systems through the interaction between an actor and they system
- create it as part of requirements definition are via JAD
- A description of how a user uses the system being designed to perform a given task
System boundary diagram
- depicts the interfaces between the software under test and the individuals, systems, and other interfaces
- purpose is to establish the scope of the system and to identify the actors that need to be developed
- each boundary, an actor must be identified
Actors
an individual group or entity outside the system
-May include other software systems, hardware components, or other entities
Primary actor
Wanna have a girl which requires the assistance of the system
Secondary actor
One from which the system requires assistance
use case fields (format)
-unique identifier and name summary description -frequency/iteration number -status, actors, trigger -Basic and alternate course of events -pre-and post conditions -Business rules and assumptions -Notes in author, action and date
Happy path
follows a single flow uninterrupted by errors or exceptions from beginning to end
Sad part
Hey path through the app which does not arrive at the desired result
Alternate path
additional testable conditions are derived from the exceptions in alternative course of the use case
Why should we use “use cases”?
to address the effects of incomplete, incorrect, and missing test cases
-helps with communication between customer, developers, testers, and other project people
Preconditions
A list of conditions which must be met before the use case can be properly executed
Post conditions
A list of conditions which will be true after the use case finished successfully