NetarchiveSuite|
Size: 1319
Comment:
|
Size: 3327
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 10: | Line 10: |
| The Testcoordinator is a keyplayer during an iteration maintaining following general and specific duties: | |
| Line 12: | Line 11: |
| Preparing for releasetest is not a separate task for each iteration, but an integral part of the whole iteration. The Testcoordinator is accordingly a proactive keyplayer and is dependent on following input: * The developer defines together with the Testcoordinator explicit how each task can be tested during the release test, if this is deemed necessary. * The devolpers are responsible for providing testdata and sanity check descriptions to the Tescoordinator. * Component owners are responsible for providing the Testcoordinator with a list of bugs fixes. The Testcoordinator maintains following general and specific duties. |
|
| Line 20: | Line 27: |
| * coordinating the execution of relasetest together with QA responsible | * coordinating the execution and status of the relasetest together with QA responsible |
| Line 24: | Line 31: |
| * The Test Coordinator is responsible for, that all fixed bugs are addressed in the release test description. * The creation of the Wiki test release page happens soon after the start of the iteration. During the implentation of the iteration following task need to be done: * The release test for each task is continuously defined and implemented. * 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 Test Coordinator will work together with the developer to decide who is responsible for implementring the releasetest * The task is solved when there is a release test. * 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 is spread out to different testpeople |
|
| Line 27: | Line 52: |
| The current iteration releasetest page |
The actual iteration releasetest page |
| Line 32: | Line 56: |
| The current iteration releasetest page | The actual task page The actual review page The actual iteration releasetest page |
To be written on basis of translated: http://kb-prod-udv-001.kb.dk/twiki/bin/view/Netarkiv/IBmetodikDec2006SForberedelseReleaseTest
The Test Coordinator role contains [#TestCorDescription Description], [#TestCorProcesses Responsible for processes], [#TestCorGuidelines Relevant Guidelines], [#TestCorReferences References to Current Work] and [#TestCorBackup Backup].
Anchor(TestCorDescription) DescriptionBR
Preparing for releasetest is not a separate task for each iteration, but an integral part of the whole iteration. The Testcoordinator is accordingly a proactive keyplayer and is dependent on following input:
- The developer defines together with the Testcoordinator explicit how each task can be tested during the release test, if this is deemed necessary.
- The devolpers are responsible for providing testdata and sanity check descriptions to the Tescoordinator.
- Component owners are responsible for providing the Testcoordinator with a list of bugs fixes.
The Testcoordinator maintains following general and specific duties.
Anchor(TestCorProcesses) ProcessesBR
General:
- setting the exact successcriteria together with the developers for each implementation task
- preparing the release test description, data and platform for the releasetest
- coordinating the execution and status of the relasetest together with QA responsible
- executing releasestests
Specific:
- The Test Coordinator is responsible for, that all fixed bugs are addressed in the release test description.
- The creation of the Wiki test release page happens soon after the start of the iteration.
During the implentation of the iteration following task need to be done:
- The release test for each task is continuously defined and implemented.
- 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 Test Coordinator will work together with the developer to decide who is responsible for implementring the releasetest
- The task is solved when there is a release test.
- 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 is spread out to different testpeople
Anchor(TestCorGuidelines) GuidelinesBR
- The actual iteration releasetest page
Anchor(TestCorReferences) References to Current WorkBR
- The actual task page The actual review page The actual iteration releasetest page
Anchor(TestCorBackup) BackupBR Please refer to [:Development#Staffing: Staffing].