Category: TestComplete

  In module 1 of this Fast Start TestComplete course we’ve looked at the TestComplete development environment. You might not necessarily understand what everything does but you should be familiar with these core components: Project Workspace – where you develop your automated tests Object Browser – where you can examine the application you’re testing And within each of those components you should understand what these sub components are for: Project Workspace     - Project Explorer: shows the artifacts created for your automation project - Workspace: where you create and modify those different artifacts Object Browser - Object List: hierarchy of objects (processes, windows & browsers) on your system - Properties: a list of characteristics relating to a specific object...

If you’re looking to learn TestComplete fast then this is the place to start. We’ve pulled together 12 fast start training modules teaching you all you need to know when you start out with TestComplete. Everything you need to become productive in the shortest time possible. Each module comprises of one short video along with a list of key learning point and concepts. All this designed to get you productive with TestComplete in the shortest time possible. The quicker you become familiar with TestComplete the quicker you’ll be writing and running effective automated tests. Over the course of 12 modules we’ll cover the following topics: Module 1 – Getting Started Key Components Module 2 – Creating our first test Module...

Cross browser testing is always a bit of a challenge for test teams that are trying to keep up with the ever increasing combinations of browsers, platforms and operating systems. Add mobile browsers into the mix and you may as well forget traditional approaches testing. Testing manually just isn’t going to cut it. One approach worth looking at for cross browser testing using TestComplete’s browser emulator feature. Depending on your website or web app you may well be able to write a test once then just scale up using emulations of browsers on a single machine. Alright, nothing really replaces testing on the real device with the final release of the product. That’s an approach that’s time consuming, requires lots...

We’ve mentioned in previous posts about Name Mapping in our software test automation tool TestComplete. Whilst creating a Mapped name for an object we select a few properties which we use to identify that object. This is the ‘Basic Mode’ of Name Mapping. In some cases though, the value of the selected property may differ. Perhaps in a different environment the properties are different. For example, a window may have different class name in different OS. Sometimes you may want to give the value of the property within some range or with some condition. For example, Childcount > 34, or Name should start with the string “save”. To create name mapping with these conditions we have to use the Conditional...

In Testcomplete the Test Items page within your project is used to organize, manage & execute the test cases that you’ve automated. For example we might have developed test automation scripts for thousands of test cases. However, each time we want to create a software test automation run we may want to execute only a selection of the testcases. We may also want to execute some multiple times with different test data. The Test Items feature allows us to perform all of these tasks simply. Organise Testcases Execute only selected Testcases. Execute a testcase multiple times Executing a testcase with different test data A blank Test Items page will look like this: So lets work with this and consider the...

Let us consider a recorded test automation script for a scenario in an application. In that script, we have the test data which we entered into our application while recording the test. If you execute the script, it will use exactly the same test data. However, this approach isn’t scalable and forces you to use the same test data every time your run the script. So ideally we should create test scenarios with a range of different test data. If your application has a scenario, which needs to be tested with different test data, then you can go with data-driven framework for automated testing. A Data-Driven framework is an excellent test automation framework, which gives good test coverage with minimal...

The Full Name of an object, which is defined by TestComplete, can be difficult to work with. For example if you have a long object name with special characters, typing and reading it can be time consuming and prone to typing mistakes. Let us say a textbox in a web page has the following name. Sys.Process(“iexplore”, 2).Page(“https://www.google.com/accounts/ServiceLogin?service=mail&passive=true&rm=false&continue=http%3A%2F%2Fmail.google.com%2Fmail%2F%3Fui%3Dhtml%26zy%3Dl&bsv=llya694le36z&scc=1&ltmpl=default&ltmplcache=2&from=login”).Table(1).Cell(0, 1).Panel(“login”).Form(“gaia_loginform”).Panel(“gaia_loginbox”).Table(0).Cell(0, 0).Panel(0).Table(“gaia_table”).Cell(2, 1).Textbox(“Email”) This is not a simple bit of text to work with. To overcome this issue we can use the NameMapping feature. In the above mentioned object, from the text “Sys” to “Textbox(“Email”)” we can create a Mapped name for every object and use it in our scripts. If you want to learn more about the basics of how name mapping...

TestComplete has many features to simplify test automation script development work. One of them is Name Mapping. Using this feature we can create a Mapped name using the properties of the object in our application. We can then use this name to refer to that object in our scripts. But why should I create a Mapped name? What are the advantages of doing this? Let us consider the following example. In a web page we have a button, a ‘Login Button’. In the process tree the full name for this button is as follows: Full Name of Login button: Sys.Process(“iexplore”).Page(“*”).Form(“main”).Button(“button1”) If I use this Full Name in my test automation script to refer the button it is easy to get...

Sometimes we’ll find that our application won’t be open to TestComplete. So the application doesn’t expose any details about the it’s objects and methods, or Testcomplete may not have in-built support for the controls or windows in the application. For example we may have a browser type that is not supported by TestComplete. Equally we may have objects like toolbar buttons, icons that aren’t supported by TestComplete. To automate test on these types of applications, we can use Find Image feature. What do we mean when we talk about automation using the Find Image feature? Using the Image of a particular control, window or object, our script will find the position of the object and then performs an action on...

Sometimes with test automation tools it’s difficult not to jump to the conclusion that they aren’t suitable for the job you want them to do. Usually this because of the steep learning curve and the difficulties associated with working out how best to approach the problem you are trying to resolve. One of the most important aspects with any tool is it’s ability to identify objects in the application you’re trying to automate. When you can’t identify the object you’re stuck. With Test Complete you may come across instances where it won’t recognize the control or window in your application. This is because Test Complete may not have in-built support for those objects. So you may think it is impossible...