comparison between DSDM and XP testing - Revision history

Rev 22: Reverted edits by 64.247.69.74 (Talk) to last version by Beta M

2008-11-20T09:29:43Z

Reverted edits by 64.247.69.74 (Talk) to last version by Beta M

64.247.69.74: nn

2008-11-20T02:47:51Z

Beta M at 17:18, 31 December 2006

2006-12-31T17:18:23Z

New page

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]]

← Older revision		Revision as of 09:29, 20 November 2008
Line 1:		Line 1:
−	nn	+	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]]

@@ 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):
-. Fitness for business purpose is the essential criterion for acceptance of deliverables.
-. 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]]