Come let us explore together…

Posts tagged ‘TestComplete 8’

What is new in TestComplete 8 ? – Part 2


DDT enhancements

Data Driven testing is well supported in this version of TestComplete. The enhancement ‘Data-Driven loop’ is mainly useful for Keyword-driven testing. Usually keyword-driven test can be done with minimum programming/coding knowledge. This ‘Data-Driven loop’ feature still makes it easier to implement without much of technical knowledge.

If your keyword-driven test has repeated actions and differ only with test data, then you can opt for this feature.

To turn the repeated code as a loop with different data, simply select the set of actions (test steps or sub-actions) which you want to turn in to loop and right-click to get the pop up menu. Select ‘Make Data Loop’ option to get the data source configuration wizard.

Selecting or creating data source, configuring how and which data to be read, binding with test steps and much more can be done through this wizard itself.

Based on the data source (Excel, CSV, DB table), the configuring and data selection process (wizard options) will differ. But this wizard will be very useful and can use with minimum programming knowledge.

The good part is after specifying the data source file; it will be visualized inside the wizard itself.

  • You can view the data in worksheets in case of Excel worksheet
  • Comma separated values in case of CSV.
  • Content of tables in case of DB tables

 

This wizard will reduce the typo errors, data source connection problems, test data range specification etc.,

Note: In the script based automation we can reap the above DDT advantages using its built-in drivers, methods and properties.

https://automate101.wordpress.com/2010/07/27/data-driven-testing-with-testcomplete-part-2/

Network suite enhancements

 

Networksuite has a good number of improvements in TestComplete 8. Among these I like automatic logging/Reboot on remote machines and visualizing the remote desktop screens.

Now you can write a script to login/reboot and remote machines which you treat as client and start test suites there.

Also the remote machines desktop screen can be viewed inside the network suite panel. This allows us to track the execution without manually log-in into those systems.

I have to really explore more on this feature because it is said that GUI tests run via the Remote Desktop do not fail if the Remote Desktop is minimized or closed during the test run. Need to know exact difference between TestComplete 7.52 and 8.

TestLog enhancements

 

If you have used test Visualizer while recoding the scripts, it will replay with synchronization to the recorded images while playing back.

We can view the actual image and expected images in the test log once the test were completed. These log items will show as an image comparison where we can analyze the image to find the root cause if it has the failure.

ImageComparion in Testlog
Comparison of Expected and Actual screen shot

 

Now the test logs can be exported as bugs to JIRA, OnTime and Software Planner. This feature minimizes the bug logging and tracking of it.

As we have methods and properties to access test log items using script, this version has new “LogItem.Status” property to determine its status of specified LogItem. These set of methods and properties will be useful when you want to parse the execution log and prepare/document the data that is interested for you.

Script Extension enhancements

1. The next version of WMI (1.1) scripts are added to Script Extensions to support most likely used functions. A total of 10 new functions were added in this version.
2. The bug reporting mechanism to JIRA, OnTime and Software Planner were implemented as script extensions

Still exception handling mechanism can be improved in Script Extension. Also more objects like Registry, Stores etc., can be given access inside script extensions.

Others

In the Toolbar -> options menu item, we can configure the TestComplete options.

• ‘Images’ and ‘When referring to an non-existence object’ items are moved from General list.

• ‘Debug Services’ option was removed

• New option “Java Bridge” is added to map the JVM (for supporting java classes)

• Under “Recording” option, the option to ‘Record text input into simple editors as’ will allow us to use “SetText” or “Keys” function. Also you can set to record only user action on TestedApps application and skip other actions.

• The option “Visualizer” is removed in this version.

• We can configure the sorting of categories displayed in object browser using the option Panels -> Object Browser -> Categories sorting

You can directly send error reports to AutomatedQA support using “Help -> Contact support team” menu option, which will open the new support form of TestComplete.

If you come across any differences/ enhancements in TestComplete 8, please share here…

 

Hope there is 101 ways to automate…

Thanks & Regards,
Giri Prasad

What is new in TestComplete 8 ? – Part 1


Hi All,

Last week the much awaited TestComplete 8 (TC8) was released after successful beta testing. This was the first release from AutomatedQA after it merged itself with other similar vendors and makes a new company SmartBear software.

This version is said to be developed closer and communicative with its ally’s products (SmartBear and Pragmatic products).  Come let us try and experience whether we can benefit or not !!!

Before installing there is no much system requirements to be taken care of. If your system has TestComplete 7 and working fast enough, you can directly install version 8 and no additional resources are needed.

Also don’t directly open any projects developed in previous versions of TestComplete in TC 8. Because once it is opened, TC8 will convert to its version and you cannot open the same project with lower versions. (Take a backup of your projects before using TC8). From the perspective of AutomatedQA, what is new or enhancements?

  1. UI changes
  2. Support for latest products/applications
  3. Test Visualizer
  4. Name Mapping enhancements
  5. DDT enhancements
  6. Network suite enhancements
  7. TestLog enhancements
  8. Script Extension enhancements
  9. Other differences

This week I tried with the new TestComplete 8 (8.0.290.7) trial version and like to share my experience. You can install TestComplete 8.0 in parallel with 7.52 version. (No need to remove or upgrade previous version)

UI changes:

The first change everyone expects was with UI level changes. Most of the newer versions come with a mandatory UI change. Also we cannot accept it is a new version without these changes.

In TC8 there is not much change in the menu and tool bars other than changes in Run button and Checkpoint buttons.

You will observe more changes in the UI if your have Windows Vista or later OS versions…

  • You can see new Recording toolbar (with dense down items) having only Play, Pause and Stop buttons. The other recording items are hidden and can make it visible using the slider in the toolbar.
  • While opening the project we can see a link to sample TestComplete projects in the file open dialog box which simplifies the access to stored sample projects.
  • During playback you can see a playback toolbar near the TestComplete notification area (Upper right corner) holding buttons to Pause and Stop payback.
  • The object property icon is renamed to “Object Spy
  • Refresh and Highlight toolbar buttons are added in the NameMapping section

Support for latest products and applications:

Comparing with the older versions, TestComplete 8 supports the following:-

  1. .NET framework 4.0
  2. 64-bit Windows, .NET and Java applications
  3. Microsoft Silverlight 3
  4. Mozilla Firefox 3.6

In addition it can access methods inside JAR files and 64-bit DLLs. We can write code to call the methods defined in JAR file and 64-bit DLLs.

Test Visualizer

TestComplete 8 has new feature called Test Visualizer which is useful while recording, mapping objects, play back and result verification.

From my understanding Test Visualizer is a new feature which takes screen shots of Application Under Testing(AUT) for the on-screen actions (Click, SetText, etc,.) done. This will work only while your record through TestComplete 8 version. (For older projects you need to re-record the test steps to bring in the feature)

TestVisualizer sample screen shot
Figure showing the Test Visualizer feature

Advantages:-

  1. Track the test recording and execution. (Both sequence and actions)
  2. Without having the actual AUT running, map the objects directly from Test Visualizer.
    1. I think TC is not just taking a screen shot for the Test Visualizer. Because we have an option here in the frames to map object dynamically without the actual object running behind.
    2. To map the object which you missed while recording just click the Eye icon in the picture frame (Test Visualizer), this will open the “Visualizer Frame” where we can see the recorded AUT screen.
  3. Using this frame we can map new object directly by scrolling through and right clicking the screen object (If it is already mapped , shows as mapped)
  4. If the AUT was changed after recording you can update the changes right from this Test Visualizer using “update from screen” option available in Visualizer frame. (AUT respective screen must be active(running) for this option alone)
  5. You can add on-screen action test step from this frame when using a keyword driven test

How about resource consumption for this feature ?  Need to wait and see !

Name mapping enhancements

Name mapping is a feature where definitely lot of improvement should come. AutomatedQA is constantly placing enhancement to make it comparatively good.

Conditional mapping is a cool option added in TC 8. We can map our object based on few conditions (AND & OR). When you map an object, in the “object name mapping window” we can find an option to switch between Conditional or Basic mode. Basic mode is usual way of mapping; Conditional is having different values for same property or different property itself for an object.

In conditional mode, we can design the condition by adding property-value along with condition type to tell how TestComplete how an object should be recognized.

This way we can avoid lot of conditional statements and property validations inside the scripts and get it done in primary location. Usually this may helpful when the script is handling different version of AUT in different environments.

Also it is said that highlighting and deletion is made easy in this version.

Hope there are 101 ways to Automate…
Thanks & Regards,
Giri Prasad