[Original] Test Management Process with testdirector

Test Management Process with testdirector:

 

The test management of testdirector includes the following four stages:

Requirement definition (Specify requirements):

Analyze the application and determine test requirements.

Test Plan (Plan tests):

Establish a test plan based on test requirements.

Test execution (Execute tests):

Create a test set and perform the test.

Defect tracking (Track defects):

Report defects in the program and track the whole process of defect repair.

 

During each phase of the test, you can analyze the data by generating detailed reports and icons.

 

1.2 requirement definition (specify requirements)

Analyze the application and determine test requirements.

 

 

Define the test scope (Define testing Scope):

Check the application documentation and determine the test scope-test purpose, objectives, and policies.

Create requirement (Create requirements):

Create a requirements tree and make sure it covers all test requirements.

Describe the requirement (Detail requirements):

Create a detailed directory for each requirement topic in the "requirement Tree", describe each requirement, and assign it a priority. If necessary, add attachments.

Analysis Requirements (Analyze requirements):

Generate Reports and charts to help you analyze test requirements and check requirements to ensure they are within your test scope.

 

1.3 planning tests)

Create a test plan based on the defined test requirements.

 

Define a test policy (Define testing strategy):

Check the application, system environment, and test resources, and confirm the test objectives.

Define the Test Topic (Define test subject):

Divide applications based on modules and functions and correspond to each test unit or topic to build a test plan tree ).

Define test (Define tests):

Define the test Type for each module and add basic instructions for each test.

Create requirement coverage (Create requirements coverage):

Connect each test to the test requirement.

Design test procedure (Design test steps):

For each test, the type of test (manual test and Automatic Test) to be performed is determined first. If you want to perform a manual test, test steps needs to be added to the test plan tree ). The test procedure describes detailed test operations, check points, and expected results for each test.

Automatic Test (Automate tests):

For the part for automatic testing, you should use Mi, yourself, or a third-party testing tool to create a test script.

Analyze the test plan (Analyze test plan):

Generate Reports and charts to help you analyze test plan data and check all tests to ensure they meet your test goals.

 

1.4 test execution (running tests)

Create a test set and perform the test.

 

Create a Test Set (Create Test Sets):

Define different test groups in your project to achieve different test objectives. They may include, for example, test a new application version or a special feature in an application. Determine which tests are included in each test set.

Determine the schedule (Schedule runs):

Schedules test execution and assigns tasks to testers.

Run the test (Run tests):

Perform each test set automatically or manually.

Analyze the test results (Analyze test results):

View test results and make sure that application defects are discovered. The generated reports and charts help you analyze these results.

 

1.5 defect tracking)

Report defects in the program and track the whole process of defect repair.

Add defect (Add Defects):

Report New defects found during program testing. Quality Assurance personnel, developers, project managers, and end users can add defects at any stage of the testing process.

Check new defects (Review new defects):

Check for new defects and determine which ones should be repaired.

Fix open defects (Repair open Defects):

Fix the bugs you decide to fix.

Test new build (Test new build):

Test the new build of the application and repeat the above process until the defect is fixed.

Analyze defect data (Analyze defect data):

Generate Reports and charts to help you analyze the defect repair process and determine when to release the product.

 

Testdirector FAQs:

Problem 1: After testdirector is installed in win2003, open the testdirector icon and some "HTML code" is displayed, as shown below:

<HTML>
<Head>
<Meta http-equiv = "Content-Type" content = "text/html; charset = iso-8859-1"/>
<Meta name = "generator" content = "Microsoft FrontPage 4.0"/>
<Title> testdirector 8.0 SP2 </title>
<! -- ============================== Style =============================== -->
<Style type = "text/CSS">
# Links_sheet {
Left: = 0;
Top: = 50;
Position: relative;
Visibility: visible ;}
</Style>
</Head>
Solution: start IE-> Internet Options-> Security-> trusted site-> Add a website, such as http: // js-test154, and try again!

Problem 2: testdirector cannot be opened in IE7

Solution: refer to my previous post: http://www.cnblogs.com/mayingbao/archive/2006/04/25/384153.html

Question 3: Why is the password of site administrator of testdirector missing?

Solution: Open the user table in the DOMs. mdb library in c: \ Program Files \ common files \ Mercury Interactive \ domsinfo

Note: The password must be tdtdtd.