Please enable JavaScript.
Coggle requires JavaScript to display documents.
2 .2 TEST LEVELS (2.2.4 Acceptance testing (The acceptance test should…
2 .2 TEST LEVELS
2.2.4 Acceptance testing
-
is most often the responsibility of the user or customer, although other stakeholders may be involved as well.
The goal of acceptance testing is to establish confidence in the system, part of the system or specific non-functional characteristics, e.g. usability, of the system.
is most often focused on a validation type of testing, whereby we are trying to determine whether the system is fit for purpose.
-
-
Within the acceptance test for a business-supporting system, two main test types can be distinguished
user acceptance test focuses mainly on the functionality thereby validating the fitness-for-use of the system by the business user
-
Other types of acceptance testing that exist are contract acceptance testing and compliance acceptance testing.
Contract acceptance testing is performed against a contract's acceptance criteria for producing custom-developed software.
Compliance acceptance testing or regulation acceptance testing is performed against the regulations which must be adhered to, such as governmental, legal or safety regulations.
If the system has been developed for the mass market then testing it for individual users or customers is not practical or even possible in some cases.
-
-
2.2.1 Component testing
also known as unit, module and program testing, searches
for defects in, and verifies the functioning of software that are separately testable.
may be done in isolation from the rest of the system depending on the context of the development life cycle and the system.
Most often stubs and drivers are used to replace the missing software and simulate the interface between the software components in a simple manner
may include testing of functionality and specific nonfunctional characteristics such as resource-behavior, performance or robustness testing, as well as structural testing
One approach in component testing, used in Extreme Programming (XP), is to prepare and automate test cases before coding.
2.2.3 System testing
is concerned with the behavior of the whole system/product as defined by the scope of a development project or product.
is most often the final test on behalf of development to verify that the system to be delivered meets the specification and its purpose may be to find as many defects as possible.
-
requires a controlled test environment with regard to, amongst other things, control of the software versions, testware and the test data
The test environment should correspond to the final target or production environment as much as possible in order to minimize the risk of environment specific failures not being found by testing.