lecture 8 Flashcards
testing
the process of examining a component, subsystem, or system to determine its operational characteristics and whether it contains any defects
test case
a formal description which contains the starting state, then the system goes through different events in which the response to each event should match the predicted responses or ending state
characteristics of a test case
- it is defined based on functional and non-functional requirements
- must test all normal and exception situations
test data
a set of starting states and events that are used to a test a module, group of modules or system
unit test
testing of an individual method, class, or component before integrating it with other softwares
integration test
testing of a group of methods, classes or components to see how they behave together
usability test
testing to determine whether a method, class, subsystem, or system meets user requirements
why is usability testing required
because the test involves functional and non-functional requirements
how are functional requirements evaluated
use case by use case
system test
an integration test of the entire system or subsystem
characteristics of system testing
- it is preformed regularly
- can be performed after each iteration
build and smoke test
a system test that is performed daily or several times a week
performance/stress test
a type of integration and usability test that determines whether the system or subsystem can meet the time-based performance criteria
response time
the desired or maximum allowable time limit for software response to a query or update
throughput
the desired or minimum number of queries and transactions that must be processed per a certain period of time