Differences between revisions 2 and 3
Revision 2 as of 2010-08-16 10:24:37
Size: 97
Editor: localhost
Comment: converted to 1.6 markup
Revision 3 as of 2011-02-24 14:44:13
Size: 97
Comment:
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
<<Include(Process/Prepare_Release_Test_WithoutTitle)>> <<Include(Process/Prepare Release Test WithoutTitle)>>

Prepare Release Test Process

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 (last edited 2011-02-24 14:44:13 by MikisSethSorensen)