|
|
| Line 1: |
Line 1: |
| − | This article will compare and contrast [[Dynamic Systems Development Method|DSDM]] and [[Extreme Programming|XP]] [[software testing]].
| + | nn |
| − | | + | |
| − | ==DSDM==
| + | |
| − | Principles (J Stapleton, ''DSDM business focused development, 2nd ed. 2003):
| + | |
| − | 4. Fitness for business purpose is the essential criterion for acceptance of deliverables.
| + | |
| − | 8. Testing is integrated throughout the lifecycle.
| + | |
| − | | + | |
| − | * {{ll|Unit test}}s are prioritised in accordance with [[Risk Based Testing]].
| + | |
| − | * Testing is done at the end of each phase/iteration. (see: [[Dynamic Systems Development Method|DSDM]] lifecycle)
| + | |
| − | | + | |
| − | ==XP==
| + | |
| − | * Fully integrated testing.
| + | |
| − | * Continuous integration.
| + | |
| − | * Write test first, code to pass the test.
| + | |
| − | | + | |
| − | * Extreme programming achieves 100% code coverage through coding only to pass the tests.
| + | |
| − | | + | |
| − | ==Simmilarities==
| + | |
| − | In both frameworks:
| + | |
| − | * Tests are repeatable.
| + | |
| − | * Customer validation is the key
| + | |
| − | | + | |
| − | | + | |
| − | [[Category:Software testing]]
| + | |
| − | [[Category:Software design methodologies]]
| + | |
