Still working to recover. Please don't edit quite yet.
Difference between revisions of "comparison between DSDM and XP testing"
From Anarchopedia
(nn) |
m (Reverted edits by 64.247.69.74 (Talk) to last version by Beta M) |
||
| Line 1: | Line 1: | ||
| − | + | This article will compare and contrast [[Dynamic Systems Development Method|DSDM]] and [[Extreme Programming|XP]] [[software testing]]. | |
| + | |||
| + | ==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]] | ||
Latest revision as of 09:29, 20 November 2008
This article will compare and contrast DSDM and XP software testing.
DSDM[edit]
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.
- Unit tests are prioritised in accordance with Risk Based Testing.
- Testing is done at the end of each phase/iteration. (see: DSDM lifecycle)
XP[edit]
- 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[edit]
In both frameworks:
- Tests are repeatable.
- Customer validation is the key
