Locating and repairing software defects efficiently is essential to the development process. Software developers, testers, and end users in all stages of the testing process can detect defects and add them to the defects project. Using Mercury Interactive’s TestDirector Add Defect dialog box you can report design flaws in your application, and track data derived from defect reports.
For example, suppose you are testing a flight reservation application. You discover that errors occur when you try to order an airline ticket. You can open and report the defect. This includes a summary and detailed description of the defect, where it was discovered, and if you are able to reproduce it. The report can also include screen captures, Web pages, text documents, and other files relevant to understanding and repairing the problem.
If a test run detects a defect in the application under test, you can report it directly from your Test Results window (when connected to a TestDirector project).
When you report a bug from the Test Results window, basic information about the test and the selected checkpoint (if applicable) is automatically included in the bug description.
Using the Add Defect Dialog Box
The Add Defect dialog box is a defect tracking component of TestDirector, Mercury Interactive’s Web-based test management tool. You can report application defects directly to a TestDirector project. You can then track defects until the application’s developers and software testers determine that they are resolved.
Setting Up the Add Defect Dialog Box
Before you can launch the Add Defect dialog box, you must ensure that TestDirector 7.2-8.0 is installed. You must also ensure that WinRunner is connected to a TestDirector server and project. The connection process has two stages. First, you connect WinRunner to the server. This server handles the connections between WinRunner and the TestDirector project. Next, you choose the project you want WinRunner to access. The project stores tests, test run information, and defects information for the application you are testing.
Reporting Defects with the Add Defect Dialog Box
When you are connected to TestDirector, you can report defects detected in your application directly from the WinRunner Test Results window.
To report a defect with the Add Defect dialog box:
If you are working in the Unified report view, you need to connect to TestDirector from the Test Results window as described in step 4.
The Add Defect dialog box opens. Information about the selected line in the Test Results is included in the description.
Reporting Defects During a Test Run
You can insert tddb_add_defect statements to your test to instruct WinRunner to add a defect to a TestDirector project based on conditions you define in your test script. Your statement can include data for the summary and description fields, as well as any other field name and value you specify.
For example, suppose your test begins by logging in to a flight reservation application. If the login is unsuccessful, you can report a defect that specifies the summary and description of the defect as well as the values for the Detected by and Assigned to fields.
Use the following syntax when inserting tddb_add_defect statements:tddb_add_defect (summary, description, defect_fields);
When entering defect fields, use the format:
Be sure to enter field names and not field labels. For example, use the field name BG_DETECTED_BY for the field label Detected By.
If your test contains tddb_add_defect statements, confirm that you are connected to the appropriate TestDirector project before running your test.
WinRunner Related Interview Questions
|SILK TEST Interview Questions||LoadRunner Interview Questions|
|WinRunner Interview Questions||HTML Interview Questions|
|QTP Interview Questions||Manual Testing Interview Questions|
|OpenStack Interview Questions||Automation Testing Interview Questions|
|API testing Interview Questions||Rational robot Interview Questions|
|Selenium IDE Interview Questions||Performance Testing Interview Questions|
|Test Director Interview Questions|
Winrunner At A Glance
Understanding How Winrunner Identifies Gui Objects
Understanding Basic Gui Map Concepts
Working In The Global Gui Map File Mode
Editing The Gui Map
Merging Gui Map Files
Configuring The Gui Map
Learning Virtual Objects
Checking Gui Objects
Working In The Gui Map File Per Test Mode
Working With Web Objects
Working With Activex And Visual Basic Controls
Checking Powerbuilder Applications
Checking Table Contents
Creating Data-driven Tests
Synchronizing The Test Run
Defining And Using Recovery Scenarios
Handling Web Exceptions
Using Regular Expressions
Enhancing Your Test Scripts With Programming
Creating User-defined Functions
Creating Compiled Modules
Calling Functions From External Libraries
Creating Dialog Boxes For Interactive Input
Understanding Test Runs
Analyzing Test Results
Running Batch Tests
Running Tests From The Command Line
Controlling Your Test Run
Setting Properties For A Single Test
Setting Global Testing Options
Customizing The Test Script Editor
Customizing The Winrunner User Interface
Setting Testing Options From A Test Script
Customizing The Function Generator
Initializing Special Configurations
Integrating With Quicktest Professional
Managing The Testing Process
Testing Systems Under Load
All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd
Wisdomjobs.com is one of the best job search sites in India.