tests the minimal software component, or module. Each unit (basic component) of the software is tested to verify that the detailed design for the unit has been correctly implemented. In an Object-oriented environment, this is usually at the class level, and the minimal unit tests include the constructors and destructors.
exposes defects in the interfaces and interaction between integrated components (modules). Progressively larger groups of tested software components corresponding to elements of the architectural design are integrated and tested until the software works as a system.
tests at any level (class, module, interface, or system) for proper functionality as defined in the specification.
tests a completely integrated system to verify that it meets its requirements.
verifies that a system is integrated to any external or third party systems defined in the system requirements.
validates whether the quality of service (sometimes called Non-functional requirements) parameters defined at the requirements stage is met by the final product.
can be conducted by the end-user, customer, or client to validate whether or not to accept the product. Acceptance testing may be performed as part of the hand-off process between any two phases of development.
But in my company, we simplify level of testing:
- Unit Testing
- Functional Testing
- System Integration Testing (SIT)
- User Acceptance Testing (UAT)
1 komentar:
Is it same between Level of testing and V-Model? Are they have something in common?
Post a Comment