Changes between Version 5 and Version 6 of DeveloperGuidelines/Testing/EdenTest/WriteTestcase
- Timestamp:
- 06/08/14 06:16:39 (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
DeveloperGuidelines/Testing/EdenTest/WriteTestcase
v5 v6 17 17 Before writing your first testcase, please make sure that you have !EdenTest set up, you understand the directory structure and the know-how of how to run !EdenTest and see its results. If not, go through [http://eden.sahanafoundation.org/wiki/DeveloperGuidelines/EdenTest EdenTest]. 18 18 19 As !EdenTest is built on the principle of '''ATDD''' which is a practice in which the acceptance criteria is decided, with examples, and then distilled into a set of concrete acceptance tests before development begins. To say it simply, write the tests which covers your functionality before writing the code for the functionality. Then, write the code for that functionality so that it passes the tests. The '''T''' aspect of '''F.I.R.S.T'''. 19 As !EdenTest is built to make it easy to do '''ATDD''' which is a practice in which the acceptance criteria is decided, with examples, and then distilled into a set of concrete acceptance tests before development begins. To say it simply, 20 ATDD is like: 20 21 22 1. Define (or refactor) acceptance test(s) from user stories 23 2. Automate the acceptance test 24 3. Run the acceptance test 25 4. If fail: refactor code, then repeat 3. If pass: development stops, back to 1. 21 26 === What we have to do? === 22 27