ETestingHub-Online Software Testing Tutorial-Software Testing Tools-Test Director
  1. Home

  2. Introduction To Software Testing
  3. What is Software Testing
  4. Software Testing Requirements
  5. Why is Testing necessary
  6. Software Testing Life cycle Software Testing Life Cycle
  7. Software Testing Types

  8. Software Testing Methods
  9. White Box Testing
  10. Black Box Testing

  11. Software Testing Models
  12. V Model
  13. Waterfall Model
  14. Spiral Model

  15. Software Testing Techniques
  16. Levels of Software Testing
  17. Pshycology of Software Testing
  18. Economics of Testing
  19. Defect Profile
  20. Software Requirements
  21. Software Configuration
  22. Requirements Traceability
    Requriment Traceability Matrix
  23. Software Test Plan
  24. Software Manual Testing
  25. Component Testing
  26. User Acceptance Testing(UAT)User Acceptance Testing

  27. Software Automation Testing
  28. Benefits of Automation Testing
  29. Manual Vs Automation Testing

  30. Software Testing Automation Tools
  31. Win Runner
  32. Test Director
  33. Load Runner

  34. Quality Assurance
  35. About Quality Assurance
  36. Importance of QA
  37. QA Faq's
  38. QA Testing

  39. Software Testing-TestCases
  40. Software Testing Validation
  41. Software Testing Verification
  42. Software Testing Versioning
  43. Software Testing Development
    Life Cycle
  44. Glossary of Testing Terms
  45. Software Testing Interview Faq's
  46. Software Testing Books

  47. Software Testing Certification
  48. CSQA
  49. CSTE
  50. ISEB

  51. Software Testing Standards
  52. Software Testing ResumesSoftware Testing Resumes

  53. About Us
  54. Contact Us

     Online Software Testing Tutorial

Software Testing Tools-Test Director

Software Automated Tool TestDirector simplifies test management by helping you organize and manage all phases of the software testing process, including planning, creating tests, executing tests, and tracking defects.
With TestDirector, you maintain a project's database of tests. From a project, you can build test sets groups of tests executed to achieve a specific goal.
For example, you can create a test set that checks a new version of the software, or one that checks a specific feature.
As you execute tests, TestDirector lets you report defects detected in the software. Defect records are stored in a database where you can track them until they are resolved in the software.
TestDirector works together with WinRunner, Mercury Interactive's automated GUI Testing tool.
WinRunner enables you to create and execute automated test scripts. You can include WinRunner automated tests in your project, and execute them directly from TestDirector.
TestDirector activates WinRunner, runs the tests, and displays the results, TestDirector offers integration with other Mercury Interactive testing tools (LoadRunner, Visual API, Astra QuickTest, QuickTest 2000, and XRunner), as well as with third-party and custom testing tools.

The TestDirector workflow consists of 3 main phases:
In each phase you perform several tasks:

Planning Tests
Divide your application into test subjects and build a project.
1. Define your testing goals.
Examine your application, system environment, and testing resources to determine what and how you want to test.
2. Define test subjects.
Define test subjects by dividing your application into modules or functions to be tested. Build a test plan tree that represents the hierarchical relationship of the subjects.
3. Define tests.
Determine the tests you want to create and add a description of each test to the test plan tree.
4. Design test steps.
Break down each test into steps describing the operations to be performed and the points you want to check. Define the expected outcome of each step.
5. Automate tests.
Decide whether to perform each test manually or to automate it. If you choose to perform a test manually, the test is ready for execution as soon as you define the test steps. If you choose to automate a test, use WinRunner to create automated test scripts in Mercury Interactive’s Test Script Language (TSL).
6. Analyze the test plan.
Generate reports and graphs to help you analyze your test plan. Determine whether the tests in the project will enable you to successfully meet your goals.

Running Tests
Create test sets and perform test runs.
1. Create test sets.
Create test sets by selecting tests from the project. A test set is a group of tests you execute to meet a specific testing goal.
2. Run test sets.
Schedule test execution and assign tasks to testers. Run the manual and/or automated tests in the test sets.
3. Analyze the testing progress.
Generate reports and graphs to help you determine the progress of test execution

Tracking Defects
1.Report defects detected in your application and track how repairs are progressing.
2. Report defects detected in the software. Each new defect is added to the defect database.
3.Track defects.
Review all new defects reported to the database and decide which ones should be repaired. Test a new version of the application after the defects are corrected.
4. Analyze defect tracking.
Generate reports and graphs to help you analyze the progress of defect repairs, and to help you determine when to release the application.

What is a Test Set?
After planning and creating a project with tests, you can start running the tests on your application. However, since a project database often contains hundreds or thousands of tests, deciding how to manage the test run process may seem overwhelming.
TestDirector helps you organize test runs by building test sets. A test set is a subset of the tests in your project, run together in order to achieve a specific goal. You build a test set by selecting tests from the test plan tree, and assigning this group of tests a descriptive name. You can then run the test set at any time, on any build of your application.
Do You Keep Track of Defects?
Locating and repairing software defects is an essential phase in software development. Defects can be detected and reported by software developers, testers, and end users in all stages of the testing process. Using TestDirector, you can report flaws in your application, and track data derived from defect reports.

When a defect is detected in the software:
a)end a defect report to the TestDirector database.
b)Review the defect and assign it to a member of the development team.
c)Repair the open defect.
d)Test a new build of the application after the defect is corrected. If the defect does not reoccur, change the status of the defect.
e)Generate reports and graphs to help you analyze the progress of the defects in your TestDirector project.
f)Reporting a New Defect
You can report a new defect at any stage of the testing process by adding a defect record to the project database. Each defect is tracked through four stages: New, Open, Fixed, and Closed. When you initially report a defect to the project database, you assign it the status New.

Home |   Introduction to Testing |   Test Plan  | Manual Testing  | Automated Testing |   About Quality Assurance |   Contact Us   Sitemap  
© Copyright 2015 EtestingHub