Asset Upgrade Tool in QTP
QTP testing documents, such as tests, components, and application areas
Testing document attachments, such as function libraries, shared object repositories, and recovery scenario files
This tool is intended for use only by the Quality Center Administrator and must be run during the Quality Center upgrade process, before you begin working with Quality Center integration features.
The QTP Asset Upgrade Tool for Quality Center is the only way to upgrade QTP assets in a Quality Center 10.00 project, from an earlier QTP version to the current format.
Go Back to -> QTP 10 Integration with QC.
QTP 10 - Asset Comparison Tool and Asset Viewer
The QuickTest Asset Comparison Tool compares each element of the asset in a hierarchal display. The tool also enables you to drill down to view a comparison of the assets that are associated with that asset. For example, when comparing two versions of a test, the comparison may indicate that two of the function libraries, a recovery scenario, and some of the action steps changed between the two versions. You can then drill down to view a comparison of the two versions of any of these items.
The QuickTest Asset Viewer is similar to the Asset Comparison Tool, but is used to view the data for a single version of a QuickTest asset.
Go Back to -> QTP 10 Integration with QC.
Versioning and Baselines
- Versioning. In previous versions of QTP and Quality Center, limited version control options were available if your Quality Center server had the Version Control Add-ins, which worked with third-party version control tools to perform version control. Now, version control is fully integrated into Quality Center, and the site administrator can enable version control on a per project basis.
- Baselines. In Quality Center, a project administrator can create baselines that provide "snapshots" of a project at different stages of development. In the Management module—Libraries tab, the administrator first creates a library, which specifies the root folders from which to import the data. The administrator then creates the actual baseline, which comprises the latest checked in versions of every asset included in the library. The administrator can also import and share entire baselines from other Quality Center projects.
When QTP is connected to a Quality Center project with version control support, you can check any QTP asset into or out of the version control database.
When a project reaches an important stage in the project lifecycle, the administrator can create a new baseline of the files in the library at that point.
In Quality Center, these baselines can be viewed and compared in their entirety. In QuickTest, you can view, retrieve, or compare the individual assets saved in any baseline of a library. This enables you to review an asset as it appeared at a specific phase in the project time line.
Notes:
Baselines are supported in Quality Center 10.00 Enterprise and Premier editions only. They are not supported in Quality Center Starter edition.
Go Back to -> QTP 10 Integration with QCFor more information, see Managing Versions of Assets in Quality Centerand Viewing Baseline History
Delphi Add-in in QTP
The new Delphi Add-in enables you to test Delphi controls that were created in the Delphi IDE and are based on the Win32 VCL library.
QTP Delphi Add-in Extensibility is an SDK (Software Development Kit) package that enables you to develop support for applications that use third-party and custom Delphi controls that are not supported out-of-the-box by the QTP Professional Delphi Add-in.
For more information, see Using the Delphi Add-in
Go back to -> New features in QTP 10
QTP Test Results Analysis with New Reporting Functionality
Test Results Analysis with New Reporting Functionality
QuickTest 10.00 includes a powerful set of new reporting options that help you analyze and manage your run results more thoroughly and efficiently. These include:
- Jump to step. When you want to know more about a particular node in the Test Results window, right-click it and select Jump to Step in QuickTest. The QuickTest main window comes into focus, and the cursor jumps to the relevant step. For more information, see Jumping to a Step.
- Export Test Results to Microsoft Word or PDF Formats. In addition to HTML format, you can now select to save your QuickTest run results in Microsoft Word or PDF formats. You can then share this information, together with any local system monitoring data, with your developers and performance testing teams. For more information, see Exporting Test Results.
- New Image Reporting Options:
- Add Images to the Test Results. When you use the Reporter.ReportEvent method to add information to the run results, you can now specify an image file as the fourth argument. When you view the results, the image is displayed in the Result Details tab of the Test Results window. For example, you can include an image returned by a CaptureBitmap step in the run results. For more information, see ReportEvent Method in the Utility section .
- View Bitmaps Differences in Bitmap Checkpoints. In addition to the expected and actual bitmaps that are displayed in the Test Results window, you can also select to view the differences between the two. The difference bitmap is a black-and-white image that contains one black pixel for every pixel that is different between the two images. For more information, see Analyzing Bitmap Checkpoint Results.
- Include Images in Exported and Printed Test Results. When you choose the Detailed option for printing or exporting, the document now includes all images. These include screen captures of steps, expected, actual, and difference bitmaps for bitmap checkpoints, and any images sent to the run results using the ReportEvent method. For more information, see Printing Test Results.
- Additional Quality Center Details. The run results for tests and components that are run as part of a Quality Center test set now include the Quality Center server and project name
New ToDo Pane
The new To Do pane that is now available in the QTP, enables you to create and manage self-defined tasks, and to view a compiled set of the TODO comments from your tests, components, and associated function libraries.
For example, you can use the Tasks tab to provide instructions to someone else during a handover, or to create reminders for yourself. The Tasks tab provides check boxes in which you can mark off each task as you complete it. In the Comments tab, you can view and sort all your TODO comments. You can also jump directly to a selected TODO comment in the testing document.
If you use the Maintenance Run Wizard to detect updates needed to your steps or object repository, then you can use the To Do pane to track and manage the TODO comments added during the maintenance run session.
You can also export your tasks and TODO comments from the To Do pane to an XLS (Excel), CSV (comma separated), or XML file.
Go back to -> New features in QTP 10
Custom Bitmap Checkpoint Comparison Algorithm in QTP 10
After you install and register a custom comparer on the QTP computer, your comparer is available for selection in the Bitmap Checkpoint Properties dialog box. The dialog box provides space for specifying additional configuration preferences expected by your comparer.
When QTP a bitmap checkpoint that uses a custom comparer, it supplies the expected and actual bitmaps to the custom comparer object. It then receives and reports the results that the custom compares returns.
Go back to -> New features in QTP 10
Download QTP 10.0 Evaluation
QuickTest Pro 10 works on Windows, VMware and Virtual PC, supports Internet Explorer 8, Firefox 3 and offers additional add-ins for Java, .Net, Oracle, Deplhi, Siebel, Peoplesoft, SAP.
Features (It is a ppt converted into pfd file it contains all the details of the new features with clear figures, so must download this)
LoadAndRunAction - Call Actions Dynamically During the Test Run
Call Actions Dynamically During the Test Run
Generally, when you insert a call to an external action, the action call becomes part of the test, and the called action is loaded each time you open the test.
In some situations, you may want to take advantage of the new LoadAndRunAction statement to load an action only when the step runs, and then run that action.
This is useful, for example, if you use many conditional statements that call external actions, and you do not want to load all of these actions each time you open the test, since these actions may not be necessary during the run session.
Go Back to-> New Features in QTP 10
Save Tests with Resources in QTP 10
Improve Portability by Saving Copies of Tests Together with Their Resource Files
Tests and their resource files are often stored on a network drive or in Quality Center. However, you may need to open or run a test when you do not have access to the network drive or QC. For example, you may need to create a portable copy of a test for use when traveling to other sites.
You can save a standalone copy of your test and its resource files to a local drive or to another storage device using the File > Save Test with Resources command. When you save a test in this manner, QTP a copy of your test, all associated resource files, and any called actions.
Go Back to -> New Features in QTP 10
Local System Monitoring in QTP 10
You can monitor a number of different system counters to view the effects your application has on the system. You can also define upper limits for the counters. If any of the specified counters exceed these limits, the test run will fail.
Additionally, you can export the data from the System Monitor tab to a variety of file types.
The results generated for the counters you monitor are displayed as a line chart in a special System Monitor tab in the Test Results window.
The points in the chart are synchronized with the steps in the Run Results tree. When you select a step in the tree, the (red) Current Step line jumps to the corresponding location in the chart.
You can also export the data from the chart so it can be further analyzed in other programs.
Go Back to -> New Features in QTP 10
QTP script to Add defect in QC
Set TDConnection = CreateObject("TDApiOle.TDConnection")
TDConnection.InitConnection "http://yovav/tdbin" ' URL for the DB
TDConnection.ConnectProject "TD76","bella","pino" ' Valid login information
If TDConnection.Connected Then
MsgBox("Connected to " + chr (13) + "Server " + TDConnection.ServerName _
+ chr (13) +"Project " + TDConnection.ProjectName )
Else
MsgBox("Not Connected")
End If
'Get the IBugFactory
Set BugFactory = TDConnection.BugFactory
'Add a new empty bug
Set Bug = BugFactory.AddItem (Nothing)
'fill the bug with relevant parameters
Bug.Status = "New"
Bug.Summary = "Connecting to TD"
Bug.Priority = "4-Very High" ' depends on the DB
Bug.AssignedTo = "admin" ' user that must exist in the DB's users list
Bug.DetectedBy = "admin" ' user that must exist in the DB's users list
'Post the bug to DB ( commit )
Bug.Post
Download the code from here
New Resources and Dependencies Model of QC with QTP
If you are working with a Premier edition Quality Center server, then you can also import and share your resources across different projects. You can synchronize these assets in both projects when changes are made. This functionality also enables you to reuse your existing assets instead of creating new assets whenever you create a new project. For example, you can create a set of template assets to use as a basis for new projects.
Using the Resources and Dependencies Model
In previous versions of QTP and Quality Center, a test's associated resource files (such as shared object repositories, function libraries, recovery scenarios, and external data tables), were stored in Quality Center as attachments, while files associated with an application area were stored in a standalone Resources folder in the Business Components module.
Quality Center 10.00 introduces a new Test Resources module. This module enables you to store all of these resources as separate entities that are linked to their owners and marked as dependencies. Tests or actions that call other tests are also linked as dependencies.
When you select a QTP test, business process test, or individual component in the Quality Center test or component tree, you can view these dependent resources and tests in a new Dependencies tab. The Dependencies tab shows all Quality Center entities that are used by your testing document as well as all entities that are using it. For example, if your QTP test is associated with two function libraries, and the actions in your test are associated with three object repositories, these entities will be displayed in the Using table of the test's Dependencies tab. If one of the actions in your test is called by another test, then that calling test will be displayed in the Used by table.
In QTP, you can also view the action-specific dependencies in the Used By tab of the Action Properties dialog box.
Quality Center recognizes assets that are linked as owned by or owner dependencies and ensures that these important relationships are maintained when you import or create baselines, rename or move resources, select to delete resources, or perform other operations that can impact these relationships.
Note: If required, you can continue using the previous attachments model for all or some of your QTP assets. However, if you use the old model, you will not be able to take advantage of many of the features associated with the resources and dependencies model.
Go Back to -> QTP 10 integration with QC.
QTP 10 Integration with QC
QTP 10 has a powerful set of new Quality Center 10.00 integration capabilities for QuickTest assets.*
These integration capabilities include:
- New resources and dependencies model for storing and managing shared assets
- Support for asset versioning and baselines
- Asset Comparison Tool for comparing versions of individual QuickTest assets and Asset Viewer for viewing an earlier version of a QuickTest asset
- A special tool for Quality Center administrators that upgrades all QuickTest assets to use these new features.
* QTP assets include tests, components, application areas, and the resources associated with them, such as shared object repositories, function libraries, recovery scenarios, and external data tables.
New Resources and Dependencies Model
Versioning and Baselines
Asset Comparison Tool and Asset Viewer
Asset Upgrade Tool