Fichas
Sin título
Fichas del conjunto (13)
- 1CMM Level 1 - InitialAd hoc testing. No planning, structure or expected results.
- 2CMM Level 2 - RepeatableBasic documentation and standards. Test plans exist and company is able to reuse project success on future projects.
- 3CMM Level 3 - DefinedGood documentation and standards. Test material retained, regression test plans available. Test material has become an asset the company can use and the company is beginning to use test automation.
- 4CMM Level 4 - ManagedDetailed metrics of the software process and product quality are recorded. Test management tools in regular use. Test automation is used systematically.
- 5CMM Level 5 - OptimizingTesting the process not the product.
- 6Component testingTesting the lowest level of independently executable software. Verified against the V-model Module specification.
- 7Small integration testingTesting faults that could not be found at component testing level by joining together components that have already been tested in isolation. Verified against the V-model technical design specification.
- 8Functional system testingRunning the software as a complete system and testing to find inconsistencies with functionality. Verified against the V-model functional specification.
- 9Non-functional system testingRunning the software as a complete system and testing against non-functional requirements such as how well a function is performed(performance, precision etc.). Verified against the V-model functional specification and business and technical environment specification.
- 10Acceptance testingRunning the software as a complete testing and testing the detect inconsistencies with the customers requirements. Verified against the V-model customer requirements specification.
- 11Regression testingTesting done after some modification has been made to previously released software to ensure no functionality has been lost. Usually done through re running system testing.
- 12Smoke testingTesting that aims at ensuring the most important functions work in order to decide if a build enough to progress with further testing.
- 13—
Información
- Descripción
- Software, Quality and Testing Fichas sobre Sin título, creado por Dan Brown el 04/05/2017.
- Creado por
- Dan Brown
- Visitas
- 0
- Valoración