If you’re still wondering about any of these bits then maybe it’s worth going back and looking at the Getting Started Module. If you’re happy with this then let’s walk through the steps you’ll need to follow to build your first automated test in TestComplete.
Create your Project suite, by clicking on the ‘New Project Suite’ button (1) and then enter the name for this suite. Once that’s created click on the ‘New Project’ button (2). It’s a bit back to front but you’ll be creating more Projects than Project Suites so it’s kind of makes sense to have the ‘New Project’ button on the left.
* – we wont get into scripting in this course but we might touch on the odd little bit of code so we may as well select Python at this stage.
Then click ‘Finish’ and we’ll have our first Project which is contained with our first Project Suite.
Before we go any further we’ll need an application to test. To make our lives easy we’re going to use an application called Calc Plus from Microsoft.
Microsoft don’t actually provide this as a download’able application anymore but you will find it on sites like ‘download.cnet.com’.
We’re using Calc Plus because it exposes a lot of it’s object information to TestComplete. We’re not using the default calcualtor supplied with Windows because this one doesn’t expose everything we need. Calc Plus just makes our life easier as we start out learning TestComplete.
Next we’ll create our first test. Our first test will be a mixture of adding test steps manually and recording parts of the test too.
To start off then we’ll manually add a few test steps before we record some test steps.
Then right click on the ‘StartCalc’ test in project explorer and select run start calc. This’ll just make sure we have Calc Plus running so that we can complete the next step.
You should see the recording tool bar open as TestComplete records your actions. And then record a few actions in Calc Plus (e.g. click the keys 2 * 2). Do NOT close the Calc Plus application at this point.
Then click stop on the recording tool bar.
At this point we’ve created all the component tests we need to run a full test scenario. All we need to do is link these together and run them. We do this at the project level by adding multiple project test items that call these tests in sequence.
And that’s it. Our first automated test. Created using a combination of building keyword tests manually (using drag and drop) and by recording tests. We’ve built the project in a modular fashion with three test cases pulled into the project list for execution. This way we can reuse these tests in other scenarios as we build out our test cases.