This project is read-only.

Specifying the test object intake

The preparation of the intake of the test object so that testing can start as soon as possible after delivery of the test object. This activity contains the following subactivities:
  • Creating a checklist for the test object intake
  • Creating a pre-test test script.

Test object intake

At a certain point, the test team takes delivery of the test object. This first activity has the aim of establishing whether the delivery of the test object is complete, i.e. that it contains what was agreed with the supplier of the test object – no more and no less. Checks whether the test object is complete can be visualized in different ways, for example the default report “Hours of Work” within the MSF Agile template gives a good view if all work is done.

Cannot resolve image macro, invalid image name or id.

Other great resources for test object intake are the reports “stories overview” and “stories progress”.

Cannot resolve image macro, invalid image name or id.

The stories overview report also visualizes the testing effort.

Pre-test test script.

After installation of the test object, a pre-test takes place in order to determine whether the test object is good enough to start testing. A few examples:
  • Checklist with all the functions, which should all be accessible
  • For a number of representative functions, a simple test case with valid input (“good case”) is specified
  • Specification of test cases solely aimed at integration to check that the various parts can communicate with each other.

The data-cycle test is a good choice for this. Pre-test cases can have different formats. Within Test Center you can create a test suite with a set of pre-test cases which is copied and reused between different test plans.

copy suite from plan.png

Another way to create pre-test cases is by automating with Coded UI test them and execute these as proof. Both ways of executing pre-tests can actually must be done by development to proof the completeness and functionality of the test object.

Last edited Nov 6, 2009 at 12:58 PM by ClemensReijnen, version 4


No comments yet.