Specifying the infrastructure

On the basis of the specification of the infrastructure contained in the (master) test plan, it is considered whether further specification and detail are necessary. The planning of the test environment, test tools and workplace is also worked out in more detail. Besides describing what resources are necessary, expectations are also set out in respect of the supplying party during the management of these resources. The timely involvement of the various parties is essential. Agreements should be made for the supply and build of the infrastructure, and these agreements should be checked at regular intervals. In consultation with the various suppliers (internal and external) it is determined how detailed the specification should be. The delivery times of the various parts are included in the detailed plan.

Aim

To specify the description of the required infrastructure (from the master test plan or test plan) in a more detailed level.

Sub-Activities

  • Workplace Specification
    • Required locations, desks, chairs, telephones, PCs et cetera.
    • required authorizations, disk space, software, e-mail accounts, et cetera.
  • Specify the test environment
    • Setup of the test environment.
    • Maintenance of the test environment.
  • Test tools usages
    • If, in the creation of the (master) test plan, it is decided to employ test tools, this should be firmed up during this activity. The decision should be backed up by definite choices of one or more tools. As made clear in the definition of test tools, they are intended to support one or more test activities. During this specification of the test tools, it should be clear which test activities are to be supported and how this should be done.
    • The selection and deployment of a tool can be carried out according to the life cycle model, as described section 8.5.5 “Implementing test tools with a tool policy”.

Beside the normal authorization tasks that need to be executed to give someone access to the test environments and e-mail access, when using test tools also authorization need to be maintained for the test artifacts, like test plan access and edit rights, test case creation and execution rights and test result edit rights. In more formal teams you should set these rights in a more strict way than in loose teams, although you also could give someone different kind of rolls in your team.

Within Microsoft Test and Lab Manager the maintaining of this authorization is done at different places. See Microsoft Test and Lab Manager and security and permission settings.

testplanathorizations.png

The test environment can be setup in Microsoft Test and Lab Manager within the Lab Center.
labenvironment.png

While TMap is a tool agnostic methodology, this guidance is focused on the usages of TMap with Microsoft Test tools so in this guidance you will find the TMap activities which are supported by Microsoft Test tools and how this need to be done. To be complete, Microsoft Test tools are supportive to all TMap test activities.

Exit Criteria

check-TMap_1.gif Detailed specification of workplace.
check-TMap_1.gif Detailed specification of test environment.
check-TMap_1.gif Test tool(s) plan of approach.

Last edited Dec 18, 2009 at 7:39 PM by ClemensReijnen, version 11

Comments

No comments yet.