Showing posts with label Testcomplete integration with Technologies. Show all posts
Showing posts with label Testcomplete integration with Technologies. Show all posts

How to test Silverlight 4 Applications using TestComplete 8

TestComplete 8 provides greater support to verify Microsoft Silverlight 4 application components by using any functional test methodology such as black-box and white-box test mechanisms. In this version of test complete engine can access Silverlight internal objects, methods, properties and fields in order to automate applications.


In order to track Silverlight components by testcomplete engine, first you require to check following “Extend Silverlight Object Tree” checkbox option by navigating to Tools -> Default Project Properties -> Projects -> Open Application -> Silverlight. Subsequent that, the test complete engine will have access to Silverlight objects and their methods, properties and fields and you can employ those elements in your automated tests. (Pls. refer the following screen cap)




















Further, you can notice all Silverlight objects and their available methods and properties in the hierarchy of object tree model subsequent to explore browsers such as IE, Firefox.











Now TestComplete introduce a new SlObject method in order to automate applications with Silverlight components. Using this method, users allow obtaining a Silverlight component by its name, which was stated in the application’s source code.

Moreover, TestComplete also offers a SlApplication scripting object that is a wrapper to a Silverlight application’s main class that sum up application defined functionality and inherit methods and properties of the System.Windows.Application class.

As well as the members of this System.Windows.Application class contains the SlClasses property. This property assist you for scripting interface to namespaces and assemblies classes included in your Silverlight application package in the.xap file.








Now Testcomplete provide great opportunity to access static non visual objects and their public members by using SlClasses property. In addition to functional testing, this special feature allows you to perform unit/web component performance testing by using application’s internal classes and their associates.

Hope that the above mentioned features will facilitate you easily creates more powerful automated tests for your Silverlight applications.

To download TestComplete 8 Trial

Configure TestComplete project to access the InfoPath form’s

The following sections will explain how to configure TestComplete automation project and access the InfoPath form’s fields in TestComplete scripts.
Configuring TestComplete Project
Before scripting & testing our InfoPath forms we have to configure the TestComplete project -
• Launch TestComplete and create a new test project suite and project.
• Right-click the TestComplete project node in the TestComplete Project Explorer panel and select Edit - Properties from the context menu. This will open the TestComplete project editor in the Workspace panel and display the Properties page.
• Select the “Open Applications – MSAA” group on the left of the page. Then TestComplete will display a list of MSAA properties on the right. Note, this list contains windows class names and their properties that will be exposed by the use of TestComplete’s MSAA engine.
• Choose the check box related to the asterisk (*) class name:



This allows TestComplete to use the MSAA engine to expose methods and properties of any existing window.
Subsequent to configure the MSAA engine so that it exposes any window, the form is displayed in the objects tree as the object named “pane”. You can script required InfoPath test scenario by exploring the needed form controls and its properties.

Integration of Test Complete with visual studio "Team Foundation Server"

The following illustration shows the process through which Testcomplete test results are generated, published, and eventually moved into the operational data stores and data warehouse of Team Foundation Server.

Following are the prerequisites to publish TC test results,

1. Get permission to TFS Server for Publishing results (In my experiment, I granted permission as Root Admin).
2. Get full access permissions for accessing Build Server and relevant project folder to access relevant builds. E.g. \\testtfs08\\
3. Get TestComplete installed on TFS server.

Steps:

A. Extending Visual Studio Tests with TestComplete Test Projects

Please See the below article
http://darshikaj.blogspot.com/2009/05/intergrate-testcomplete-test-with.html

B. Publish TestComplete Test Results to TFS Server

1. The first thing we will require to do is create a new build agent on the server. To do this you should right click on the ‘Builds’ node for your team project, then click ‘Manage Build Agents’. Once dialog comes up, click the ‘Add’ button which will bring us to the dialog below.



2. Share and grant full access permission to the project build repository defined below. (Minimum of Build Services group membership is required).

Intergrate TestComplete test with Microsoft Visual Studio Team system (Test Edition)

The following illustration shows the process through which Testcomplete test results are generated, published, and eventually moved into the operational data stores and data warehouse of Team Foundation Server.

A. Extending Visual Studio Tests with TestComplete Test Projects

1. Create a Test Script in TestComplete6.

2. Create a Test Project in Visual Studio 2008.

3. TestComplete includes a Visual Studio Team System integration package that adds a new test type “TestComplete6 test” to Visual Studio.



4. Add the TestComplete Test suite to the VS Test Project.



In this Visual Studio editor, we can specify the TestComplete project suite with the desired tests and select the specific test items to be executed.

5. Now switch to the Test List Editor panel in VS and select the TestComplete test for execution.



6. After Visual Studio finishes running the tests, we can view the results of the TestComplete test execution directly within Visual Studio,

Search This Blog