Differences between revisions 1 and 16 (spanning 15 versions)
⇤ ← Revision 1 as of 2009-02-27 13:53:41 →
Size: 704
Editor: EldZierau
Comment:
← Revision 16 as of 2010-08-16 10:24:54 → ⇥
Size: 2792
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
~-[[Action(edit)]]-~ ~-<<Action(edit)>>-~
Line 3: Line 3:
The Prepare Release Test process contains [#PrepRelTestDescription Description], [#PrepRelTestPurpose Purpose], [#PrepRelTestResponsible Responsible], [#PrepRelTestMethod Method], [#PrepRelTestTime Time], [#PrepRelTestInput Input] and [#PrepRelTestOutput Output]. The Prepare Release Test process contains [[#PrepRelTestDescription|Description]], [[#PrepRelTestPurpose|Purpose]], [[#PrepRelTestResponsible|Responsible]], [[#PrepRelTestMethod|Method]], [[#PrepRelTestTime|Time]], [[#PrepRelTestInput|Input]] and [[#PrepRelTestOutput|Output]].
Line 5: Line 5:
[[Anchor(PrepRelTestDescription)]]
'''~+Description+~'''[[BR]]		 <<Anchor(PrepRelTestDescription)>>
'''~+Description+~'''<<BR>>
 * the overall preparation is continuously defined and implemented
 * setting the exact successcriteria together with the developers for each implementation task
 * preparing the release test description, data and platform for the releasetest
Line 8: Line 11:
[[Anchor(PrepRelTestPurpose)]]
'''~+Purpose+~'''[[BR]]		 <<Anchor(PrepRelTestPurpose)>>
'''~+Purpose+~'''<<BR>>
 * a reliable releasetest for all changes made in the actual iteration
 * a releasetest ready for execution just after the last iteration task is finished
Line 11: Line 16:
[[Anchor(PrepRelTestResponsible)]]
'''~+Responsible+~'''[[BR]]		 <<Anchor(PrepRelTestResponsible)>>
'''~+Responsible+~'''<<BR>>
 * [[Process Role/Test Coordinator|Test Coordinator]]
Line 14: Line 20:
[[Anchor(PrepRelTestMethod)]]
'''~+Method+~'''[[BR]]		 <<Anchor(PrepRelTestMethod)>>
'''~+Method+~'''<<BR>>
Line 17: Line 23:
[[Anchor(PrepRelTestTime)]]
'''~+Time+~'''[[BR]]		 During the implementation of the iteration following task
need to be done or verified by a proactive Testcoordinator:
Line 20: Line 26:
[[Anchor(PrepRelTestInput)]]
'''~+Input+~'''[[BR]]		   * 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
Line 23: Line 38:
[[Anchor(PrepRelTestOutput)]]
'''~+Output+~'''[[BR]]		 <<Anchor(PrepRelTestTime)>>
'''~+Time+~'''<<BR>>

 * After the 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)>>
'''~+Input+~'''<<BR>>
  * 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)>>
'''~+Output+~'''<<BR>>

   * a reliable releasetest - just in time

edit

The Prepare Release Test process contains Description, Purpose, Responsible, Method, Time, Input and Output.

Description

  • the overall preparation is continuously defined and implemented
  • setting the exact successcriteria together with the developers for each implementation task
  • preparing the release test description, data and platform for the releasetest

Purpose

  • a reliable releasetest for all changes made in the actual iteration
  • a releasetest ready for execution just after the last iteration task is finished

Responsible

Method

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

Time

Input

  • 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

Output

  • a reliable releasetest - just in time

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