Differences between revisions 11 and 12
⇤ ← Revision 11 as of 2009-05-18 08:06:22 →
Size: 1577
Editor: TueLarsen
Comment:
← Revision 12 as of 2009-05-18 10:22:25 → ⇥
Size: 1679
Editor: TueLarsen
Comment:
Deletions are marked like this. Additions are marked like this.
Line 12: Line 12:
This task includes the coordination and execution of the releasetest. It is the Testcoodinator's responsibility to coordinate the given manpower for the releasetest and support
the different testusers in fullfilling the tascases and the current releasetest status as well.
Line 32: Line 33:
It is the Testcoodinator's responsibility to coordinate the given manpower for the releasetest and support
the different testusers in fullfilling the tascases.
 
The manpower for release testing is decided by the project-leader. 		The process starts when codefreeze is established and ends when all testcases are tested and all documentation are reviewed and updated according to iterations changes.
Line 40: Line 38:
The prepared releasetest.

Action(edit)

TODO: Translate http://kb-prod-udv-001.kb.dk/twiki/bin/view/Netarkiv/IBmetodikDec2006SReleaseTest

The Release Test process contains [#ReleaseTestExecutionDescription Description], [#ReleaseTestExecutionPurpose Purpose], [#ReleaseTestExecutionResponsible Responsible], [#ReleaseTestExecutionMethod Method], [#ReleaseTestExecutionTime Time], [#ReleaseTestExecutionInput Input] and [#ReleaseTestExecutionOutput Output].

Anchor(ReleaseTestExecutionDescription) DescriptionBR

It is the Testcoodinator's responsibility to coordinate the given manpower for the releasetest and support the different testusers in fullfilling the tascases and the current releasetest status as well.

Anchor(ReleaseTestExecutionPurpose) PurposeBR

A reliable release ready for accept test. The quality of the release is decided by the QA-role and Project-leader.

Anchor(ReleaseTestExecutionResponsible) ResponsibleBR

  • [:Process Role/Test_Coordinator:Test Coordinator]

Anchor(ReleaseTestExecutionMethod) MethodBR

Testing all releasetestcases described on the releasetest twiki page. All cases must be tested.

Anchor(ReleaseTestExecutionTime) TimeBR

The process starts when codefreeze is established and ends when all testcases are tested and all documentation are reviewed and updated according to iterations changes.

Anchor(ReleaseTestExecutionInput) InputBR

The prepared releasetest.

Anchor(ReleaseTestExecutionOutput) OutputBR

Process/Release Test WithoutTitle (last edited 2010-08-16 10:24:38 by localhost)