Development Case: Test

Discipline 

There are no formal changes to the Test Discipline - it is used as is (see the RUP Overview: Test).

Artifacts 

Artifacts	How to use				Review Details	Tools Used/ Templates/ Examples
	Incep	Elab	Const	Trans
Test Evaluation Summary	Could	Must	Must	Must	Formal- Internal	Template: Test Evaluation Summary
Test Package	Could	Could	Should	Should	Formal- Internal	Embedded in the Design Model (see Template: Design Model).
Test Class	Could	Could	Should	Should	Informal	Embedded.
Test Subsystem	Could	Could	Should	Should	Formal- Internal	Embedded in the Implementation Model (see Template: Implementation Model).
Test Component	Could	Could	Should	Should	Informal	Embedded.
Test Suite	Could	Must	Must	Must	Formal- Internal	Template: Test Suite
Test Case	Could	Must	Must	Must	Formal- Internal	Embedded.
Test Script	Could	Must	Must	Must	Formal- Internal	Embedded.
Test Plan	Should	Must	Must	Must	Formal- External	Template- Test Plan
Test Results	Could	Must	Must	Must	Formal- External	Template- Test Results
Workload Analysis Document	Won't	Should	Should	Should	Formal- Internal	Template: Workload Analysis Document

Notes on the Artifacts 

None.

Reports 

Notes on the Reports 

None.

Additional Review Procedures 

None.

Other Issues 

[Note any outstanding issues with the discipline's configuration here.

Such as the Test Approval Criteria:

• Test cases - Informally approved by the system testers.
• Test scripts - casual.
• The system testers decide if the test criteria for an iteration is fulfilled.
• The customer approves the final iteration.]

Configuring The Discipline

When configuring the Test Discipline help can be found in:

• RUP Discipline: Environment
• RUP Activity: Develop Development Case
• RUP Guidelines: Important Decisions in Test

You should also familiarize yourself with:

• RUP Discipline: Test
• RUP Artifacts: Test
• RUP Concepts: Test