2875
Comment:
|
2705
|
Deletions are marked like this. | Additions are marked like this. |
Line 2: | Line 2: |
TODO: Translate http://kb-prod-udv-001.kb.dk/twiki/bin/view/Netarkiv/IBmetodikDec2006SForberedelseReleaseTest TODO: Take Time, responsible and backup from http://kb-prod-udv-001.kb.dk/twiki/bin/view/Netarkiv/CurrentUdviklingsMetodik |
|
Line 45: | Line 41: |
* The release test for each task and the overall preparation is continuously defined and implemented. | * After iteration has been started and tasks distributed by [:Process_Role/Project Leader:project leader] * Before [:Process/Code_Freeze:code freeze] within the iteration |
The Prepare Release Test process contains [#PrepRelTestDescription Description], [#PrepRelTestPurpose Purpose], [#PrepRelTestResponsible Responsible], [#PrepRelTestMethod Method], [#PrepRelTestTime Time], [#PrepRelTestInput Input] and [#PrepRelTestOutput Output].
Anchor(PrepRelTestDescription) DescriptionBR
- setting the exact successcriteria together with the developers for each implementation task
- preparing the release test description, data and platform for the releasetest
Anchor(PrepRelTestPurpose) PurposeBR
- a reliable releasetest for all changes made in the actual iteration
- a releasetest ready for execution just after the last iteration task is finished
Anchor(PrepRelTestResponsible) ResponsibleBR
- [:Process Role/Test_Coordinator:Test Coordinator]
Anchor(PrepRelTestMethod) MethodBR
During the implementation of the iteration following task need to be done or verified by a proactive Testcoordinator:
- The creation of the Wiki test release page happens soon after the start of the iteration.
- The Test Coordinator will work together with the developer to decide who is responsible for implementing the releasetest
- Before the implementation of a task the deleloper defines how the release test can be implemented. Unit tests may be sufficient testing so that a proper release test is not necessary.
- Accepted by the test coordinator
- The tests covers the need for each iteration. By development iterations - not production releases - the test focus is only on the code areas, that may be affected by the changes.
- That documentation will be verified.
- That each release test is checked as far as possible before the start of the release test
- That there is clean up of the releasetest page for old test cases and and bug test items.
- That the time for preparation and execution of the releasetest is fair.
- That the platform has sufficient capacity (disk space platforms ..)
- That each test ready for execution is spread out to different testpeople
Anchor(PrepRelTestTime) TimeBR
After iteration has been started and tasks distributed by [:Process_Role/Project Leader:project leader]
- Before [:Process/Code_Freeze:code freeze] within the iteration
Anchor(PrepRelTestInput) InputBR
- Component owners are responsible for testdata and sanity checks and for providing the test coordinator with a list of bugs fixes and a sanity check descriptions
Anchor(PrepRelTestOutput) OutputBR
- a reliable releasetest - just in time