Test Complete Made Easy Book 6w3s3

TestComplete Made Easy by Lino Tadros - Falafel Software Inc.

Welcome to TestComplete Made Easy, the new guide to TestComplete, the award winning automated testing tool from AutomatedQA Corp. We hope you enjoy the book as much as we, at Falafel Software, enjoyed creating it. the latest version of this book and the example source files: http://www.automatedqa.com/testcomplete-book Lino Tadros President & CEO Falafel Software Inc. www.falafel.com

TestComplete Made Easy Copyright © 2008 AutomatedQA Corp. - 1.0 Release All rights reserved. No parts of this work may be reproduced in any form or by any means - graphic, electronic, or mechanical, including photocopying, recording, taping, or information storage and retrieval systems - without the written permission of the publisher. Products that are referred to in this document may be either trademarks and/or ed trademarks of the respective owners. The publisher and the author make no claim to these trademarks. While every precaution has been taken in the preparation of this document, the publisher and the author assume no responsibility for errors or omissions, or for damages resulting from the use of information contained in this document or from the use of programs and source code that may accompany it. In no event shall the publisher and the author be liable for any loss of profit or any other commercial damage caused or alleged to have been caused directly or indirectly by this document. Printed: July 2008

Publisher AutomatedQA Corp. Authors Alain "Lino" Tadros Eric Holton Steve Trefethen Technical Editors Noel Rice Drew Wells Cover Designer Matt Kurvin Team Coordinator Noel Rice Production Falafel Software Inc.

Special thanks to: All the team at AutomatedQA worldwide for creating a magnificant piece of software in TestComplete. The authors also would like to thank the Falafel team in Colorado, Texas, California and Washington for their , guidance and recommendation on the subjects of the manual. Falafel would like to thank Mr. Derek Langone and Mr. Drew Wells for their trust and belief in the quality of Falafel Software's work. Falafel would also like to thank Mr. Bobby Edgar for his continuous during the training summits and for being a great friend to Falafel for many years. Last but not least, thank you to all our families for their and patience while we wrote the book

4

TestComplete Made Easy

Table of Contents Foreword

9

11

Part I Introduction 1 Introduction ................................................................................................................................... to TestComplete

11

2 Who Should ................................................................................................................................... Read this Book

11

3 What Do................................................................................................................................... You Need to Have Before You Read this Book?

12

4 What Do................................................................................................................................... You Need to Know Before Reading this Book?

13

5 How the ................................................................................................................................... Book is Organized

13

17

Part II AutomatedQA 1 History ...................................................................................................................................

17

2 Product ................................................................................................................................... Offerings

17

Part III Overview of Testing and TestComplete

23

1 Objectives ...................................................................................................................................

23

2 Terminology ...................................................................................................................................

23

3 Types of................................................................................................................................... Testing

23

4 Before You ................................................................................................................................... Begin

24

5 Your Most ................................................................................................................................... Important Test

26

6 Summary...................................................................................................................................

26

29

Part IV TestComplete IDE Environment 1 Objectives ...................................................................................................................................

29

2 Menus and ................................................................................................................................... Toolbars

29

3 s and ................................................................................................................................... Workspaces

31

Project Explorer

.......................................................................................................................................................... 31

Object Browser

.......................................................................................................................................................... 33

Process Tree Pane ......................................................................................................................................................... 34 Object Properties ......................................................................................................................................................... Pane 36 Object Recognition ......................................................................................................................................................... 42 Introduction

......................................................................................................................................... 42

White-Box Applications ......................................................................................................................................... 43 Editor

.......................................................................................................................................................... 46

Code Completion ......................................................................................................................................................... 46 Bookmarks

......................................................................................................................................................... 47

Editor Options ......................................................................................................................................................... 48 Debugging

......................................................................................................................................................... 50

Breakpoints

......................................................................................................................................... 50

Call Stack

......................................................................................................................................... 51

Locals

......................................................................................................................................... 52

Watch List

......................................................................................................................................... 53

4 Summary...................................................................................................................................

57

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Contents

5

Part V Projects and Suites

59

1 Objectives ...................................................................................................................................

59

2 Project Anatomy ...................................................................................................................................

59

3 New Project ................................................................................................................................... Wizard

62

4 Hands on................................................................................................................................... Lab: Create a Simple Test

64

5 Summary...................................................................................................................................

65

Part VI Project Items

67

1 Objectives ...................................................................................................................................

67

2 Project Items ...................................................................................................................................

67

Win32 Tested Applications .......................................................................................................................................................... 68

3 Summary...................................................................................................................................

Part VII Test Log

70

72

1 Objective...................................................................................................................................

72

2 Script Log ...................................................................................................................................

72

3 Emailing................................................................................................................................... Result

73

4 LockEvents ...................................................................................................................................

74

5 Summary...................................................................................................................................

75

Part VIII Named Mappings

77

1 Objectives ...................................................................................................................................

77

2 Map to Object ...................................................................................................................................

77

3 Highlight................................................................................................................................... Objects

86

4 Mapping................................................................................................................................... Dialog

88

5 Aliases in ................................................................................................................................... Scripts

89

6 Summary...................................................................................................................................

89

Part IX Unit Testing

91

1 Objectives ...................................................................................................................................

91

2 ed ................................................................................................................................... Unit Testing Types

91

3 NUnit Example ...................................................................................................................................

92

4 Hands on ................................................................................................................................... Lab: Running a Unit Test

95

5 Summary...................................................................................................................................

97

Part X Manual Testing

99

1 Objectives ...................................................................................................................................

99

2 Setting up ................................................................................................................................... a Manual Test Project

99

3 Hands on ................................................................................................................................... Lab: Create a Manual Test

100

4 Hands on ................................................................................................................................... Lab: Scripting and Manual Testing

107

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

5

6

TestComplete Made Easy 5 Summary ...................................................................................................................................

111

113

Part XI Basic Record and Playback 1 Objectives ...................................................................................................................................

113

2 Overview ...................................................................................................................................

113

3 Recording ................................................................................................................................... Toolbar Anatomy

114

Adding Text

.......................................................................................................................................................... 115

Changing Recording .......................................................................................................................................................... Types 116 Pausing

.......................................................................................................................................................... 117

Stopping

.......................................................................................................................................................... 117

4 Hands on ................................................................................................................................... Lab: Perform a Basic Recording

117

5 Summary ...................................................................................................................................

118

120

Part XII Low Level Procedure 1 Objectives ...................................................................................................................................

120

2 Recording ...................................................................................................................................

120

3 Hands on ................................................................................................................................... Lab: MS Paint Test

123

4 Summary ...................................................................................................................................

127

129

Part XIII Stores and Checkpoints 1 Objectives ...................................................................................................................................

129

2 Region ................................................................................................................................... Comparisons

129

3 Files Comparisons ...................................................................................................................................

133

4 Object Comparisons ...................................................................................................................................

136

5 Hands on ................................................................................................................................... Lab: Comparing File, Picture and a Property

138

6 Summary ...................................................................................................................................

145

147

Part XIV Data-Driven Testing 1 Objectives ...................................................................................................................................

147

2 Overview ...................................................................................................................................

147

3 Modifying ................................................................................................................................... Scripts

147

4 Hands on ................................................................................................................................... Lab: Modifying Recording for Data-Driven Testing

149

5 Summary ...................................................................................................................................

152

154

Part XV Event Handling 1 Objectives ...................................................................................................................................

154

2 General................................................................................................................................... Events Definition

154

OnLogError

.......................................................................................................................................................... 156

3 Unexpected ................................................................................................................................... Windows

157

4 Hands on ................................................................................................................................... Lab: Create Unexpected Window Handler

158

5 Summary ...................................................................................................................................

162

Part XVI Working with Databases

164 Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Contents

7

1 Objectives ...................................................................................................................................

164

2 ADO

...................................................................................................................................

164

3 BDE

...................................................................................................................................

166

4 Hands on ................................................................................................................................... Lab: Query Database

166

5 Summary ...................................................................................................................................

174

Part XVII Web Page Testing

176

1 Objectives ...................................................................................................................................

176

2 Web Page ................................................................................................................................... Model

176

3 Naming................................................................................................................................... Conventions

177

4 Web Comparison ................................................................................................................................... Checkpoint

177

5 Web Accessibility ................................................................................................................................... Checkpoint

180

6 Finding................................................................................................................................... Web Page Elements

183

7 Dynamic ................................................................................................................................... HTML

185

8 Hands on ................................................................................................................................... Lab: Work with Web Pages

188

9 Summary ...................................................................................................................................

197

Part XVIII WebServices Testing

199

1 Objectives ...................................................................................................................................

199

2 Testing................................................................................................................................... against WSDL

199

3 WebServices ................................................................................................................................... Checkpoint

204

4 WebServices ................................................................................................................................... Testing Dialogs

209

5 XML Checkpoint ...................................................................................................................................

211

6 Hands on ................................................................................................................................... Lab: Testing a SOAP 1.2 Web Service

213

7 Summary ...................................................................................................................................

220

Part XIX HTTP Performance Testing

222

1 Objectives ...................................................................................................................................

222

2 Performance ................................................................................................................................... Testing Your Web Applications

222

3 HTTP Load ................................................................................................................................... Testing Options

222

4 Cookie ................................................................................................................................... Handling

224

5 Recording ...................................................................................................................................

224

6 Connections, ................................................................................................................................... Requests and Responses

227

7 Visual Creation ................................................................................................................................... of a Load Test

228

8 Analysis ................................................................................................................................... of the Test Log

230

9 Modifying ................................................................................................................................... HTTP Traffic

232

10 Hands on ................................................................................................................................... Lab: Working with HTTP Traffic

234

11 Summary ...................................................................................................................................

237

Part XX Remote Agent 1 Objectives ...................................................................................................................................

239 239

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

7

8

TestComplete Made Easy 2 Installing ................................................................................................................................... Remote Agent

239

3 Running ................................................................................................................................... Remote Agent

239

4 Configuring ................................................................................................................................... Remote Agent

241

5 Hands on Lab: Working with Remote Agent for HTTP Load Testing...................................................................................................................................

243

6 Summary ...................................................................................................................................

247

249

Part XXI Distributed Testing 1 Objectives ...................................................................................................................................

249

2 Network................................................................................................................................... Suites

249

3 Hosts ...................................................................................................................................

251

4 Jobs/Tasks ...................................................................................................................................

252

5 SynchPoints ...................................................................................................................................

253

6 Setup ...................................................................................................................................

253

7 Summary ...................................................................................................................................

260

262

Part XXII Forms 1 Objectives ...................................................................................................................................

262

2 Creating ...................................................................................................................................

262

3 Scripting ...................................................................................................................................

264

4 Summary ...................................................................................................................................

264

266

Part XXIII Best Practices 1 General...................................................................................................................................

266

2 Web Page ...................................................................................................................................

268

270

Part XXIV Cheat Sheet 1 Keyboard ................................................................................................................................... Shortcuts

270

2 Code Completion ...................................................................................................................................

272

3 Keyboard ................................................................................................................................... Handling in Recorder

273

4 Global Shortcuts/Changing ................................................................................................................................... Keyboard Emulation

274

Part XXV Professional Offering Index

278 280

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Foreword

9

Foreword TestComplete is more than just a test automation tool – it does that, of course, but it also integrates all the other aspects of testing – from organizing your manual tests, to doing unit testing and functional testing, and all the way to performance and load testing. That’s already a daunting amount of functionality, and then on top of that TestComplete s multiple programming languages and platforms and it comes out of the box bundled with for a long list of third party components. I almost forgot – you can also write your scripts in any of several standard scripting languages, too. That’s a lot of ground to cover. It’s easy to get started with TestComplete, but to take full advantage of everything that it has to offer you need not only to understand the built-in functionality, but you also need a deep knowledge of your testing trade and software development best practices. Anyone writing a book on TestComplete had better have that kind of depth and experience. To be honest, there just aren’t that many experts in this field that have such experience and are also proficient and entertaining technical writers. When I first heard a new book on TestComplete was going to be written I crossed my fingers that the superstar team at Falafel Software would be involved in some way. I just can’t think of anyone more appropriate for the task. Now that I’ve reviewed the first manuscript, I can see that I was right… (again). This book is terrific. It will definitely end up on the nightstands of all discerning TestComplete s. I strongly recommend it to everyone from novices just getting their feet wet, to expert testers ready to go to the next level. Finally, my deepest respects go to Lino Tadros, founder and CEO of Falafel software, for his expertise and his appreciation that all work and no fun is no way to go in life, and especially in testing. Thank you, Lino, for such a fine book and even more, thank you for being my friend and knowing all there is to know about Ouzo.

Atanas Stoyanov Original Founder of AutomatedQA

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Part

I Introduction

Introduction

1

Introduction

1.1

Introduction to TestComplete

11

About TestComplete Today automated testing plays a vital role in many software development projects. Automated testing has long been thought critical for large software development organizations, but is often considered to be too expensive and difficult to implement for smaller companies. AutomatedQA’s TestComplete breaks this stereotype. It delivers automated functional, unit, regression, manual, data-driven, object-driven, distributed and HTTP load, stress and scalability testing in one easy-to-use and totally integrated package at an affordable price. TestComplete is a full-featured environment for automated testing of Windows, .NET, Java, WPF (XAML) applications, web pages, web servers and web services. It has been designed to free developers and QA departments from the massive drain on time and energy required by manual testing. TestComplete offers systematic, automated, and structured testing, with superior for .NET, Java, Visual C++, Visual Basic, WPF (XAML), Delphi, C++Builder and web applications. It is equally oriented for testing 32-bit and 64-bit applications. With TestComplete you can also test PowerBuilder, FoxPro, Access and other applications. TestComplete is the ultimate solution to perform nightly tests and to help you get reliable daily builds of your software. TestComplete tools and features let every member of your team, developers and non-developers, no matter how technically savvy, contribute to your testing projects. Once you start using TestComplete, you will be able to turn every test run into a key contribution to your overall development efforts. TestComplete will keep your projects on schedule and on spec, the team confident, and the work 100% productive. With TestComplete you and your team can implement comprehensive software testing strategies, “automating the non-automatable” for maximum return on investment: “In my opinion, [TestComplete] is a must-have tool for any software developer who believes in applying a rigorous testing methodology to his products. The ability to work with Visual C++, Visual Basic, C++Builder, Delphi, Java and .NET applications means that you’re virtually getting several tools in one, and the wide variety of scripting languages means you can work in whatever language you’re most comfortable with. Even if you have no interest in automated testing procedures, [TestComplete’s] fascinating ability to ‘automate the non-automatable’ is sure to find a use on your desktop!” Dave Jewell, Delphi Magazine

1.2

Who Should Read this Book You should read this book if:

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

12

TestComplete Made Easy

· You have never used TestComplete and want to learn what it's all about. · You have worked in a QA environment and want to learn the AutomatedQA approach using TestComplete. · You have used TestComplete and want to make your knowledge more comprehensive.

1.3

What Do You Need to Have Before You Read this Book? This book was written for TestComplete 6.x.

Minimum System Requirements Ø Intel Pentium II 400 MHz or higher (Pentium III 800 MHz recommended). Ø Microsoft Windows 98, Windows ME, Windows 2000, Windows XP (both 32-bit and 64-bit editions), Windows Vista (both 32-bit and 64-bit editions), Windows Server 2003 (both 32-bit and 64-bit editions) or Windows NT 4.0 with Service Pack 6 or later. Important: If you use a computer that has several processors or a multiple-core processor (for example, dual-core U) and has Windows XP Service Pack 2, then you must install the Windows update #896256 in order for TestComplete to be able to record actions correctly. The update is available on Microsoft’s web site: http://.microsoft.com/kb/896256 Ø Microsoft Internet Explorer 5.0 or later. Ø Memory: 128MB of RAM (256MB or more recommended). Ø 250MB hard disk space. Ø VGA or higher resolution monitor. Ø Mouse or other pointing device.

Additional Requirements Ø To test Java Open Applications, you must have one of the following Java virtual machines installed on your computer: o MSVM, build 3309 or later. o Sun JDK (or JRE) v. 1.1.8 or later. o BEA JRockit 5.0. Ø To test .NET Open Applications, the Microsoft .NET Framework v. 1.0.3705 or later is required. Ø To execute TestComplete tests from test projects created in Microsoft Visual Studio 2005, Microsoft Visual Studio 2005 Team Suite ver. 8.0.50727.42 or later or Microsoft Visual Studio 2005 Team Edition for Software Testers ver. 8.0.50727.42 or later are required. Ø To install TestComplete’s Microsoft Visual Studio 2005 Team Foundation Integration package, Microsoft Visual Studio 2005 Team Foundation Server Release is required. Ø To perform load testing of web servers, Microsoft Windows 2000, Window XP, Windows Vista, Windows Server 2003 or Windows NT with Service Pack 6.0 or later is required. Also, it is recommended that your computer meets the following requirements: · Minimal Configuration

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Introduction

13

o Intel Pentium III 800 MHz o 256 of RAM (for 300 virtual s) · Recommended Configuration o Intel Pentium 4 3 GHz with HyperThreading o 1 Gb of RAM

1.4

What Do You Need to Know Before Reading this Book? TestComplete is a development environment, complete with an IDE (Integrated Development Environment) and programming languages. In this course you will not be simply clicking a few buttons and automatically recording your tests. Expect to perform development work, i.e. working with the IDE, writing script and working with relatively complex test configurations. The training is based on Windows platform testing. Although the product is capable of using 5 different scripting languages, the source code for the book is written in VBScript and JScript. This manual is used in TestComplete training classes along with lectures and hands-on lessons to give students a rich learning environment. When this material is presented in the classroom, the format is 50% lectures and 50% hands-on labs. While a printed manual can't reproduce the experience of listening to and working with a skilled trainer, it was written by those same trainers and we've done our best to make the text in this book an acceptable stand-in for the lectures. The chapter text (or lectures if we're lucky enough to be in class together) will provide you with the background knowledge on testing and TestComplete. The hands-on labs will provide the practical skills required to handle real-world testing scenarios and they are reproduced here exactly as they are presented in the classroom.

1.5

How the Book is Organized AutomatedQA This section includes a brief history of how AutomatedQA came into being and its mission. The section also includes a 1000 foot view of its award winning products TestComplete, Automated Build Studio, AQtime, AQdevTeam, TestExecute and TestRecorder.

Overview of Testing and TestComplete This section discusses an approach to organizing your efforts for maximum return on your automatedtesting investment. In this section you'll learn basic testing terminology, types of testing, strategies for organizing and communicating your testing results, how to build a "smoke test" and best practices for building durable tests that remain effective over time.

TestComplete IDE Environment This section introduces the basic tools you need to work effectively with TestComplete, including an exploration of the TestComplete environment and debugging basics.

Projects and Suites This chapter covers the structure of a TestComplete project and the parts that make up the various testing functionality included in a project. This chapter discusses the difference between a Project and Project Suite, the components of a Project, how to use the Project Wizard and how to create a simple test. Copyright © 2008 AutomatedQA Corp. - 1.0 Release

14

TestComplete Made Easy

Project Items This section provides an overview of all project item types with additional detail on the Win32 Tested Application.

Test Log This section discusses the test log and the types of messages available in TestComplete. We will learn how to email the test log and also how to reduce the size of the test log.

Named Mappings This section introduces Named Mappings and Aliases used to handle long object identifiers and to provide identifiers with meaningful names.

Unit Testing This section discusses unit testing, the types of unit test frameworks ed by TestComplete and provides an example of using an NUnit unit test.

Manual Testing This section looks at the structure of a TestComplete project and the parts that make up the various testing functionality included in a project.

Basic Record and Playback This section demonstrates how to perform basic record and playback tasks.

Low Level Procedure This section discusses TestComplete's Manual Testing features, how to construct a simple manual test using one of the provided sample applications and how to interact with manual tests from scripts.

Stores and Checkpoints This section explores how to compare various testing input including visual areas of the screen, files and objects.

Data-Driven Testing This section covers how the Data Driven Testing plug-in consumes common data types.

Event Handling This section explains how to respond to events that occur during testing and explains how to handle unexpected windows.

Working with Databases TestComplete includes general-purpose mechanisms for connecting to external databases. This section explains the connectivity options, how to connect and run queries during a test.

Web Page Testing Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Introduction

15

This section discusses how TestComplete represents web pages in the Object Browser, how to navigate between web pages and how web checkpoints are used. This section also talks about strategies for locating and testing dynamic HTML elements.

WebServices Testing This section demonstrates how to test a web service, including how to import web service meta data, calling simples methods, creating web service types and calling complex methods. This section also explains how to create a web service checkpoint.

HTTP Performance Testing This section explores HTTP performance testing and other types of performance testing (e.g. load, stress, scalability). You will also learn about HTTP traffic recording and modification.

Remote Agent Remote Agent is a tool that allows for the distribution of HTTP loads tests across a network of computers. This section explains how to install, configure and run Remote Agent.

Distributed Testing This section explains how tests are run on several computers at the same time.

Forms This section demonstrates how to create forms and manipulate them using script

Best Practices This section contains notes on best practices for testing in general and web pages in specific.

Cheat Sheet Here you'll find a handy reference to TestComplete general keyboard shortcuts, shortcuts for Code Completion, keyboard handling in the recorder, how to change global shortcuts and how to change keyboard emulation.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Part

II AutomatedQA

AutomatedQA

2

AutomatedQA

2.1

History

17

AutomatedQA offers software products and services for development and quality assurance projects worldwide. They create innovative, award-winning and affordable products for the entire software development lifecycle including TestComplete for test automation and AQtime, a sophisticated performance and memory profiler. AutomatedQA has an impressive list of customers ranging from huge teams in the world's largest organizations to progressive one-developer shops. AutomatedQA was founded in 1999 with headquarters in Las Vegas, Nevada, United States. AutomatedQA’s guiding principle is to be wholly focused on providing affordable and feature-rich developer tools and quality assurance technologies, and on providing s with fast and accurate product each and every day. What does affordable and feature-rich mean? It means bang for the buck. It means that their solutions tend to cost a fraction of their competitor's prices and offer more features. A good example is their automated testing tool, TestComplete. Some of their competitors charge separately for different test types like GUI testing, unit testing and load testing. TestComplete includes all ed testing types in one product with more features, for considerably less. It’s this combination of affordability and features that led Joel Spolsky, of joelonsoftware.com to write, “AutomatedQA's TestComplete is a great product and just as capable as the market leader at less than one-tenth the price. Why would anybody pay $6000 per seat for test automation?”. -- Joel Spolsky As a side note, AutomatedQA first customer ever in 1999, was no other that Falafel Software's QA Master, Mr. Eric Holton.

2.2

Product Offerings AutomatedQA offers several products in the Software Application LifeCycle Management sector. This include TestComplete, AQtime, Automated Build Studio, AQdevTeam and other derivatives of the main products like TestExecute, TestRecorder and AQtime for Linux.

AQtime Debug, Optimize, and Deliver Rock Solid Applications AQtime is AutomatedQA's award-winning performance profiling and memory and resource debugging toolset for Microsoft, Borland, Intel, Compaq and GNU compilers. The latest version of AQtime, AQtime 5, includes dozens of productivity tools that help you easily isolate and eliminate all performance issues and memory/resource leaks within your code by generating comprehensive and detailed reports for your .NET and Windows applications. AQtime s .NET 1.0, 1.1, 2.0, 3.0 applications and Windows 32- and 64-bit applications. AQtime is built with one key objective - to help you completely understand how your programs perform during execution. Using its integrated set of performance and debugging profilers, AQtime collects crucial performance and memory/resource allocation information at runtime and delivers it to you both in summarized and detailed forms, with all of the tools you need to begin the optimization process. This is all done without modifying the application's source code!

With AQtime's intuitive and -friendly interface and instrumentation in hand, you will quickly know the exact speed, memory usage, and application usability issues in your programs. As you

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

18

TestComplete Made Easy

optimize and improve your code, AQtime provides all the tools to compare and merge results so that over time, an exact and accurate "picture" of your application's state takes shape: · Monitor and report on all areas that could degrade your project’s performance and quality. · Assess the thoroughness of your tests by using Coverage Profiling. · Ensure that you make the right code improvements from day one. · Helps drill down to the exact line of source code that is responsible for performance or memory allocation inefficiencies.

Automated Build Studio Automate Software Builds, Tests and Deployment In the current state of software development, with projects becoming more and more complex, building, testing and releasing of software projects consumes an ever-increasing amount of time and resources. Automated Build Studio is a powerful build and release management system that provides an easy way to automate the software development build, test and release processes. Its intuitive interface and Copyright © 2008 AutomatedQA Corp. - 1.0 Release

AutomatedQA

19

unprecedented flexibility allows even inexperienced s to create complex visual macros which can automate repetitive or day-to-day tasks with the single click of a button.

Even though the product name includes the word “build”, you can use Automated Build Studio to automate any common or everyday tasks in your organization. Automated Build Studio contains over 540 built-in operations that will help you: · Compile applications · Create installation packages · Perform automated builds as scheduled tasks · Get and put files from/into version control systems · Label sources in version control systems · Compile help files · Create, modify and delete registry keys and INI file settings · Copy and move files to a location (network drive, Web site, FTP server, etc.) · Extract and pack files from/to ZIP and RAR archives · Run automated test scripts and profilers · Post bug reports to issue-tracking systems · Send and receive e-mail, ICQ and newsgroup notifications · Burn CDs and DVDs · COM and .NET components · Perform scripting operations in any of 3 scripting languages (VBScript, Jscript or DelphiScript) or many other operations...

With Automated Build Studio you can: · Automate your software builds · Perform distributed builds · Automate the process of application testing and profiling. · Create deployment packages and write them to CD and/or DVD. · Automate back-up processes. · Automate data and system consistency checks (for example, you can automate checking the free disk space or the availability of a Web service).

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

20

TestComplete Made Easy

TestExecute TestExecute allows you to execute scripts written with TestComplete and log test results on machines that do not have TestComplete installed - using a simple, resource friendly command-line utility. TestExecute gives QA departments the ability to test applications in real life environments - such as at customer sites - without the need to install TestComplete on the target machine.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

AutomatedQA

21

TestRecorder TestRecorder is a set of runtime libraries to be distributed with your 32-bit and 64-bit applications. Once incorporated into your app, TestRecorder fully records end- actions in the binary format. Later, the recorded data can be converted with TestComplete to an easily readable script code in VBScript, Jscript, DelphiScript, C++Script or C#Script. These scripts tell you exactly what a was doing during application execution - allowing you to accurately repeat the sequence of actions via TestComplete or TestExecute.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Part

III Overview of Testing and TestComplete

Overview of Testing and TestComplete

3

Overview of Testing and TestComplete

3.1

Objectives

23

In this section we'll discuss an approach to organizing your efforts to maximize the return on your automated testing investment. The content in this section is based on years of experience "in the trenches" from people who have worked to build a productive and efficient automated test environment. In this section you'll learn about: · Basic testing terminology · Types of testing · Strategies for organizing and communicating your testing results · How to build a "smoke test" · Best practices for building durable tests that remain effective over time.

3.2

Terminology First, let's define a few to help facilitate a discussion on testing: · QA - the Quality Assurance team · R&D - the Research and Development team developing the application being tested · Build - a specific revision of the application under test that is submitted to QA · Application - the code that will be tested using TestComplete

3.3

Types of Testing Manual Testing Manual Testing is where a tester methodically exercises the features of a product or product area without the aid of test automation. The single greatest strength of manual testing is that it is truly real-world testing, meaning that the tester can utilize the application under test the same way an end would. Through manual testing the tester can provide a wide variety of about the application under test not limited to simply reproducing bugs. The major weakness of manual testing is that it is time consuming, tedious and requires extended periods of very focused attention which can be very difficult to perform on a regular basis. Manual testing tends to be quite error prone, leading to situations where consistently reproducing a bug can be very difficult.

Functional Testing Functional Testing focuses on interactions with an application's interface (UI) via the mouse, keyboard or other input device with particular attention to how the application visually responds to input. The goal of Functional Testing is to methodically cover all of the various UI features exposed by an application. Functional Testing should be highly organized and structured in a manner that allows for additional tests to easily be incorporated as new features are added.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

24

TestComplete Made Easy

Unit Testing Unit Testing is testing that focuses on smaller atomic portions of an application. Typically, Unit Testing requires internal knowledge of how an application performs and seeks to test portions (objects, methods and function) of an application in isolation. In many cases, applications have to be designed with Unit Testing in mind in order for this type of testing to be truly effective. The benefit of unit testing is that it tends to force application developers to write smaller more well defined routines with fewer dependencies allowing for more highly specific tests to be developed.

Regression Testing Regression Testing is process of executing tests in a repeatable manner and comparing the latest results with previous test executions to ensure that the same outcome is achieved. Regression Testing is extremely important and is the means of realizing the value of test automation. Repeatedly executing tests over time allows you to the application is still performing in the manner in which it was intended.

Distributed Testing Distributed Testing is the act of farming different portions of a test out to separate machines for execution. Distributed Testing is useful for simulating real world interactions on a networked application such as a web site or web service and can exercise functionality designed to handle concurrent use of application resources including, but not restricted to data.

HTTP Performance Testing HTTP Performance Testing is the simulation of real-world interactions with a web application from multiple machines. TestComplete provides the ability to leverage networked computers and virtual s to simultaneously submit HTTP transactions to a web application.

Multi-Tier Explained In software development there are typically three Tiers which are used to describe various aspects of an application they are Client Tier, Middle Tier and Data Tier. These are each defined as: Client - The interface or presentation of an application and it's data which is typically covered through Functional Testing. Data Tier - The storage of an application's data which can be exercised by Functional Testing as well as Unit Testing Middle Tier - Refers to the portion of the application responsible for moving data back and forth between the Client and the Data Tiers. The code that resides in this Tier can be tested from either the Client Tier via Functional testing or through Unit Testing on the code in the Middle Tier itself. Keep in mind that these are not strict rules as to which type of testing should be used but more illustrative how the different types of testing can be used.

3.4

Before You Begin There are a few things you should know before diving into writing test automation using TestComplete or any test automation tool for that matter. In this section, we'll discuss the steps you should take to maximize the utility of your test automation efforts.

Communicating Test Results Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Overview of Testing and TestComplete

25

Now you might be thinking "huh? I haven't even started yet and I have to think about communicating my results?" The answer is a resounding YES! Unfortunately, Quality Assurance and test automation specifically, at least in the software world, tends to get a bad rap. Creating solid test automation that can stand up over time and provide valuable ongoing is a difficult task which leads a lot of people (read management) to think time and effort spent working on automation is wasted. To solve this problem you'll want to focus on getting your test results published quickly and consistently to prove that you're efforts are worth the investment. TestComplete provides some facilities for producing log output though you'll want to be sure and iron out your strategy from the start. For example, you may want to setup a web server where you can publish results in fact, TestComplete s exporting log results to HTML which could be a good starting place.

Plan your testing, but not that kind of planning... The planning we're referring to has to do with your choice of testing tool, TestComplete. Planning sounds like an obvious first task and although it's important to plan in of testing an applications features it's also important to plan with respect to the testing facilities available in TestComplete. You should gain a thorough understanding of TestComplete's features before you embark on writing test automation to avoid a situation where you're weeks into test development only to discover a feature that could have saved you numerous hours or days. TestComplete is rich with features that make test automation easier although like any development tool it provides many different ways to solve the same problem. For example, TestComplete has a powerful and indeed almost alluring, recorder making it easy to quickly create automated tests. While a test recorder is a great tool, recorded tests tend to be more brittle than hand written tests because they capture a single iteration at a given point in time and don't take into unexpected events like an error dialog popping up. The alternative is handwritten tests where you can methodically plan how the test will react in unexpected circumstances. The down side of handwritten tests is they tend to take longer to develop though over the long run they'll likely require less maintenance because of the tendency to design the test more rigorously. That said, it's not a bad idea to start with a recorded script and massage it into what amounts to a handwritten test.

Organizing your TestComplete projects TestComplete provides the ability to customize the Project Items that are included by default on a new project using Project Templates. In order to maintain consistency across your testing organization you should work towards creating a project template(s) that's pre-configured for your test environment. For example, if you're testing a Window 32-bit GUI application, create a Project Template that has the Win32 Tested Applications node with your application already added to it. Also, look closely at how you can utilize Aliases to avoid using long dotted object names like: Sys.Process("iexplore").IEFrame(0).Window("WorkerW", "", 1).Window( "ReBarWindow32", "", 1).Window("ComboBoxEx32", "", 1).Window( "ComboBox", "", 1).Window("Edit", "", 1)

Use a Source Control Repository TestComplete is a development tool and as such the projects, scripts, data etc. used in your tests should be kept under version control. If this is something you're already doing, skip ahead. If not, you should consider version control the next priority and work to get your test suites under version control. There are lots of options including some excellent Open Source projects which are freely available like Subversion, otherwise known as SVN. While it's beyond the scope of this document to discuss the specific merits of source control it's a subject that shouldn't be ignored.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

26

3.5

TestComplete Made Easy

Your Most Important Test Arguably, the first test you should focus on is a "smoke test". In this section we'll discuss what a smoke test is and provide guidance as to how to construct the test in such a way as to maximize its effectiveness.

Creating a Smoke Test Probably the most important test you'll write is your smoke test, at least it should be. Typically, the goal of a smoke test is to that the latest build delivered to QA is either worth further consideration or DOA (dead on arrival). The smoke test is crucial because of the time savings it can provide both R&D and QA. A good smoke test should: · Run quickly - a smoke test should not last for hours but minutes and test the most crucial functionality · Fail quickly - as soon as a failure is detected in the smoke test should end and trigger a failure notification · Cover a broad range of functionality, focusing on breadth not depth · Require minimal setup/configuration of the application under test · Be setup to run against every build · Adapt over time as the application under test evolves · Serve as a model for new test automation If you take the time to organize your smoke test to cover these goals you will undoubtedly save time and resources over the long run. Your smoke test should serve as an model that embodies your "best practices" from which your QA team can draw from for their own tests. If you've never written a smoke test before, start small. In the beginning simply get the smoke test to even a single piece of functionality consistently. Over time, work to increase its coverage but remain focused on the quality of the test. It's unacceptable to have a smoke test that can't run consistently and without problems.

Executing your tests regularly Once your smoke test is written and under version control the next step is to automate its execution. AutomatedQA has a product called Automated Build Studio which can automate your TestComplete tests and trigger them to execute when a new build is delivered to QA, a process called Continuous Integration or CI. In addition to Automated Build Studio there are Open Source CI servers such as CruiseControl.NET. The main benefit of a CI server is to reduce the amount of time it takes to execute your test automation as well as ensure that it executes against every build. By setting up a CI server you can not only alleviate your QA engineers from having to manually execute their tests but you'll quickly identify tests that are unable to consistently run to completion and may require closer scrutiny. In addition, many CI servers include a means of publishing test results providing for great visibility into the automation efforts.

3.6

Summary To best leverage your investment in test automation it's important to plan your overall testing strategy. Before diving in and unleashing the full power of TestComplete be sure to organize your communication

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Overview of Testing and TestComplete

27

strategy. Make communicating your results an important part of judging the success of your efforts. Also, treat your test development like any other software development project and use the tools available to maintain the quality and integrity of your test code.

the Goal Ultimately, the goal of test automation is to save time, money and improve quality. Test automation can relieve you of the task of manually testing existing functionality allowing you to focus attention on areas not already covered by automation. However, that statement is only true as long as your existing test automation is working, being executed consistently and the results are clearly communicated to the people who need them.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Part

IV TestComplete IDE Environment

TestComplete IDE Environment

4

TestComplete IDE Environment

4.1

Objectives

29

This section introduces the basic tools you need to work effectively with TestComplete. In this section you will: · Get familiar with the TestComplete environment. · Locate the Menus, Toolbars, Workspace areas, Object Browser and Project explorer. · Gain a solid understanding of the Object Browser. · Get familiar with the TestComplete Code Editor and all its features. · Gain the necessary knowledge of debugging in the TestComplete Editor.

4.2

Menus and Toolbars TestComplete Menus The TestComplete menus are no different from many Integrated Development Environments menus. From the figures below, you can see the File, Edit, View, Script, Tools and Help menus.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

30

TestComplete Made Easy

TestComplete Toolbar The TestComplete Toolbar is an easy way to get at TestComplete functionality or deeper menu items with only one click. Saving files, adding new units, recording, playing back, debugging, searching, formatting,etc...

The great thing about the toolbar is that it is customizable. So if you ever use a TestComplete functionality often and you don't see it on the toolbar, add it by right clicking on the toolbar and choose customize. Click on the Commands tab and drag any functionality you desire to anywhere on the toolbar. Once you drag a command to the toolbar, the icon is persisted there permanently.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

TestComplete IDE Environment

4.3

s and Workspaces

4.3.1

Project Explorer

31

The TestComplete IDE as you might expect consists of several pluggable windows that facilitate project management, code management, debugging, object browsing, main script and result logs workspaces.

The Project Workspace consists of two main windows, The Project Explorer and the Code Explorer.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

32

TestComplete Made Easy

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

TestComplete IDE Environment

33

The Project Explorer will allow you to see all projects in a suite and all the specific Project Items that are part of a specific Project. If you ever missed a Project Item from the Wizard at startup, you can always right click on a Project in the Project Explorer and choose Add New Item, where you will be presented with all TestComplete Project plug-ins to add to the project. The Code Explorer on the other hand, is a different view into your code base that enables you to navigate easily between functions in large files, rename functions, delete functions, sort functions by name in the tree, etc...

4.3.2

Object Browser The Object Browser is the most powerful part of TestComplete. It is where all the brains behind the TestComplete muscle reside. When you click on the Object Browser Window in TestComplete, the engine monitors all running processes on your machine and extracts vital information about each process for display as you can see below. You can filter the kind of processes you need to inspect or eliminate a category of processes by right-clicking on the Object Tree below on the left and filter processes. The Object Browser can also examine your system as a hardware unit and report on the U, U count, amount of memory (RAM) on the machine, Operation system is use, and other useful information, from a testing perspective.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

34

4.3.2.1

TestComplete Made Easy

Process Tree Pane The Process Tree Pane enables you to view all currently running processes on the machine and its toolbar on top allows you to filter the processes from running application to system processes to chosen testapps applications in your TestComplete project.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

TestComplete IDE Environment

35

By Right clicking anywhere in the Object Tree Pane, the popup menu appears with options to refresh the content of the tree, filter, terminate, copy to editor, sort and other useful functionality that we will discuss later in this chapter.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

36

4.3.2.2

TestComplete Made Easy

Object Properties Pane From the Object Tree Pane, invoke the 3rd menu option from the top called Object Properties..., that will invoke the following dialog when you need to quickly dissect a window on the screen.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

TestComplete IDE Environment

37

As a Lab for this part of the chapter, let's use the Object Browser, Object Tree Pane and Object Properties dialog to work with a Notepad window: 1. Open Notepad from the Windows directory or System32, depending of the version of Windows you are running. 2. View the Object Browser in TestComplete to determine that the process of Notepad has been detected by the Object Tree.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

38

TestComplete Made Easy

Notice that the process of Notepad is displaying three windows underneath the process and the Properties of the process itself are displayed on the right. The main Notepad window is actually the 3rd one down. The other two windows (IME and MSCTFIME UI) are other non-visible windows in Notepad for language direction reasons like Hebrew and Arabic, etc... 3. To make sure that the main window of Notepad is the 3rd one underneath the process, right click on it and choose Highlight on the Screen.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

TestComplete IDE Environment

39

Note: The Notepad application is brought to the front and the main window starts flashing with a red rectangle around the main window several times. 4. Notice in the Properties window that most of the properties have a blue color arrow next to them. That means these properties are READ-ONLY as far as the Object Browser is concerned.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

40

TestComplete Made Easy

5. One of the properties of that main window in Notepad is called "WndCaption" and it does not have the blue arrow next to it. That means it can be written to from the Object Browser. This property is actually the title of the window. Push the CTRL key and click inside of the edit area of the property. 6. Type "Welcome to TestComplete Training" and press [Enter].

7. Now go back to the Notepad application and view the title area of the application.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

TestComplete IDE Environment

41

Don't worry, you did not change Notepad forever :) it is only for this session until it is shutdown and started up again. 8. Now let's use the Finder tool to capture the Edit window in Notepad (The white area only with no Notepad title or menus). 9. Invoke the Object Properties dialog from the popup menu of the Object Tree. Drag the Finder tool to the white area in Notepad until you see a red rectangle around the edit portion only.

10.The Object Properties will automatically refresh and show all the properties TestComplete was able to see from the Window object in memory.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

42

TestComplete Made Easy

The button pointed to by the number 1 above will allow you to highlight the window object in-place in the Object Tree Pane as part of the Object Browser. This is a very handy button when your application windows are numerous and have a deep hierarchy as is the case for Internet Explorer. The button pointed to by number 2 above will allow you to highlight the object on the screen by flashing it several times, similar to step 3 above. 4.3.2.3

Object Recognition

4.3.2.3.1 Introduction

From the previous sample with Notepad, you probably noticed that TestComplete recognized a lot of properties of the main Notepad window as well as the Edit window. On the other hand, you probably also noticed that the Fields and Events tab were blank. Even the Methods tab had only methods pertaining to standard TestComplete functionality and actions. So where is Notepad own methods, Fields and events?

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

TestComplete IDE Environment

43

Well, TestComplete will recognize objects and will go as deep as the application will allow it to. That means, it is based on how the application was built, developed or compiled as to what TestComplete will be able to see inside of it. This brings up the topic of White Box Applications Vs. Black Box Applications. TestComplete will be able to automatically see deeply inside .NET and Java application without any changes to the application just because of the nature of metadata generation of .NET and Java application which are easy to reflect. Reflection is the ability to retrieve internal objects, properties, methods and events. So these are always called White Box Applications. Some Applications are written in C, C++ or Delphi, these applications are mainly Black Box applications but could be compiled in such a way to enable them to become White Box Applications. That would require compiling with Debug information enabled and the inclusion of some TestComplete files into the project to enable reflection of all program metadata.

4.3.2.3.2 White-Box Applications

While viewing the Object Browser, you will notice sometimes that a TestComplete icon will show next to a specific process. That sign identifies the process as "OPEN" and means TestComplete can reflect its content and get as much Runtime Type Information as possible.

In this sample, I used Visual Studio 2008 to generate a very simple C# based Windows application that adds two numbers together

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

44

TestComplete Made Easy

The only line of code in this example is: private void btnAddition_Click(object sender, EventArgs e) { TxtResult.Text = (Convert.ToInt32(TxtNumberOne.Text) + Convert.ToInt32(TxtNumberTwo.Text)).ToString(); }

In case you don't have Visual Studio, the executable is available through the book as "TCDotNetApp.exe".

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

TestComplete IDE Environment

45

Notice that TestComplete automatically figured out that we are dealing with a .NET application so it started using the built in "WINFORMSOBJECT" identifier to make it easier to reach all .NET methods, fields, events and properties associated with the application. At this point, if we had a function in the TCDotNetApp.exe called "Hello" that was never called from the Interface, it will still show up in the Methods tab. We would be able to call it directly from the script and it will be visible to TestComplete via reflection. Note: TestComplete has many built in recognition objects for Delphi VCL objects, Java Swing objects, XAML WPF objects and others...

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

46

TestComplete Made Easy

4.3.3

Editor

4.3.3.1

Code Completion The Code Editor in TestComplete is easy to use and productive to get the job done. One of the first features you will discover and love in the TestComplete Editor is the Code Completion feature. I am not sure how we used to write code before this feature was introduced in major development tools and in TestComplete. Instead of having prior knowledge of the objects you need to deal with in TestComplete or have access to the Help files, it is simple enough to let TestComplete do the job for you by entering the name of an object and placing a "." a period after the object. That will invoke the Code Completion window with all properties, methods and events available for that object. Sometimes you even have the need to invoke the Code Completion window in the middle of a statement. That is possible using the handy keyboard shortcut CTRL-SPACE.

Another great feature of the TestComplete Editor is the Parameter Completion feature. For example, when you need to know the count and type of a parameter that TestComplete recognizes, you can always open a parenthesis and key in CTRL-SHIFT-SPACE to bring up the Parameter completion window:

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

TestComplete IDE Environment

4.3.3.2

47

Bookmarks Another great feature of the editor in TestComplete is the ability to place bookmarks in script units opened in the IDE and be able to jump between them by a simple keystroke. You can set a bookmark by having the cursor on that line and pressing CTRL - SHIFT - and a number between 1 and 9.

In the figure above, please notice that the bookmarks are set on lines 5,15 and 18 (see the yellow glyph in the gutter). Also, the Bookmarks window at the bottom of the editor will list all set bookmarks with their numbers, their unit names and their line numbers. To jump to a specific

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

48

TestComplete Made Easy

bookmark at any time, press CTRL - 0 to 9 (without the SHIFT). To delete a bookmark, delete from the bookmark window or press CTRL-SHIFT- 0 to 9 again while the cursor is on the bookmark. 4.3.3.3

Editor Options From Tools | Options, you can get to the Editor options under s | Code Editor:

Under Display, you have the choice to change the Text specifications, background colors and margin, gutter styles and capacity and also whether you want to show line numbers or not. Another very useful feature of the editor in TestComplete is the ability to set Code Templates.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

TestComplete IDE Environment

49

Every Scripting language has it own templates. Above you will see that I added a new Template called TCTraining that contains a function name "test" with a comment in it. The script itself can be anything that you expect to use a lot in your testing. Notice also the little pipe "|" sign inside the brackets. The pipes indicates the position of the cursor in the code after the template has been inserted. Now lets go back to the editor and try to enter this template: 1. Choose an empty are between two function and press CTRL - J. The following code template helper will appear:

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

50

TestComplete Made Easy

2. Choose the TCTraining Template from the list and press Enter. The code is inserted in the script unit and the cursor is blinking right before the comment starts.

4.3.3.4

Debugging

4.3.3.4.1 Breakpoints

The Debugger capabilities in the TestComplete's Editor are very helpful in finding script errors, flow problems and also to evaluate the values of local and global variables.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

TestComplete IDE Environment

51

The Breakpoints window in TestComplete is very easy to use. You can set breakpoints in your editor by clicking in the gutter next to the line you want to set a breakpoint on or by pressing F5 while the cursor is on that line. In the Breakpoints window you can: · Enable or disable a specific breakpoint. That is better than deleting them and reentering them all over based on different debug sessions. · View the Location of the unit name it resides in and also the line number of where it resides. · Include a description to explain the goal behind using the breakpoint. · Finally, you have two powerful features in the breakpoints window which are Count and Condition. If you are debugging a "For Loop" that goes on for 1000 iterations, knowing that it will fail some time after 900 times, it would be wise to place a Count of 900 on the breakpoint instead of having to step over the breakpoint 900 times. When the count is not known but a condition has to be met, the Condition property can be set (e.g: x > 100). 4.3.3.4.2 Call Stack

The Call Stack window is very helpful when your scripts get called one from the other in a long chain of execution. During a break in execution, the Call Stack window will show the order of execution for the Copyright © 2008 AutomatedQA Corp. - 1.0 Release

52

TestComplete Made Easy

calling functions to get to that point of execution. The figure below shows the Call Stack at a break in execution. Usually that is good information for pinpointing the offending procedure. Unfortunately, in many cases "X" does not mark the spot like an Indiana Jones' movie, so the problem you are trying to figure out has already manifested itself way before the break in execution occurred. These are tougher bugs to figure out.

4.3.3.4.3 Locals

The Locals window is an easy and fast way to monitor the value of local variable inside of a specific function. Like in the figure below, we created 2 local variables, "myString" and "myNumber", and assigned specific values to both. To view their values, you only need to open the Locals window and they will be there as long as you are breaking inside of the function that contains them. So how do you view values of variables that are not local to a function? That is the functionality of the Watch List.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

TestComplete IDE Environment

53

4.3.3.4.4 Watch List

Notice in the screenshot below that the Global variable "myGlobal" did not show up in the locals window. This is correct, as the myGlobal variable is not a local of that function.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

54

TestComplete Made Easy

To evaluate the myGlobal variable, go to the Watch List window and add a new item by rightclicking in the window.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

TestComplete IDE Environment

55

The output in the Watch List window will allow you to monitor the value of that variable during the life of the execution session.

You can also use the Evaluate command available from the debug menu item in the editor:

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

56

TestComplete Made Easy

The Evaluate dialog displays the current value of the expression.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

TestComplete IDE Environment

4.4

Summary In this chapter: · You got a tour of the TestComplete environment. · Located the Menus, Toolbars, Workspace areas, Object Browser and Project explorer. · Gained a good understanding of the Object Browser. · Got familiar with the TestComplete Code Editor and all its features. · Gained the necessary knowledge for debugging in the TestComplete Editor.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

57

Part

V Projects and Suites

Projects and Suites

5

Projects and Suites

5.1

Objectives

59

This section looks at the structure of a TestComplete project and the parts that make up the various testing functionality included in a project. In this section you'll learn about: · The difference between a Project and Project Suite · Understand the components of a Project · Learn to use the Project Wizard · Create a simple test

5.2

Project Anatomy In TestComplete a Project is a container of test scripts and other Project Items used by the tests that make up the project. A Project Suite is a container of projects providing a mechanism to logically group related projects. To create a new project select File | New | Project... and you will be presented with the Create New Project dialog:

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

60

TestComplete Made Easy

The Create New Project dialog presents you with a number of pre-configured Project Templates that are geared towards specific types of testing. The templates are: · General Purpose Test Project - useful for a wide variety of test scenarios · Object Driven Testing - for working with custom data structures · Unit Testing - for running MSTest, NUnit, JUnit, DUnit or TestComplete unit tests · Distributed Testing - for managing test execution of projects on different computers · HTTP Load Testing - for load testing web server applications · [All Items] - template that includes all of TestComplete's available Project Items Once you click OK on the Create New Project dialog you will be presented with the New Project Wizard which allows you to further customize your New Project. For more details refer to the following section on the New Project Wizard. After creating a new project you can view all of its Project Items and sub items from the Project Explorer.

The various parts of a project are as follows: · MyProjectSuite - A Project Suite · MyProject - A Project

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Projects and Suites

61

· Script - A Project Item · Unit1 - A Project Item Element

Structure of Projects in TestComplete In TestComplete, Projects function as containers for different pieces of functionality related to testing and are organized on disk in a similar file/folder structure. In fact, removing a node from Project Explorer only removes it from the logical view presented by TestComplete and does not actually delete the item from disk which means you can easily add removed items back to a project. Here is the above project viewed from within Windows Explorer:

Projects Projects can contain the following: · Project Items: Provide for a specific type of testing. · Project Item Elements: The child nodes that represent testing functionality of the Project Item or serve to organize its contents. · Folders: Provides a means of organizing Project Items and Project Item Elements within a Project When a project is initially created you have the opportunity to specify which Project Items you want included. You can add and remove Project Items at any point. Adding them at the time a project is created is a matter of convenience.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

62

TestComplete Made Easy

Both Project Suites and Projects provide a logical view of the files and folders that make up the project. When removing nodes from the Project Explorer you are only removing them from this logical view. The actual files and folders are not deleted from disk and may be added back to the project using the right-click context menu and selecting Add | Existing Item...

Project Items Project Items make up the specific types of testing functionality or assist in performing various test operations. TestComplete includes a large collection of Project Items covering a wide variety of test functionality. You can easily add and remove Project Items using the right-click menu on the Project node of the Project Explorer.

5.3

New Project Wizard The New Project Wizard is provided as a convenience allowing you to configure a new project with a default set of testing functionality. It's not crucial to know up front all of the necessary Project Items that your project will require as Project Items can be added or removed directly from the Project Explorer after the project has been created.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Projects and Suites

63

Project Templates Initially, accepting the defaults on this dialog will be the preferred choice until your familiar enough with the available Project Items and can identify the ones you use most frequently at which point you can create a Project Template. To define a new template select the Project Items you use most frequently and click the Save As... button to create a new Project Template that will be available on the Create New Project dialog.

Best Practice - Setting up a Custom Template If you're testing a Windows Application you may want to setup a Project Template that's geared towards that type of testing. Project templates are located in \Bin\ProjectTemplates.xml making it easy to share templates with your entire team. In any testing organization it's important to establish standards like this to help maintain consistency across your testing organization. The following walkthrough demonstrates how to create a custom Project Template you may find useful for testing Windows applications: 1. Select File | New | New Project... 2. On the Create New Project dialog from the list of Templates select the [All Items] template 3. Click the Unselect All button at the bottom of the Project Items checkbox 4. Check the following Project Items: - Name Mapping - Stores

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

64

TestComplete Made Easy

- Win32 Tested Applications 5. In the left hand column on the dialog click Win32 Tested Applications 6. At the bottom of the Items list click the Add button to add a specific Windows application to test against 7. On the Create New Item dialog fill in the name of your application and click Next 8. In the Tested application edit box type the complete filename including path to the Windows application you wish to test or use the ellipsis (...) button to select the application 9. Click the Finish button 10. In the left hand column of the dialog click Select Project Items 11. Click the Save As... button 12. On the Save Template dialog enter a Template Name and Description and click OK to create a new project template that you can reuse

13. Click the Finish button

Deleting a Project Template TestComplete 6.0 does not have built-in UI for editing or deleting Project Templates. However, you can manually edit \Bin\ProjectTemplates.xml using a plain text editor such as Windows Notepad to delete or modify an existing template.

5.4

Hands on Lab: Create a Simple Test Creating a Simple Test 1. Select File | New | New Project...

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Projects and Suites

65

2. Select General Purpose Test Project and click the OK button 3. On the New Project Wizard click the Finish button, accepting the defaults

5.5

Summary In this chapter we covered the structure of a TestComplete project and the parts that make up the various testing functionality included in a project. You should be familiar with how to construct a Project Template for use across your organization for greater consistency and easy of use when creating new test projects.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Part

VI Project Items

Project Items

6

Project Items

6.1

Objectives

67

This section provides an overview of all project item types with additional detail on the Win32 Tested Application.

6.2

Project Items The Project Wizard Select Project Items tab allows you to select which project items are included in the project.

· ActiveX - This project item allows you to load an ActiveX object in TestComplete's memory space and use that object in your tests. For example you could use the Microsoft ADO Data Control to work with databases. · Events - This project item is used to hook to TestComplete events (and those of other application, such as ActiveX controls). This item is not required but is highly recommended. · HTTP Load Testing - Necessary for the creation of a load on a web server using TestComplete. · Low-Level Procedure Collection - A virtual folder for holding low-level (screen coordinate based tests) procedures. · Manual Test - A virtual folder for holding manual tests.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

68

TestComplete Made Easy

· Name Mapping - Used to map the name of an object to a shorter name (aliasing). · Network Suite - Used in distributed testing. · ODT - Object Driven Testing used to add pseudo class structure to script code. · Script - Holds a collection of script units. THIS ITEM IS REQUIRED. · Stores - Holds collections of checkpoints used in a project · Unit Testing - A virtual folder for holding Unit Tests. · Forms - A virtual folder for holding Forms (Forms presented to the during the test run, such a progress dialog, etc). · Web Services - A virtual folder for holding connection, methods and type of web services (Information from the WSDL file). · Win32 Tested Application - Holds information for managing the Application(s) under test.

6.2.1

Win32 Tested Applications The screenshot below the configuration of Win32 tested applications:

· Icon - Show the icon associated with the tested application · Launch - If checked, this application will be run if TestedApps.RunAll command is used (either from script or context menu). · Name - Is the name that TestComplete uses to refer to the tested application (must be a name that the scripting language can handle). · File Name - Is the name of the application on the disk. · Count - This is the number of instances of the application that TestComplete will launch. If the application is already running TestComplete will post a warning message in the Test Log. · File Path - By default, File Path is the relative path to the file name from the TestComplete project. · Run Mode - How the application is launched. · Parameters - Allows parameters to be set using the ellipses button.

Run Mode · Simple - Launches the application under the same as TestComplete. Parameters can be ed in Simple mode.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Project Items

69

· RunAs - Launches the application under the specified by the parameters dialog.

· Debug - Launches the application under the same as TestComplete, then TestComplete attaches to the application as a "debugger". The stack trace of any exception that occurs in the application while the test(s) are being run will be recorded in the TestLog. This option requires debug information in the application under test. · Profile - Launches the application inside of AQTime using the profile (or AQTime project) specified in the parameters dialog. For example code coverage profiling could be used to see how much of the code is being tested by your automated tests.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

70

6.3

TestComplete Made Easy

Summary In this section we had a brief overview of the project items of TestComplete. We also looked at Win32 Tested Application project item in more detail.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Part

VII Test Log

72

TestComplete Made Easy

7

Test Log

7.1

Objective This section discusses the test log and the types of messages available in TestComplete. We will learn how to email the test log and also how to reduce the size of the test log. In this section you will: · Learn about the basic Test (Results) Log. · How to view the Test Internet Explorer. · How to reduce test log size using LockEvents. · Learn how to email the test log.

7.2

Script Log Logs are used to persist from your tests including errors, warning messages and events as well as entire files and images. Logs are stored in a directory as XML files.

Log Tree This area will have a node for each Test Item level used to run the test. In the image above, for example, a project suite was run. The project suite is the top (root) node and each project is represented by the child of the project suite. The statuses of child items in the tree bubble up to the parent items. In the screenshot above you can see that errors flagged in child level items (the red X indicates the error status) have bubbled up to the project suite node. The context menu for the Log Tree contains menu items to handle the log output including Export to IE, Send Email and the ability to view closed Log s.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Test Log

73

Script Log This area contains messages coming from both TestComplete and the script code. The are six different types of messages: · Message - Can come from TestComplete or from the script code (Log.Message), will not cause the test to fail. · Warning - Can come from TestComplete or from the script code (Log.Warning), not necessary a failure for the test but could be an indicator for why a test failed. · Error - Can come from TestComplete or from the script code (Log.Error), this indicates a failure for the test. · Events - Usually comes from TestComplete but can come from the script as well (Log.Event), does not cause the test to fail. TestComplete generates an event for every mouse-click or keyboard entry in the test. · Image - Usually comes from script code (Log.Picture) but TestComplete can generate as well (Region Checkpoints). · File - There are two types of File log items. Log.File, will copy the file into the directory holding the log XML file and creates a hyperlink to the file. Log.Link just creates a hyperlink to the file without copying the file. The script log area may have a hierarchical structure via creating and pushing log folders onto the log ( Log.AppendFolder, Log.CreateFolder/Log.PushLogFolder, Log.PopLogFolder). All messages by default go into the last pushed log folder (i.e., the top of the stack).

7.3

Emailing Result Sending the result via email can be done either by script code (see help file for examples) or after the test run by selecting Send via Email... from the Log Tree context menu. Selecting Send via Email... creates an email with a multi-part hypertext file attachment. To preview what this file will look like, select View Results in IE from the context menu. View Results in IE also shows how TestExecute will display Test Results after a test run.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

74

7.4

TestComplete Made Easy

LockEvents With any long running test, the test result log will be filled with hundreds if not thousands of events.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Test Log

75

Most of the time, the tester is not interested in events unless there is a problem in the test run. TestComplete can eliminate events unless an error occurs. By adding Log.LockEvents to the script code, no events will be placed into the test log unless an error occurs. By default the last 20 events are logged, but this can be changed by adding a parameter to the Log.LockEvents command.

7.5

Summary In this section we learned about the test log and the different type of messages available in TestComplete. We learned how to email the test log and also how to reduce the size of the test log.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Part

VIII Named Mappings

Named Mappings

8

Named Mappings

8.1

Objectives

77

This section introduces Named Mappings and Aliases used to handle long object identifiers and to provide identifiers with meaningful names. In this section you will learn about: · Named Mapping. · Aliases and how they are different from Name Mapping · How TestComplete uses Alias and Name Mapping.

8.2

Map to Object TestComplete provides Named Mappings and Aliases to tame extremely long object identifiers that have meaningless default names. For example:

Sys.Process("Hello").1.2.Container1.Container2.button1

Clearly there are numerous issues with this identifier, its long and awkward not to mention we have no clue about the purpose or identity of "Container1", "Container2" or "button1". Named Mappings allow you to rename 1, 2, Container1, Container2 and button1 to useful names like My, myInside, myTabs, myPages and btnSubmit. The issue here is that you still need to type:

NameMappings.Sys.Process("Hello").My.myInside.myTabs.myPages.btnSubmit

TestComplete lets you create an Alias to represent this long string. If you create the Alias "btnSubmit", you only need to type:

Aliases.btnSubmit

Consider the AutomatedQA website Products link at the top of the page:

The standard full name for this HTML element is: Sys.Process("iexplore").Page("http://www. automatedqa.com/").(0).(0).Link(1). This does not tell anyone reading the script what HTML element the code is working with. There are a

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

78

TestComplete Made Easy

couple of ways to map an on-screen object in TestComplete: · Select the element in the Object Browser or Object Properties Window, and right-click for the context menu and select "Map the Object Name..." · Use the Map Object from Screen (

) button from the Tools toolbar.

1. Click the Map Object from Screen button to displays the Map Object dialog.

2. Use the finder tool (

) to select the Products link and push the OK button.

3. If the NameMapping project item is not in the project, TestComplete will ask if you want to add the NameMapping project item.

4. Click the Yes button.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Named Mappings

79

5. Click the OK button. 6. If the parent objects have not already been mapped, TestComplete will require them to be mapped before mapping the selected item.

7. Click the Yes button.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

80

TestComplete Made Easy

8. The Object Name Mapping dialog will be shown.

· In the caption of the Object Name Mapping dialog, there is an indicator that shows how many items need to be mapped in order to map the selected item. · The standard TestComplete name for the object is shown just below the caption. · The Selected Properties is used by TestComplete to find the on-screen object. · The properties that are selected for a given on-screen object are configured using the Templates button. · Any property that is listed in Selected Properties or Available Properties can be added or removed. · The OK button will add the object to the NameMapping project item and the Aliases part of the NameMapping project item. · The Skip button will add the object to the Mapped Object part but not into the Aliases part of the NameMapping project item. 9. Aliases are best explained by example, we are going press the Skip button for both the Sys object...

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Named Mappings

10.And the Skip button for the Process object.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

81

82

TestComplete Made Easy

11.Rename the Page Object to "HomePage" and click the OK button.

12.Press the Skip button for the Objects (Skip two times).

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Named Mappings

83

13.On the second object, TestComplete will say the it does not have enough information to make this unique in the NameMapping project Item. Although, TestComplete can work with non-unique objects, it is more reliable to have the object be unique.

14.Press the No button. 15.Find the Parent property in the Available Properties and click the ellipse button.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

84

TestComplete Made Easy

16.Select the Parent.Name property and add it to the Selected Properties.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Named Mappings

85

17.Press the Skip button. 18.Since there is the possibility that a new link could be added before the Products link, the Selected Properties will be changed from the standard properties. First, remove the Name property from Selected Properties, then add the innerText property. Change the Mapped Name to "ProductLink" and Press the OK button.

19.The NameMapping project item editor with all nodes expanded now looks like:

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

86

TestComplete Made Easy

In script code, the Product link can be referred to by the following code: Sys.Process("iexplore").Page("http://www.automatedqa.com/").(0).(0).Link(1)

or NameMapping.Sys.iexplore1.HomePage._0_._0_.ProductLink

or Aliases.HomePage.ProductLink

In this way, Aliases allow you to ignore on-screen objects that were used for design but are not necessary to the test automation process.

8.3

Highlight Objects During mapping or after the fact, objects being referred to can be highlighted on the screen. In the Name Mapping dialog, this is done by pressing the Highlight button.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Named Mappings

87

In the NameMapping project item editor, highlighting is done by selecting Highlight on Screen from the context menu (right-clicking).

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

88

8.4

TestComplete Made Easy

Mapping Dialog The parts of the Mapping dialog are listed below:

· Mapped Name - lets you define the name for an on screen object · Description - short note about the object · Selected Properties - the properties that are used to define this on screen object for name mapping. · Available Properties - additional properties that can be use to help refine the name mapping. · Template Name - which template that TestComplete used to define the Selected Properties initially. · Select - if the on screen object matches one than one possible template, this button allows you to choose which template to use. · Templates - Allows you to add/edit Templates. · Highlight - Highlights the currently selected object on the screen if possible. · OK - Add the selected object to both the Mapped Objects and the Aliases sections of the NameMapping project item. · Skip - Add the selected object to the Mapped Objects only. · Cancel - Cancel the mapping at this point (all items mapped before will still be mapped).

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Named Mappings

89

· Help - Brings up the help on this dialog.

8.5

Aliases in Scripts If you are recording a script and have the NameMapping project item in the current project, TestComplete will first try to use the Aliases project item in the recording. If that does not work, it will use the NameMapping project item. In manual coding you can use the Aliases as well. If the Alias object is available in the Object Browser, then TestComplete will present all the properties and methods for that object. If the object is not available in the Object Browser, TestComplete will present a smaller subset of methods and properties. This can be changed in the Options dialog (Tools | Options| Engines | Name Mapping) by selecting the Store CodeCompletion Information. This does increase the size of the NameMapping project item file but allows you to code without having the tested application open.

8.6

Summary We learned about what name mapping is and what it is used for. The difference between Aliases and Name Mapping was explained. And we learned how to map an object from the screen.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Part

IX Unit Testing

Unit Testing

9

Unit Testing

9.1

Objectives

91

This section discusses unit testing, the types of unit test frameworks ed by TestComplete and provides an example of using an NUnit unit test. In this section you will: · Learn about the types of unit test framework ed by TestComplete · See an example of using a Unit Test.

9.2

ed Unit Testing Types Running unit tests within TestComplete has several advantages: · Management gets a single report that includes both unit and automated tests. · Provides an easy way for Quality Assurance to run unit tests (in addition to Developers running unit tests). · Can make it possible to run unit tests as part of the build process. TestComplete s five different types of Unit Testing: · DUnit - A unit test framework for Delphi Applications, require that the test application be compiled as open and include the tcDUnit.pas file. · JUnit - A de-facto standard unit test framework for Java Applications. · MSTest - A unit test framework designed by Microsoft for unit testing .NET applications, comes with Visual Studio 2008 and Visual Studio 2005 Team Edition. · NUnit - An open-source unit test framework based on JUnit, used for unit testing .NET applications. · TCUnitTest - A unit test frame work that allows unit testing of any open application. Some of the unit test frameworks require that TestComplete know where the test runner application is located on the test machine. The information can be entered in the Options Dialog (Tool | Options from the main menu). From the Options Dialog select Engines | Unit Testing.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

92

9.3

TestComplete Made Easy

NUnit Example NUnit is a popular .NET unit testing framework (available at http://www.nunit.org). When it is installed, it includes a sample unit test assembly. 1. Add a Unit Testing Project Item to your project. 2. Add a NUnit Project Item under the Unit Testing Project Item.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Unit Testing

93

3. Click the ellipses button for the Assembly file name. Add the Assembly that holds the NUnit tests. 4. Push the OK button. This will open the NUnit editor in TestComplete.

5. Right-Click the NUnit1 Project Item and run the test.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

94

TestComplete Made Easy

The screenshots below show sample output and logging for the test run.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Unit Testing

9.4

95

Hands on Lab: Running a Unit Test 1. Create a new project 2. Add the "TestedApps" Project Item. 3. Add the "UnitTestingDemo" application to the project from the directory " \Samples\Unit Testing\C#\bin\" 4. Run the Application (Right-Click on the "UnitTestingDemo" Project Item).

5. Add a "Unit Testing" Project Item 6. Add a "TCUnitTest" Project Item to the "Unit Testing" Project Item.

7. Click the ellispe button (...) next to the process.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

96

TestComplete Made Easy

8. Select the "UnitTestingDemo" Process. 9. Select the Mode of "Run selected tests only". 10.Click the Load button. 11.Uncheck the "ShowNum" Method (this method has a UI which we do not want to handle in a unit test). 12.Click Run on the "TCUnitTest1" Project Item.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Unit Testing

97

Most of the work for Test Cases in the Unit Test is done by the developer in the Application.

9.5

Summary We learned about the types of unit test frameworks ed by TestComplete and how to use an NUnit unit test.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Part

X Manual Testing

Manual Testing

10

Manual Testing

10.1

Objectives

99

This section discusses TestComplete's Manual Testing features, how to construct a simple manual test using one of the provided sample applications and how to interact with manual tests from scripts. In this section you'll learn: · What a Manual Test is · How to setup a Manual Test Project · How to create a Manual Test · How to use script within a Manual Test

10.2

Setting up a Manual Test Project A Manual Test in TestComplete is a test that is performed by an individual who is directed by instructions presented on screen. TestComplete Manual Tests allow the person performing the test to indicate whether or not the test ed or failed and provide additional in the event of a failure.

Creating a New Manual Test There is no default template for creating a Manual Test so we'll walk through setting up a new project for Manual Testing: 1. From the main menu select File | New | New Project... which will display the Create New Project dialog 2. Select General Purpose Test Project and click OK 3. On the Project Wizard dialog click the Unselect All button then under Project Items check Manual Test and Win32 Tested Applications items

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

100

TestComplete Made Easy

You now have a test that's setup for Manual Testing.

10.3

Hands on Lab: Create a Manual Test The step-by-step walk-through below demonstrates how to create a manual testing project, set up a manual test, add steps to the manual test and how to run the manual test.

Creating a Manual Testing Project 1. Create a Project in TestComplete (with a new Project Suite)

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Manual Testing

101

2. Select General-Purpose Test Project Template and click OK 3. On the Project Wizard dialog click Unselect All and then check Manual Test and Win32 Tested Application

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

102

TestComplete Made Easy

4. Click Finish

Setting up a Manual Test Here we'll walk through setting up a Manual Test using a sample application provided with TestComplete called Orders.exe. 1. Right click on TestedApps and select Add | New Item... 2. Select Orders.exe (which is a sample application included with TestComplete) 3. Double click on ManualTest1 to open the editor in the Workspace

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Manual Testing

103

4. Change Test caption to "Manual Test" and Test description to "Hands on Lab" 5. Under Test instructions type "Orders application must be running to complete this test" 6. Under Test Steps right-click and select Preview Step Dialog... (click Yes on the prompt to save the dialog)

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

104

TestComplete Made Easy

7. Click Cancel to close the dialog

Adding Steps to a Manual Test 1. Under Test Steps click the Add Step

button

2. In the Step caption edit box type "open" 3. Add the directions for opening a table to the Step Instructions

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Manual Testing

4. Add another step using the Add Step Quantity"

button and set the caption to "Add Order and

5. Enter the following Step Instructions: a. Select Order | New Order... from the main menu b. Enter 2 in the Quantity Field c. that the Total Field equals 200

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

105

106

TestComplete Made Easy

Running a Manual Test In this section we'll walk through running a manual test and logging mock failures along the way. 1. In the Project Explorer right click ManualTest1 and select Run ManualTest1 2. Click Begin Test 3. Click Fail 4. Enter "Unable to find table" in the comment field 5. Click Try Again 6. Follow the reset of the step's instructions 7. Click Success 8. Click Fail on the next step 9. Click Continue At this point, you should see the following test log:

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Manual Testing

10.4

107

Hands on Lab: Scripting and Manual Testing In this section we'll illustrate using Scripts with manual tests and cover how to hook Manual test events.

Using Manual Tests from Script Code 1. Create a new TestComplete project. 2. Double click Unit1 under the Scripts node in the Project Explorer to open the code editor. VBScript is used in this example and your code may vary if you're using another scripting language. 3. In the Main routine, add a blank line under the "Enter Code Here" comment 4. Press Ctrl-Space to display the Code Completion window 5. Select TestedApps from the list. Note: Once the list appears you can begin typing to select the item from the list.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

108

TestComplete Made Easy

6. With the cursor at the end of TestedApps type a period "." to invoke the Code Complete again and select Orders 7. Type another period and select Run 8. Press Return to add a new blank line below TestedApps.Orders.Run() 9. Press Ctrl-Space to display the Code Completion window 10.Select ManualTest1 11. Type "." and select Start 12. Press Return to add a new line below ManualTest1.Start 13. Press Ctrl-Space to display the Code Completion window 14. Select TestedApps 15. Type a period "." and select TerminateAll

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Manual Testing

109

Script Interactions with Manual Tests In this example, we'll illustrate using Events and Script to interact with a during a Manual Test. This example will build upon the Manual Test created in the previous step. 1. With the previous project still open expand the Events node in the Project Explorer 2. Double click the GeneralEvents node

3. In the Workspace under Available Events expand the Manual Testing Events node

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

110

TestComplete Made Easy

4. Double click the OnBeforeStep event to add the event to your test 5. Under Events to Handle scroll the list down and locate the Manual Testing Events node 6. Click on the OnBeforeStep item then click the New button

7. Click OK on the New Routine dialog to add a new function to the Unit1 test script 8. In your Unit1 script file add a new blank like below the function declaration and type 'BuiltIn. ShowMessage("Hi from script")'

9. Run the Project and click the Begin Test button. Notice the ShowMessage dialog appears:

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Manual Testing

10.5

111

Summary In this section, we learned about TestComplete's Manual Testing features and constructed a simple manual test using one of the provided sample applications. We also illustrated how you can interact with manual tests from scripts.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Part

XI Basic Record and Playback

Basic Record and Playback

11

Basic Record and Playback

11.1

Objectives

113

This section demonstrates how to perform basic record and playback tasks including: · Understanding the recording toolbar. · How to starting a recording. · How to use buttons on the Recording Toolbar. · Perform a basic recording.

11.2

Overview TestComplete has rich Record/Playback functionality allowing you to quickly record new test scripts. TestComplete has several options that allow you to control how recording is performed. To view/change these options select Tools | Options... and click the Engines folder and select Recording. You should see the following options:

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

114

11.3

TestComplete Made Easy

Recording Toolbar Anatomy TestComplete Recording Toolbar The TestComplete recording toolbar looks like this:

The buttons are as follows: Capture Screen

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Basic Record and Playback

115

Add Text to Script Run Tested Application Add Checkpoint From the List Start Recording Stop Recording Pause Recording Record Low Level Procedure (screen coordinates) Record Low Level Procedure (window coordinates) Record Script Record an HTTP Task More Details Clicking the More Details button will expand the toolbar such that it displays Parent and Object name data for the item underneath the mouse cursor.

Starting a Recording To start a recording you must have a project loaded. You can load an existing project or start a new project. Once you have a project loaded there are two ways to begin a new recording: 1. Selecting Script | Record from the TestComplete main menu 2. Press the

Record toolbar button on the Test Engine toolbar:

11.3.1 Adding Text The Add Text to Script toolbar button allows you to insert either script or comments into the routine that's currently being recorded. Clicking this button displays the Add Text to Script dialog:

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

116

TestComplete Made Easy

Notice there is a checkbox at the bottom that allows you to indicate that the text is to be inserted as a comment. There is also a Pick Object... button that allows you to insert a line of code that references a specific onscreen object.

11.3.2 Changing Recording Types The recording toolbar has several buttons (see circled buttons below) that allow you to control the type of recording being performed.

The different recording types are: Record Low Level Procedure based on screen coordinates Record Low Level Procedure based on window coordinates Record a Script (default) Record an HTTP task To switch the type of recording simply click the appropriate button.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Basic Record and Playback

117

11.3.3 Pausing TestComplete allows you to pause in the middle of a recording by clicking on the Pause button. Pausing a test allows you to manipulate the application under test or change the environment without recording any of those actions into the script. To resume a paused test click the Start Recording button.

11.3.4 Stopping To stop a recording click the Stop button. Clicking the Stop button will close the Recording toolbar and restore the TestComplete main window leaving you in the Code Editor on the newly recorded script.

11.4

Hands on Lab: Perform a Basic Recording Recording a basic script 1. Create a new project and project suite using the General Purpose Test Project template:

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

118

TestComplete Made Easy

2. Click the

Record button on the toolbar

3. Click the Windows Start button 4. Select Run... 5. Type "notepad.exe" and click the OK button 6. Once Windows Notepad starts type "this is a test from TestComplete" 7. Click the

11.5

Stop button on the recording toolbar to end the recording

Summary In this section you learned how to perform basic record and playback tasks. We discussed the functionality available on the toolbar including how to record various types of activity.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Part

XII Low Level Procedure

120

TestComplete Made Easy

12

Low Level Procedure

12.1

Objectives In this section you will: · Get a clear understanding of when to use Low Level Procedure · Understand the choices for Low Level Procedure during recording · Understand the editing screen of Low Level Procedure after the recording session · How to play back a Low Level Procedure session successfully

12.2

Recording The reason you want to use the Low Level Procedure feature in TestComplete is when the need arises for recording specific mouse or keyboard operations on the screen for playback that are not automatically recorded during a regular recording session. For example, if TestComplete would record every mouse and keyboard operation automatically during each recording session, we would have ended up with thousands of lines of script identifying the mouse movement coordinates and clicks, while in most cases these are not necessary. On the other hand, if you are trying to Paint in a program like MS Paint or trigger a Hover event inside of Internet Explorer or FireFox, it is very much necessary that the recorder brings in the valuable mouse and keyboard coordinates, clicks and keystrokes. 1. Start a new project normally in TestComplete as shown in the figure below:

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Low Level Procedure

121

2. Make sure to enable Low Level Procedure Collection in the Project Wizard. If you forget, no worries. You will still be able to add it to the project after the fact using the Add New Item menu of the project in the Project Explorer.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

122

TestComplete Made Easy

3. When you start a recording session in TestComplete, you are presented with the recording tool bar shown below. On the recording tool bar are two buttons that enable Low Level Procedure recording: · The Screen Coordinates based button, which automatically set the coordinates for the recording as (0,0) to be the top most left of the screen. · The Window Coordinates based button, which sets the (0,0) coordinates starting from top most left window under recording. Tip: For a smoother playback and easier implementation between different resolutions on the screen, we recommend the "Window Coordinates" button to be used.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Low Level Procedure

12.3

123

Hands on Lab: MS Paint Test In this Lab, we will Low Level Procedure record MS Paint to sign a name on the screen. 1. Start a new Project 2. Enable Low Level Procedure Collection in the Wizard. 3. Start MS Paint in the Windows Directory or System32 directory depending on your version of Windows. 4. Start recording 5. Choose the Low Level Procedure - window coordinates button from the recording toolbar. 6. Drag the button from step 5 above to the MS Paint main window of the application until you see a red line around the entire MS Paint window. 7. The Create Project item dialog below will appear. Name your collection "MSPaintCollection" and click OK to close the dialog.

8. Start g your name or painting anything in the MS Paint application

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

124

TestComplete Made Easy

9. Upon completion of your masterpiece, stop the recorder from the TestComplete recording toolbar. 10.Notice that TestComplete did not record any of the clicks on the MS Paint application, but added one line of code to function Test1 to execute the collection of mouse movements and clicks collected during the recorded session.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Low Level Procedure

125

11.TestComplete collected all the mouse movement and clicks from the recorded session into an LLCollection item in the project called "MSPaintCollection" (see above). 12.Double click the MSPaintColection item in the project Explorer. 13.Notice the 900 + entries that were added to the collection to record all the mouse movement and clicks.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

126

TestComplete Made Easy

14.Each record contains the mouse operation (down, up, move), the number of the operation, the event name itself, the parameters of the mouse at that time (X & Y coordinates) and finally the delay in milliseconds between operations. 15.The nice thing about this workspace area is that you are able to modify 1 or a bunch of these 900 records at will. You can reduce the amount of time between operations, delete meaningless mouse movements that are not needed or event change the mouse coordinates on the screen after the fact.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Low Level Procedure

127

You can now try to playback the recording by running the routine. What happened? Are you surprised? Well, you probably saw the mouse moving on top of the TestComplete Editor in a pattern exactly as you expected would happen in MS Paint. That is because nothing caused the MS Paint application to come to the front or be activated. To fix that issue for your script, always activate the window that needs to be focused and top-most before running your low level procedures.

[JScript] function Test1() { Sys.Process("MSPAINT").Window("MSPaintApp", "*").Activate(); LLCollection1.MSPaintCollection.Execute( Sys.Process("MSPAINT").Window("MSPaintApp", "*")); }

12.4

Summary In this section we covered how and when to use a Low Level Procedure, recording choices, editing a recording and used the Low Level procedure workspace to change coordinates, delays and events. We also fixed a situation where the testing environment did not work as first expected.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Part

XIII Stores and Checkpoints

Stores and Checkpoints

13

Stores and Checkpoints

13.1

Objectives

129

This section explores how to compare various testing input including visual areas of the screen, files and objects. In this section you'll learn: · What a Region is. · How to create a Region Checkpoint. · How to do a File Comparison. · How to compare multiple properties of an object.

13.2

Region Comparisons Region Comparisons (Checkpoints) allow for the comparison of an area of the screen with a baseline. The baseline is stored in the Project Item called "Regions" under the Project Item called "Stores". A Region Checkpoint can be created either while recording or from the toolbar at test design time.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

130

TestComplete Made Easy

Creating a Region Checkpoint Interactively An example of creating a region checkpoint: 1. Open Internet Explorer to www.activefocus.net. 2. Open a project in TestComplete. 3. Click Create Region Checkpoint from the Tools toolbar of TestComplete. 4. Add the Stores project item if not already in the TestComplete project. 5. Use the Finder tool

to select the ActiveFocus logo

6. Name the picture "Logo" and click OK in the "Create Region Checkpoint" dialog. 7. Copy the code into a method in TestComplete. [VBScript] Sub RegionCompareExample If (Not Regions.Compare("Logo", Sys.Process("iexplore"). _ Page("http://www.activefocus.net/").Table(0).Cell(1, 0). _ Link(0).Image("nav_r1_c1"), False, False, True, 0)) Then Call Log.Error("The regions are not identical.") End If End Sub

[JScript] function RegionCompareExample() { if(!Regions.Compare("Logo", Sys.Process("iexplore"). Page("http://www.activefocus.net/").Table(0). Cell(1, 0).Link(0).Image("nav_r1_c1"), false, false, true, 0)) Log.Error("The regions are not identical."); }

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Stores and Checkpoints

8. Run the method. No errors should be part of the test log. 9. Double-click on the Regions project item to bring up the editor.

10.Click on the paint icon to edit the image.

11.Add a line from top left corner to bottom left corner.

12.Run the method again. There will be an error in the test log.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

131

132

TestComplete Made Easy

The log results show: · The first picture in the log is the expected image (the one stored in the Region project item). · The second picture in the log is the actual image. · The third picture in the log (the one shown) is the difference between the two images (shown in red pixels).

Creating a Region Checkpoint in Script Image comparison can also be done by using the Picture object of any OnScreen Object: [VBScript] Sub PictureComplareExample if not Sys.Process("iexplore").Page("http://www.activefocus.net/"). _ Table(0).Cell(1, 0).Link(0).Image("nav_r1_c1"). _ Picture.Compare(Regions.GetPicture("Logo")) then Call Log.Error("The OnScreen Object is different") End if End Sub

[JScript] function PictureCompareExample() { if (!Sys.Process("iexplore"). Page("http://www.activefocus.net/").Table(0). Cell(1, 0).Link(0).Image("nav_r1_c1").Picture(). Compare(Regions.GetPicture("Logo"))) { Log.Error("The OnScreen Object is different") } }

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Stores and Checkpoints

13.3

133

Files Comparisons TestComplete can compare files using: · A simple byte by byte comparison (Checkpoint) of two files. · Comparing file hash values (see Hash Values below). · A third-party difference engine. Settings for the third party difference engine can be set through Tools | Options to open the Options dialog, then select Engines | Stores.

Create a File Checkpoint To create a "File Checkpoint": 1. Select File Checkpoint from the "Tools" toolbar.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

134

TestComplete Made Easy

2. This will display the Create File Checkpoint dialog.

3. Select two files to compare. You can find them either on disk or using the "Files" Project Item. 4. If you know the files are different and want to compare them, click the "Calculator" button next to the Hash value edit box. 5. Press the OK button. 6. Copy the code to a new method. [VBScript] Sub FileCompareExample If (Not Files.Compare("Sample1.txt", "Sample2.txt", 0, True)) Then Call Log.Error("The files are not identical.") End If End Sub

[JScript] function FileCompareExample() {

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Stores and Checkpoints

135

if(!Files.Compare("Sample1.txt", "Sample2.txt", 0, true)) Log.Error("The files are not identical."); }

Using Hash Values If there are known difference between files, you can still compare the files by using a hash value. For example, consider the two xml files below: [XML (s.XML)] <> Eric Falafel 888 GOT-FALAFEL > <> Lino Falafel 888 GOT-FALAFEL > <> Drew AutomatedQA (978) 236-7900 > <> Derek AutomatedQA (978) 236-7900 >

[XML (Test.XML)] <> Eric Falafel 888 GOT-FALAFEL > <> Lino Falafel 888 GOT-FALAFEL > <> Drew AutomatedQA (978) 236-7900 > <> Derek AutomatedQA (978) 236-7900 > <> Test Test >

If there are known difference between files, you can still compare the files by using a hash value. To compare these two files, the code would look like the example below: Caution: The order that the files are compared makes a difference in the calculated Hash Value.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

136

TestComplete Made Easy

For example, consider the two xml files below. The hash value from TestComplete if "s. XML" is the first file in the comparison is 1812515919, if "Test.XML" is the first file the hash value is 1883158225. So the order of the comparison makes a difference in what the final hash value used in the Compare() function is.

[VBScript] Files.Compare("s.XML","Test.XML",1812515919,True)

[JScript] Files.Compare("s.XML","Test.XML",1812515919,true)

To get the hash value for two files: [VBScript/JScript] Hash = Files.CalculateHashValue("s.XML","Test.XML")

Note: Use the XML checkpoint to compare XML files.

13.4

Object Comparisons Object Comparisons allow the comparison of multiple properties of an Onscreen Object (and the children of that object, if desired). Create Object Checkpoint can be invoked with either the recording toolbar or the "Tools" toolbar:

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Stores and Checkpoints

· Use the finder icon

137

to select the onscreen object.

· If the object had children, TestComplete will ask if you want to save the properties of the child objects.

· Depending on the type of OnScreen object select, TestComplete will select certain properties for you for comparison. Any of the unselected properties can be added for comparison. [VBScript] Sub ObjectCompareExample If (Not Objects.Compare(Sys.Process("iexplore").

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

138

TestComplete Made Easy

Page("http://www.activefocus.net/").(0), "", True)) Then Call Log.Error("The objects are not identical.") End If End Sub

[JScript] function ObjectCompareExample() { if(!Objects.Compare(Sys.Process("iexplore"). Page("http://www.activefocus.net/").(0), "", true)) Log.Error("The objects are not identical."); }

· TestComplete will report the difference on the first object found with difference only.

13.5

Hands on Lab: Comparing File, Picture and a Property Comparing Files 1. Create a new project with Events, Script, Stores, and TestedApps Project Items. 2. Add the "StoresSampleProgram" to the TestedApps. 3. Add the "s.XML" to the "Files" Project Item (Copy to Stores). 4. Click the Record button in TestComplete. 5. Run the "StoresSampleProgram" 6. Open "s.XML" in the StoresSampleProgram" (File | Open...) 7. Save the file as "Test.XML" in the StoresSampleProgram (File | Save) 8. Click "Create File Checkpoint" in the recording toolbar. 9. Select "s.XML" as the first file. 10.Select "Test.XML" as the second file. 11.Press the OK button.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Stores and Checkpoints

12.Click the Add button on the Add Text to Script dialog. 13.Add a new (+ button) and enter information. 14.Save as "Test.XML" (File | Save). 15.Click Create File Checkpoint in the recording toolbar 16.Select "s.XML" as the first file. 17.Select "Test.XML" as the second file. 18.Press the OK button. 19.Click the Add button on the Add Text to Script dialog. 20.Close the "StoresSampleProgram" program. 21.Stop the recording. [VBScript] (Your recording maybe different) Sub Test1 Dim p1 Dim w1 Dim w2 Dim w3 Dim w4 Dim w5 TestedApps.StoresSampleProgram.Run Set p1 = Sys.Process("StoresSampleProgram") Set w1 = p1.Form1 Call w1.StripMainMenu.Click("File|Open...") Set w2 = p1.Window("#32770", "Open s XML") Call w2.Window("SHELLDLL_DefView").Window("SysListView32", "FolderView"). ClickItem("s.xml", 0) w2.Window("Button", "&Open").ClickButton Call w1.StripMainMenu.Click("File|Save...") Set w2 = p1.Window("#32770", "Save s File") Call w2.Window("ComboBoxEx32").Window("ComboBox").Window("Edit"). Keys("Test.XML") w2.Window("Button", "&Save").ClickButton If (Not Files.Compare("s.xml","C:\Training\Stores\Test.XML",0,True)) Then Call Log.Error("The files are not identical.") End If Set w2 = w1.WinFormsObject("1") Set w3 = w2.toolStrip1 Call w3.ClickItem("+") Set w3 = w1.WinFormsObject("dataGridView1") Call w3.ClickCell(4, "Name") Set w4 = w2.textBox1 Call w4.Click(17, 11) Call w4.Keys("Test[Tab]") Set w4 = w2.textBox2 Call w4.Keys("Test") Set w5 = w2.textBox3 Call w5.Click(15, 6) Call w5.Keys("Test") Call w4.Click(71, 4) Call w3.ClickCell(3, "Name") Call w1.StripMainMenu.Click("File|Save...") p1.Window("#32770", "Save s File").Window("Button", "&Save"). ClickButton p1.Window("#32770", "Save s File", 1).Window("Button", "&Yes"). ClickButton If (Not Files.Compare("s.xml", "C:\Training\Stores\Test.XML", 0, True)) Then Call Log.Error("The files are not identical.") End If Copyright © 2008 AutomatedQA Corp. - 1.0 Release

139

140

TestComplete Made Easy

w1.Close End Sub

[JScript] function Test1() { var p1; var w1; var w2; var w3; TestedApps.StoresSampleProgram.Run(); p1 = Sys.Process("StoresSampleProgram"); w1 = p1.Form1; w1.StripMainMenu.Click("File|Open..."); w2 = p1.Window("#32770", "Open s XML"); w2.Window("SHELLDLL_DefView").Window("SysListView32", "FolderView"). ClickItem("s.xml", 0); w2.Window("Button", "&Open").ClickButton(); w1.StripMainMenu.Click("File|Save..."); w2 = p1.Window("#32770", "Save s File"); w2.Window("ComboBoxEx32").Window("ComboBox").Window("Edit").Keys("Test.XML"); w2.Window("Button", "&Save").ClickButton(); if(!Files.Compare("s.xml", "C:\\Training\\Test.XML", 0, true)) Log.Error("The files are not identical."); w2 = w1.WinFormsObject("1"); w3 = w2.toolStrip1; w3.ClickItem("+"); w1.WinFormsObject("dataGridView1").ClickCell(4, "Name"); w3 = w2.textBox1; w3.Click(52, 5); w3.Keys("Test"); w3 = w2.textBox2; w3.Click(53, 11); w3.Keys("Test"); w2.Click(205, 102); w3 = w2.textBox3; w3.Click(52, 7); w3.Keys("Test"); w1.StripMainMenu.Click("File|Save..."); p1.Window("#32770", "Save s File").Window("Button", "&Save"). ClickButton(); p1.Window("#32770", "Save s File", 1).Window("Button", "&Yes"). ClickButton(); if(!Files.Compare("s.xml", "C:\\Training\\Test.XML", 0, true)) Log.Error("The files are not identical."); w1.Close(); }

22.Delete the "Test.XML" file from your system. 23.Run the new method. The test log will show a file comparison error.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Stores and Checkpoints

Comparing Regions (Images) 1. Click the record button in TestComplete 2. Run the "StoresSampleProgram" 3. Open "s.XML" in the StoresSampleProgram" (File | Open...) 4. Click the "Create Region Checkpoint" in the recording toolbar. 5. Use the finder tool

to select the grid from the "StoreSampleProgram"

6. Push the "OK" button. Copyright © 2008 AutomatedQA Corp. - 1.0 Release

141

142

TestComplete Made Easy

7. Click the "Add" button in the "Add Text to Script" dialog. 8. Close the "StoresSampleProgram" 9. Stop the recording. 10.Run the new method. [VBScript] Sub Test2 Dim p1 Dim w1 Dim w2 TestedApps.StoresSampleProgram.Run Set p1 = Sys.Process("StoresSampleProgram") Set w1 = p1.Form1 Call w1.StripMainMenu.Click("File|Open...") Set w2 = p1.Window("#32770", "Open s XML") Call w2.Window("SHELLDLL_DefView").Window("SysListView32", "FolderView"). ClickItem("s.xml", 0) w2.Window("Button", "&Open").ClickButton If (Not Regions.Compare("WinFormsObject_dataGridView", Sys.Process("StoresSampleProgram").WinFormsObject("Form1"). WinFormsObject("dataGridView1"),False, False, True, 0)) Then Call Log.Error("The regions are not identical.") End If w1.Close End Sub

[JScript] function Test2() { var p1; var w1; var w2; TestedApps.StoresSampleProgram.Run(); p1 = Sys.Process("StoresSampleProgram"); w1 = p1.Form1; w1.StripMainMenu.Click("File|Open..."); w2 = p1.Window("#32770", "Open s XML"); w2.Window("SHELLDLL_DefView").Window("SysListView32", "FolderView"). ClickItem("s.xml", 0); w2.Window("Button", "&Open").ClickButton(); if(!Regions.Compare("WinFormsObject_dataGridView", Sys.Process("StoresSampleProgram").WinFormsObject("Form1"). WinFormsObject("dataGridView1"),false, false, true, 0)) Log.Error("The regions are not identical."); w1.Close(); }

11.Add the line, see below, before the If in the code. [VBScript] Call w1.WinFormsObject("dataGridView1").ClickCell(1, "Name")

[JScript] w1.WinFormsObject("dataGridView1").ClickCell(1, "Name");

12.Run the method.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Stores and Checkpoints

Comparing A Single Property 1. Click the record button in TestComplete 2. Run the "StoresSampleProgram" 3. Open "s.XML" in the StoresSampleProgram" (File | Open...) 4. Click the "Create Property CheckPoint"

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

143

144

TestComplete Made Easy

5. the finder tool

to select the DataGrid.

6. Click the ellipse button (...) on the Property textbox. 7. Select the "RowCount" property.

8. Click the "Add" button to "Add Text to Script" dialog 9. Close the "StoresSampleProgram" 10.Stop the record. [VBScript] Sub Test3 Dim p1 Dim w1 Dim w2 TestedApps.StoresSampleProgram.Run Set p1 = Sys.Process("StoresSampleProgram") Set w1 = p1.Form1 Call w1.StripMainMenu.Click("File|Open...") Set w2 = p1.Window("#32770", "Open s XML") Call w2.Window("SHELLDLL_DefView").Window("SysListView32", "FolderView"). ClickItem("s.xml", 0) w2.Window("Button", "&Open").ClickButton If (Sys.Process("StoresSampleProgram").WinFormsObject("Form1"). WinFormsObject("dataGridView1").RowCount <> 5) Then Call Log.Error("The property value does not equal the template value.") End If w1.Close End Sub

[JScript] function Test3() { var p1; var w1; var w2;

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Stores and Checkpoints

145

var w3; TestedApps.StoresSampleProgram.Run(); p1 = Sys.Process("StoresSampleProgram"); w1 = p1.Form1; w1.StripMainMenu.Click("File|Open..."); w2 = p1.Window("#32770", "Open s XML"); w3 = w2.Window("SHELLDLL_DefView").Window("SysListView32", "FolderView"); w3.ClickItem("Log", 0); w3.ClickItem("s.xml", 0); w2.Window("Button", "&Open").ClickButton(); if(Sys.Process("StoresSampleProgram").WinFormsObject("Form1"). WinFormsObject("dataGridView1").RowCount != 5) Log.Error("The property value does not equal the template value."); w1.Close(); }

11.Run the routine.

13.6

Summary In this section we learned about Region (Images) and how to compare two regions. We learn how TestComplete compares files. And also how to compare multiple properties of an OnScreen object.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Part

XIV Data-Driven Testing

Data-Driven Testing

14

Data-Driven Testing

14.1

Objectives

147

This section covers how the Data Driven Testing plug-in consumes various common data types. In this section you'll learn about: · The data driven plug-in. · The different type of drivers available. · How to modify a script to use a driver.

14.2

Overview The Data Driven Plug-In (DDT) uses ADO to access different data elements, such a text files, Excel Spreadsheets, or any ADO compatible database. Once a driver has been initialized, the DDT plug-in provides a common interface to columns and rows in the data source. These methods/properties are: · ColumnCount: The number of column in the data source. · ColumnName: The name of a given column from the data source. · Name: The Name of the Driver. · Value: Returns the value of a column based on the column name or index. · EOF: Indicates if the driver is at the end of the data source. · DriveMethod: Iterates through all the records of the database, and executes a script routine for each records. · Next: Move to the next record in the data source The DDT plug-in s the creation of three different types of drivers, CVSDriver, ExcelDriver, and ADODriver: · CVSDriver is used to read text file such as comma delimited (default) or tab delimited (using a schema.ini file). By default the first row is the header information (or column names) for the driver. Example: Case,, 1,"","" 2,"1","1"

· ExcelDriver is used to read an Excel spreadsheet. The first row of the sheet is the header information for the driver. · ADODriver is a generic driver to read in ADO compatible data source.

14.3

Modifying Scripts You can modify a simple data entry script to use a outside data as an input source. For example suppose we have a script that enters a word into notepad:

[VBScript] Sub Test1 Copyright © 2008 AutomatedQA Corp. - 1.0 Release

148

TestComplete Made Easy

Dim p1 Dim w1 Dim w2 Set p1 = Sys.Process("Notepad") Set w1 = p1.Window("Notepad", "*") Set w2 = w1.Window("Edit") w2.VScroll.Pos = 0 Call w2.Click(144, 26) Call w2.Keys("TestComplete") End Sub

[JScript] function Test1() { var w1; w1 = Sys.Process("notepad").Window("Notepad", "*").Window("Edit"); w1.VScroll.Pos = 0; w1.Click(274, 105); w1.Keys("TestComplete"); }

We can modify the script to enter in multiple words from an outside data source. In the example below we create a list of customers from the AdventureWorksDB:

[VBScript] Dim MyDriver Sub Main Dim SQLStatement Dim ConnectionString ' Start Notepad TestedApps.Notepad.Run ' Limit to 100 records SQLStatement = "SELECT TOP (100) CustomerID, FirstName, LastName FROM" & _ " Sales.vIndividualCustomer" ConnectionString = "Provider=SQLOLEDB.1;Integrated Security=SSPI;" & _ "Persist Security Info=False;" & _ "Initial Catalog=AdventureWorks;Data Source=.\SQLExpress" ' Create Driver Set MyDriver = DDT.ADODriver(ConnectionString,SQLStatement) ' Call Method 100 times MyDriver.DriveMethod("Unit1.Test1") End Sub Sub Test1 Dim p1 Dim w1 Dim w2 Dim KeyStr Set p1 = Sys.Process("Notepad") Set w1 = p1.Window("Notepad", "*") Set w2 = w1.Window("Edit") w2.VScroll.Pos = 0 ' Create String with Customer Information KeyStr = MyDriver.Value("CustomerID")& "," & _ MyDriver.Value("FirstName")& "," & _ MyDriver.Value("LastName")& "[Enter]" Call w2.Keys( KeyStr) End Sub

[JScript] var MyDriver function Main() { try Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Data-Driven Testing

149

{ var SQLStatement; var ConnectionString; // Start Notepad TestedApps.Notepad.Run(); // Limit to 100 records SQLStatement = "SELECT TOP (100) CustomerID, FirstName, LastName FROM" + " Sales.vIndividualCustomer"; ConnectionString = "Provider=SQLOLEDB.1;Integrated Security=SSPI;" + "Persist Security Info=False;" + "Initial Catalog=AdventureWorks;Data Source=.\\SQLExpress"; // Create Driver MyDriver = DDT.ADODriver(ConnectionString,SQLStatement); // Call Method 100 times MyDriver.DriveMethod("Unit1.Test1") } catch(exception) { Log.Error("Exception", exception.description); } } function Test1() { var w1; var KeyStr; w1 = Sys.Process("notepad").Window("Notepad", "*").Window("Edit"); w1.VScroll.Pos = 0; w1.Click(274, 105); KeyStr = MyDriver.Value("CustomerID")+ "," + MyDriver.Value("FirstName")+ "," + MyDriver.Value("LastName")+ "[Enter]"; w1.Keys(KeyStr); }

As you can see there is very little modification of the initial recording needed to make it ready for Data Driven Testing. Most of the work is in the setup of the driving method. This example illustrated connecting to a MS SQL database using an ADO Driver.

14.4

Hands on Lab: Modifying Recording for Data-Driven Testing 1. Create a new project and project Suite. 2. Add the “All Pairs Sample” Sample Application 3. Under the Stores Project Item, right-click the Files and select Add New Item… 4. Add the TestData.Txt and the Schema.Ini files to the Stores, and click Yes on the Add Files to Stores dialog. 5. Run the "All Pairs Sample" application. 6. Click Record in TestComplete 7. Select 10 from the track bar in the sample application

8. Select Fair Share from the Allocation Strategy Combo Box

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

150

TestComplete Made Easy

9. Select All Stores from Store Selection Combo Box

10.Check mark the Greedy checkbox. 11.Click the Run Button 12.Select Fair Share from the Allocation Strategy Combo Box again. This is important for later as this causes the error message to be posted into the correct test case.

13.Stop the recording. [VBScript] Sub Test1 Dim w1 Dim w2 Set w1 = Sys.Process("All Pairs Sample").MainForm w1.WinFormsObject("trackBar1").wPosition = 10 Set w2 = w1.WinFormsObject("comboBox1") Call w2.ClickItem("Fair Share") Call w1.WinFormsObject("comboBox2").ClickItem("All Stores") w1.WinFormsObject("checkBox3").ClickButton w1.WinFormsObject("button1").ClickButton Call w2.ClickItem("Fair Share") End Sub

[JScript] function Test5() { var w1; var w2; w1 = Sys.Process("All Pairs Sample").MainForm; w1.WinFormsObject("trackBar1").wPosition = 10; w2 = w1.WinFormsObject("comboBox1"); w2.ClickItem("Fair Share"); w1.WinFormsObject("comboBox2").ClickItem("All Stores"); w1.WinFormsObject("checkBox3").ClickButton(); w1.WinFormsObject("button1").ClickButton(); w2.ClickItem("Fair Share"); }

14.Modify the checkbox line to get rid of the call to Click Button() substitute Checked = true. See the example code snippet below. [VBScript] w1.WinFormsObject("checkBox3").Checked = true

[JScript] w1.WinFormsObject("checkBox3").Checked = true;

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Data-Driven Testing

151

15.We now need to create a routine for reading the data file. In the main routine add a new line. 16.Type in "DDT.CSVDriver()" 17.Move the cursor inside the parentheses, type in "Files.FileNameByName()" 18.Inside the FileNameByName parentheses, type in “TestData.txt” (including the quotes). 19.Add a new line. 20.Type in "DDT.CurrentDriver.DriveMethod()". 21.In the parentheses, add “Unit1.Test1”. Your script should now look something like the example below: [VBScript] Sub Main DDT.CSVDriver(Files.FileNameByName("TestData.txt")) DDT.CurrentDriver.DriveMethod("Unit1.Test1") End Sub

[JScript] function Main() { DDT.CSVDriver(Files.FileNameByName("TestData.txt")); DDT.CurrentDriver.DriveMethod("Unit1.Test1"); }

22.Now to modify the inputs, change the input lines to: [VBScript] Sub Test1 Dim w1 Dim w2 Log.AppendFolder(DDT.CurrentDriver.Value("case")) Set w1 = Sys.Process("All Pairs Sample").MainForm w1.WinFormsObject("trackBar1").wPosition = DDT.CurrentDriver.Value("Iterations") Call w1.WinFormsObject("comboBox2"). ClickItem(DDT.CurrentDriver.Value("Stores")) Set w2 = w1.WinFormsObject("comboBox1") Call w2.ClickItem(DDT.CurrentDriver.Value("Strategy")) w1.WinFormsObject("checkBox3").Checked = (DDT.CurrentDriver.Value("Greedy") = "Y") w1.WinFormsObject("button1").ClickButton Call w2.ClickItem("Fair Share") Log.PopLogFolder() End Sub

[JScript] function Test5() { var w1; var w2; Log.AppendFolder(DDT.CurrentDriver.Value("case")); w1 = Sys.Process("All Pairs Sample").MainForm; w1.WinFormsObject("trackBar1").wPosition = DDT.CurrentDriver.Value("Iterations"); w2 = w1.WinFormsObject("comboBox1"); w2.ClickItem(DDT.CurrentDriver.Value("Strategy")); w1.WinFormsObject("comboBox2").ClickItem(DDT.CurrentDriver.Value("Stores")); w1.WinFormsObject("checkBox3").Checked = (DDT.CurrentDriver.Value("Greedy") == "Y");

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

152

TestComplete Made Easy

w1.WinFormsObject("button1").ClickButton(); w2.ClickItem("Fair Share"); Log.PopLogFolder(); }

23.Run the project. Caution: DO NOT TOUCH THE COMPUTER WHILE THE TEST IN RUNNING. There will be an unexpected window during the test run that TestComplete will handle.

The test log should look something like the example screenshot below:

14.5

Summary In this section we learned about how the DDT plug-in works and the different types of drivers. We learned how to modify a script to get values from the DDT driver.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Part

XV Event Handling

154

TestComplete Made Easy

15

Event Handling

15.1

Objectives This section explains how to respond to events that occur during testing. In this section you'll learn about: · What Events are. · How to create script code that responds to an event. · How to respond to unexpected windows.

15.2

General Events Definition Events occur based on certain actions and activities that occur in TestComplete, or some other application that is being tested. For example, every time an error is logged (by TestComplete or your script), TestComplete generates an OnLogError event. TestComplete has a rich set of events for handling common scenarios: General Events Name

Description

OnLogCloseNode

Occurs when a log folder is pop off the log.

OnLogCreateNode Occurs when a new log folder is appended on the log. OnLogError

Occurs when an error message is posted to the log.

OnLogEvent

Occurs when an event message is posted to the log.

OnLogFile

Occurs when a file is posted to the log.

OnLogLink

Occurs when a file reference (link) is posted to the log.

OnLogMessage

Occurs when a information message is posted to the log.

OnLogPicture

Occurs when a picture (image) is posted to the log.

OnLogWarning

Occurs when a warning message is posted to the log.

OnOverlappingWin Occurs when a overlapping window appears. dow OnTimeout

Occurs when a timeout expires in a project or project suite.

OnUnexpectedWin Occurs when an unexpected window appears. dow OnValidate

Occurs when the objects Validate method is called.

HTTP LoadTesting Events

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Event Handling

Name

155

Description

OnLoadTestingReq Occurs just before TestComplete send an HTTP request to the tested Web Server. uest OnLoadTestingRes Occurs just after TestComplete receives a response to an HTTP request. ponse Manual Testing Events Name

Description

OnBeforeStep

Occurs before the next step is display to the

OnGetNextStep

Occurs when TestComplete get the information about what the next step is to be executed

OnResume

Occurs when a manual test is about to be resumed.

OnStepFailed

Occurs when a click the Fail button in the Step Dialog

OnStepSuccess

Occurs when a click the Success button in the Step Dialog

OnSuspend

Occurs when the manual test is suspended

OnTestStep

Occurs when the stops the manual test.

NetworkSuite Events Name

Desciption

OnNetJobStateCha Occurs when a job's state changes. nge OnNetSuiteStateCh Occurs when the Network Suite's state changes. ange OnNetTaskStateCh Occurs when a task's state changes. ange OnNetVarChange Occurs when the value of a Network Suite variable changes. Test Engine Events Name

Description

OnStartTest

Occurs when a TestComplete test starts.

OnStopTest

Occurs when a test is over.

Web Testing Events

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

156

TestComplete Made Easy

Name

Description

OnWebBeforeNavi Occurs before Internet Explorer navigates to the specified Web Page gate OnWebSt Occurs when the of a web is starting. arted OnWebC Occurs when the ing of a web page is completed, failed or halted. omplete OnWebPageDownl Occurs after Internet Explorer loads the specified page (or frame) oaded OnWebQuite

Occurs before Internet Explorer closes.

15.2.1 OnLogError One of the most commonly used events, OnLogError can be used to gather addition information about the state of system when the error occurred. For example: 1. Expand the "Events" Project Item. 2. Double click the "GeneralEvents" Project Item. 3. Add an "OnLogError" handler to your project by clicking the new button next to the OnLogError event .

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Event Handling

157

4. Click the OK button in the "New Routine" dialog. TestComplete will create a new routine for you with two parameters "Sender" which represents the event handler controller and "LogParams" which contains information on the message just about to be posted to the TestComplete log file. Note: If you set LogParams.Locked = true, TestComplete will not post a message at all to the log. The following code will post a picture of the desktop to the test log along with a duplication of the error message:

[VBScript] Sub GeneralEvents_OnLogError(Sender, LogParams) Call Log.Picture(Sys.Desktop,LogParams.Str) End Sub

[JScript] function GeneralEvents_OnLogError(Sender, LogParams) { Log.Picture(Sys.Desktop,LogParams.Str) }

15.3

Unexpected Windows An unexpected window is defined by TestComplete as a modal dialog (a window that wants all keyboard and mouse activity for the application) that opens up over the application under test AND TestComplete is trying to interact with one of the other windows of the application under test. TestComplete has default handling for an unexpected window if "Ignore unexpected window" is not checked:

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

158

TestComplete Made Easy

Default Unexpected Window Handling Behavior TestComplete performs the following when an unexpected window appears: 1. Waits for the window to disappear on its own up to the Auto-Timeout period (10 seconds by default). 2. Calls the OnUnexpectedWindow event handler if any have been defined. 3. Logs an Error with a picture of the unexpected window. 4. If "Stop On Error" is checked (playback options), the test will stop. 5. If "Stop execution" is checked (playback options), the test will stop. 6. TestComplete will then attempt to close the unexpected window and continue the test. 7. Clicks the focused button (if checked in playback options). 8. Send an ESC key to the window (if checked in playback options). 9. Send an Enter key to the window (if checked in playback options). 10.Send a WM_CLOSE message to the window (if checked in playback options). 11.If TestComplete gets here without being able to close the unexpected window, the test will stop.

15.4

Hands on Lab: Create Unexpected Window Handler 1. Create a project in TestComplete. 2. Add the UnexpectWindow Application to the TestedApps project Item. 3. Click the record button in TestComplete.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Event Handling

159

4. From the recording toolbar, start the UnexpectedWindow application. 5. Enter "1" in to each of the edit boxes. 6. Click the "Calculate" button.

7. Close the application and stop the recording. 8. Comment out the code for the setting the value of the "numericUpDown2" control. 9. Run the created script. Example Script: [VBScript] Sub Test1 Dim w1 Dim w2 TestedApps.UnexpectedWindow.Run Set w1 = Sys.Process("UnexpectedWindow").UnexpectedWindow Set w2 = w1.WinFormsObject("numericUpDown1").WinFormsObject("UpDownEdit", "") Call w2.Click() Call w2.Keys("1[Tab]") 'Call w1.WinFormsObject("numericUpDown2").WinFormsObject("UpDownEdit", ""). Keys("1") w1.WinFormsObject("button1").ClickButton w1.Close End Sub

[JScript] function Test1() { var w1; var w2; TestedApps.UnexpectedWindow.Run(); w1 = Sys.Process("UnexpectedWindow").UnexpectedWindow; w2 = w1.WinFormsObject("numericUpDown1"); w2.Click(); w2.Keys("1[Tab]"); //w1.WinFormsObject("numericUpDown2").WinFormsObject("UpDownEdit", Keys("1"); w1.WinFormsObject("button1").ClickButton(); w1.Close(); }

"").

You will get an unexpected window. This unexpected window contains additional information that the developer can use to track down the issue. So, we will create a event handler for the unexpected window that will retrieve this information.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

160

TestComplete Made Easy

10.Expand the Events Project Item. 11.Double-click the GeneralEvents Project Item.

12.Click the new Button next to the OnUnexpectedWindow event in the GeneralEvents Editor.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Event Handling

13.Click the OK button. 14.In the event add the following code:

[VBScript] Sub GeneralEvents_OnUnexpectedWindow(Sender, Window, LogParams) Call Log.Message("Additional Error Information", _ Window.WinFormsObject("TextBox", "").Text) End Sub

[JScript] function GeneralEvents_OnUnexpectedWindow(Sender, Window, LogParams) { Log.Message("Additional Error Information", Window.WinFormsObject("TextBox", "").Text); }

15.Run the created script from above.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

161

162

15.5

TestComplete Made Easy

Summary In this section, we have learned about events and the types of events that TestComplete provides. We have also learned how to attach script code to events. During this time, we learned about one of the most important events caused by unexpected windows and different options for handling unexpected windows.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Part

XVI Working with Databases

164

TestComplete Made Easy

16

Working with Databases

16.1

Objectives TestComplete includes general-purpose mechanisms for connecting to external databases. You can connect to ActiveX Data Object (ADO) and Borland Database Engine (BDE) data sources. In this section you will learn: · How to connect to an ADO database. · The commands available to manipulate ADO and BDE data sources. · How to retrieve ADO data and use the data in your tests.

16.2

ADO ADO stands for "ActiveX Data Object". ADO allows TestComplete to access and manipulate data in a variety of data source (mostly databases). TestComplete offers two implementations to access ADO datasources. One route uses native Microsoft methods, the other through Borland (Codegear) methods. The table below shows the available methods: Microsoft

Borland

CreateCommand

CreateADOCommand

CreateConnection

CreateADOConnection CreateADODataSet CreateADOQuery CreateADOStoredProc CreateADOTable

The following Borland methods are specialized extensions of CreateADOCommand: CreateADODataSet, CreateADOQuery, CreateADOStoredProc, CreateADOTable. One of the hardest parts to using ADO is getting the connection string correct. You can get this information from the developer of the project you're testing, or look at http://www.connectionstrings.com.

Caution: TestComplete can not use the .NET-only connection string (for example the SqlConnection for SQL Server 2005).

To query a database using ADO: 1. Create an Connection to the database.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Working with Databases

165

2. Open the Connection. 3. Create an Query Command. 4. Execute the Query Command. 5. Do something with the returned RecordSet. 6. Close the Connection. The following example uses the AdventureWorkDB (http://www.codeplex.com/MSFTDBProdSamples/ Release/ProjectReleases.aspx?ReleaseId=4004) and SQL Server 2005. The example reads through the Sales table, logging a customer and number for each record.

[VBScript] Sub Main ' Create a new Connection object Set AConnection = ADO.CreateConnection ' Note that you can also create an ADO connection using the following code: ' Set AConnection = CreateObject("ADODB.Connection") ' Specify the connection string AConnection.ConnectionString = _ "Provider=SQLOLEDB.1;Integrated Security=SSPI;" & _ "Persist Security Info=False;" & _ "Initial Catalog=AdventureWorks;Data Source=.\SQLExpress" ' Activate the connection AConnection.Open ' Create a new Command object Set Cmd = ADO.CreateCommand ' To create an ADO command you can also use the following code: ' Set Cmd = CreateObject("ADODB.Command") ' Specify the connection Cmd.ActiveConnection = AConnection ' Specify command type and text Cmd.CommandText = _ "SELECT CustomerID, TerritoryID, Number, CustomerType," & _ " rowguid, ModifiedDate FROM Sales.Customer WHERE (CustomerType = ?)" Cmd.CommandType = adCmdText ' Create a new parameter Set Prm = Cmd.CreateParameter("@CustType",DB.adVarChar, DB.adParamInput) ' Specify the parameter value Prm.Size= 1 Prm.Value = "S" Cmd.Parameters.Append(Prm) ' Execute the command Set RecSet = Cmd.Execute ' Execute the command RecSet.MoveFirst While Not RecSet.EOF Log.Message(RecSet("CustomerID").Value & " has " & _ RecSet("Number").Value) RecSet.MoveNext WEnd AConnection.Close End Sub

[JScript] function Main() { try { var AConnection, RecSet, Cmd, Prm; // Create a new Connection object AConnection = ADO.CreateConnection(); // Note that you can also create an ADO connection using the following code: // AConnection = new ActiveXObject("ADODB.Connection"); Copyright © 2008 AutomatedQA Corp. - 1.0 Release

166

TestComplete Made Easy

// Specify the connection string AConnection.ConnectionString = "Provider=SQLOLEDB.1;Integrated Security=SSPI;" + "Persist Security Info=False;" + "Initial Catalog=AdventureWorks;Data Source=.\\SQLExpress"; // Activate the connection AConnection.Open(); // Create a new Command object Cmd = ADO.CreateCommand(); // To create an ADO command you can also use the following code: // Cmd = new ActiveXObject("ADODB.Command"); // Specify the connection Cmd.ActiveConnection = AConnection; // Specify command type and text Cmd.CommandType = adCmdText; Cmd.CommandText = "SELECT CustomerID, TerritoryID, Number, CustomerType," + " rowguid, ModifiedDate FROM Sales.Customer WHERE (CustomerType = ?)" // Create a new parameter Prm = Cmd.CreateParameter("@CustType",DB.adVarChar, DB.adParamInput); // Specify the parameter value Prm.Size = 1; Prm.Value = "S"; Cmd.Parameters.Append(Prm); // Execute the command RecSet = Cmd.Execute(); // Process the results RecSet.MoveFirst(); while (! RecSet.EOF ) { Log.Message(RecSet("CustomerID").Value + " has " + RecSet("Number").Value) RecSet.MoveNext(); } AConnection.Close(); } catch(exception) { Log.Error("Exception", exception.description); } }

For more information on ADO see Microsoft web site (http://msdn2.microsoft.com/en-us/library/ ms675532(VS.85).aspx)

16.3

BDE BDE stands for Borland Database Engine, is a legacy technology and is no longer ed by Borland. If for some reason you require connectivity using the BDE, find the latest version at "Borland Database Engine Developer " (http://info.borland.com/dev/bde/bdeupdate.html).

16.4

Hands on Lab: Query Database In this lab we are going to query the AdventureWorkDB. The example below will read the Sales table and extract a total sales figure for a given customer. The SQL to get the sales order details for any customer is the following parameterized query: SELECT * FROM Sales.SalesOrderDetail AS d INNER Sales.SalesOrderHeader AS h ON d.SalesOrderID = h.SalesOrderID WHERE (h.CustomerID = ?)

In the example we will build the code step-by-step, adding the following features as we go: Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Working with Databases

167

· Connect to the ADO datasource. · Create an ADO command. · Create a parameter for the ADO command. The parameter will contain the customer number. · Execute the command and get a result set. · Iterate the result set, calculate the total sales and log the amount. 1. Create an ADO connection to the server, run the script to make sure the connection string is correct. [VBScript] Sub Main ' Create a new Connection object Set AConnection = ADO.CreateConnection ' Note that you can also create an ADO connection using the following code: ' Set AConnection = CreateObject("ADODB.Connection") ' Specify the connection string AConnection.ConnectionString = _ "Provider=SQLOLEDB.1;Integrated Security=SSPI;" & "Persist Security Info=False;" & _ "Initial Catalog=AdventureWorks;Data Source=.\SQLExpress" ' Activate the connection AConnection.Open AConnection.Close End Sub

[JScript] function Main() { try { var AConnection, RecSet, Cmd, Prm; // Create a new Connection object AConnection = ADO.CreateConnection(); // Note that you can also create an ADO connection using the following code: // AConnection = new ActiveXObject("ADODB.Connection"); // Specify the connection string AConnection.ConnectionString = "Provider=SQLOLEDB.1;Integrated Security=SSPI;" + "Persist Security Info=False;" + "Initial Catalog=AdventureWorks;Data Source=.\\SQLExpress"; // Activate the connection AConnection.Open(); AConnection.Close(); } catch(exception) { Log.Error("Exception", exception.description); } }

2. Create an ADO command. [VBScript] Sub Main ' Create a new Connection object Set AConnection = ADO.CreateConnection ' Note that you can also create an ADO connection using the following code: ' Set AConnection = CreateObject("ADODB.Connection") ' Specify the connection string

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

168

TestComplete Made Easy

AConnection.ConnectionString = _ "Provider=SQLOLEDB.1;Integrated Security=SSPI;" & _ "Persist Security Info=False;" & _ "Initial Catalog=AdventureWorks;Data Source=.\SQLExpress" ' Activate the connection AConnection.Open ' Create a new Command object Set Cmd = ADO.CreateCommand ' To create an ADO command you can also use the following code: ' Set Cmd = CreateObject("ADODB.Command") ' Specify the connection Cmd.ActiveConnection = AConnection ' Specify command type and text Cmd.CommandText = "SELECT * FROM Sales.SalesOrderDetail AS d INNER " & _ "Sales.SalesOrderHeader AS h ON d.SalesOrderID = h.SalesOrderID " & _ " WHERE (h.CustomerID = ?)" Cmd.CommandType = adCmdText ' Create a new parameter AConnection.Close End Sub

[JScript] function Main() { try { var AConnection, RecSet, Cmd, Prm; // Create a new Connection object AConnection = ADO.CreateConnection(); // Note that you can also create an ADO connection using the following code: // AConnection = new ActiveXObject("ADODB.Connection"); // Specify the connection string AConnection.ConnectionString = _ "Provider=SQLOLEDB.1;Integrated Security=SSPI;" + "Persist Security Info=False;" + "Initial Catalog=AdventureWorks;Data Source=.\\SQLExpress"; // Activate the connection AConnection.Open(); // Create a new Command object Cmd = ADO.CreateCommand(); // To create an ADO command you can also use the following code: // Cmd = new ActiveXObject("ADODB.Command"); // Specify the connection Cmd.ActiveConnection = AConnection; // Specify command type and text Cmd.CommandType = adCmdText; Cmd.CommandText = "SELECT * FROM Sales.SalesOrderDetail AS d INNER " + "Sales.SalesOrderHeader AS h ON d.SalesOrderID = h.SalesOrderID" + " WHERE (h.CustomerID = ?)" AConnection.Close(); } catch(exception) { Log.Error("Exception", exception.description); } }

3. Create the parameter for customer number. [VBScript] Sub Main ' Create a new Connection object Set AConnection = ADO.CreateConnection ' Note that you can also create an ADO connection using the following code: ' Set AConnection = CreateObject("ADODB.Connection")

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Working with Databases

' Specify the connection string AConnection.ConnectionString = _ "Provider=SQLOLEDB.1;Integrated Security=SSPI;" & _ "Persist Security Info=False;" & _ "Initial Catalog=AdventureWorks;Data Source=.\SQLExpress" ' Activate the connection AConnection.Open ' Create a new Command object Set Cmd = ADO.CreateCommand ' To create an ADO command you can also use the following code: ' Set Cmd = CreateObject("ADODB.Command") ' Specify the connection Cmd.ActiveConnection = AConnection ' Specify command type and text Cmd.CommandText = "SELECT * FROM Sales.SalesOrderDetail AS d INNER " & " Sales.SalesOrderHeader AS h ON d.SalesOrderID = h.SalesOrderID " & _ " WHERE (h.CustomerID = ?)" Cmd.CommandType = adCmdText ' Create a new parameter Set Prm = Cmd.CreateParameter("@CustID",DB.adInteger, DB.adParamInput) ' Specify the parameter value Prm.Size= 4 Prm.Value = 676 End Sub

[JScript] function Main() { try { var AConnection, RecSet, Cmd, Prm; // Create a new Connection object AConnection = ADO.CreateConnection(); // Note that you can also create an ADO connection using the following code: // AConnection = new ActiveXObject("ADODB.Connection"); // Specify the connection string AConnection.ConnectionString = "Provider=SQLOLEDB.1;Integrated Security=SSPI;" + "Persist Security Info=False;" + "Initial Catalog=AdventureWorks;Data Source=.\\SQLExpress"; // Activate the connection AConnection.Open(); // Create a new Command object Cmd = ADO.CreateCommand(); // To create an ADO command you can also use the following code: // Cmd = new ActiveXObject("ADODB.Command"); // Specify the connection Cmd.ActiveConnection = AConnection; // Specify command type and text Cmd.CommandType = adCmdText; Cmd.CommandText = "SELECT * FROM Sales.SalesOrderDetail AS d INNER " + "Sales.SalesOrderHeader AS h ON d.SalesOrderID = h.SalesOrderID" + " WHERE (h.CustomerID = ?)" // Create a new parameter Prm = Cmd.CreateParameter("@CustID",DB.adInteger, DB.adParamInput); // Specify the parameter value Prm.Size = 4; Prm.Value = 676; AConnection.Close(); } catch(exception) { Log.Error("Exception", exception.description); } }

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

169

170

TestComplete Made Easy

4. Insert the parameter into the command object. [VBScript] Sub Main ' Create a new Connection object Set AConnection = ADO.CreateConnection ' Note that you can also create an ADO connection using the following code: ' Set AConnection = CreateObject("ADODB.Connection") ' Specify the connection string AConnection.ConnectionString = _ "Provider=SQLOLEDB.1;Integrated Security=SSPI;" & _ "Persist Security Info=False;" & _ "Initial Catalog=AdventureWorks;Data Source=.\SQLExpress" ' Activate the connection AConnection.Open ' Create a new Command object Set Cmd = ADO.CreateCommand ' To create an ADO command you can also use the following code: ' Set Cmd = CreateObject("ADODB.Command") ' Specify the connection Cmd.ActiveConnection = AConnection ' Specify command type and text Cmd.CommandText = _ "SELECT * FROM Sales.SalesOrderDetail AS d INNER " & _ ":Sales.SalesOrderHeader AS h ON d.SalesOrderID = h.SalesOrderID " & _ " WHERE (h.CustomerID = ?)" Cmd.CommandType = adCmdText ' Create a new parameter Set Prm = Cmd.CreateParameter("@CustID",DB.adInteger, DB.adParamInput) ' Specify the parameter value Prm.Size= 4 Prm.Value = 676 Cmd.Parameters.Append(Prm) AConnection.Close End Sub

[JScript] function Main() { try { var AConnection, RecSet, Cmd, Prm; // Create a new Connection object AConnection = ADO.CreateConnection(); // Note that you can also create an ADO connection using the following code: // AConnection = new ActiveXObject("ADODB.Connection"); // Specify the connection string AConnection.ConnectionString = "Provider=SQLOLEDB.1;Integrated Security=SSPI;" + "Persist Security Info=False;" + "Initial Catalog=AdventureWorks;Data Source=.\\SQLExpress"; // Activate the connection AConnection.Open(); // Create a new Command object Cmd = ADO.CreateCommand(); // To create an ADO command you can also use the following code: // Cmd = new ActiveXObject("ADODB.Command"); // Specify the connection Cmd.ActiveConnection = AConnection; // Specify command type and text Cmd.CommandType = adCmdText; Cmd.CommandText = "SELECT * FROM Sales.SalesOrderDetail AS d INNER " + "Sales.SalesOrderHeader AS h ON d.SalesOrderID = h.SalesOrderID" + " WHERE (h.CustomerID = ?)"

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Working with Databases

// Create a new parameter Prm = Cmd.CreateParameter("@CustID",DB.adInteger, DB.adParamInput); // Specify the parameter value Prm.Size = 4; Prm.Value = 676; Cmd.Parameters.Append(Prm); AConnection.Close(); } catch(exception) { Log.Error("Exception", exception.description); } }

5. Execute the command object and get the ResultSet. [VBScript] Sub Main ' Create a new Connection object Set AConnection = ADO.CreateConnection ' Note that you can also create an ADO connection using the following code: ' Set AConnection = CreateObject("ADODB.Connection") ' Specify the connection string AConnection.ConnectionString = _ "Provider=SQLOLEDB.1;Integrated Security=SSPI;" & _ "Persist Security Info=False;" & _ "Initial Catalog=AdventureWorks;Data Source=.\SQLExpress" ' Activate the connection AConnection.Open ' Create a new Command object Set Cmd = ADO.CreateCommand ' To create an ADO command you can also use the following code: ' Set Cmd = CreateObject("ADODB.Command") ' Specify the connection Cmd.ActiveConnection = AConnection ' Specify command type and text Cmd.CommandText = _ "SELECT * FROM Sales.SalesOrderDetail AS d INNER " & _ "Sales.SalesOrderHeader AS h ON d.SalesOrderID = h.SalesOrderID " & _ " WHERE (h.CustomerID = ?)" Cmd.CommandType = adCmdText ' Create a new parameter Set Prm = Cmd.CreateParameter("@CustID",DB.adInteger, DB.adParamInput) ' Specify the parameter value Prm.Size= 4 Prm.Value = 676 ' Execute the command Set RecSet = Cmd.Execute ' Execute the command AConnection.Close End Sub

[JScript] function Main() { try { var AConnection, RecSet, Cmd, Prm; // Create a new Connection object AConnection = ADO.CreateConnection(); // Note that you can also create an ADO connection using the following code: // AConnection = new ActiveXObject("ADODB.Connection"); // Specify the connection string AConnection.ConnectionString = "Provider=SQLOLEDB.1;Integrated Security=SSPI;" + "Persist Security Info=False;" +

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

171

172

TestComplete Made Easy

"Initial Catalog=AdventureWorks;Data Source=.\\SQLExpress"; // Activate the connection AConnection.Open(); // Create a new Command object Cmd = ADO.CreateCommand(); // To create an ADO command you can also use the following code: // Cmd = new ActiveXObject("ADODB.Command"); // Specify the connection Cmd.ActiveConnection = AConnection; // Specify command type and text Cmd.CommandType = adCmdText; Cmd.CommandText = "SELECT * FROM Sales.SalesOrderDetail AS d INNER " + "Sales.SalesOrderHeader AS h ON d.SalesOrderID = h.SalesOrderID" + " WHERE (h.CustomerID = ?)" // Create a new parameter Prm = Cmd.CreateParameter("@CustID",DB.adInteger, DB.adParamInput); // Specify the parameter value Prm.Size = 4; Prm.Value = 676; Cmd.Parameters.Append(Prm); // Execute the command RecSet = Cmd.Execute(); AConnection.Close(); } catch(exception) { Log.Error("Exception", exception.description); } }

6. Iterate through the result set to total the orders (this could have been done with a single sql query). [VBScript] Sub Main ' Create a new Connection object Set AConnection = ADO.CreateConnection ' Note that you can also create an ADO connection using the following code: ' Set AConnection = CreateObject("ADODB.Connection") ' Specify the connection string AConnection.ConnectionString = _ "Provider=SQLOLEDB.1;Integrated Security=SSPI;" & _ "Persist Security Info=False;" & _ "Initial Catalog=AdventureWorks;Data Source=.\SQLExpress" ' Activate the connection AConnection.Open ' Create a new Command object Set Cmd = ADO.CreateCommand ' To create an ADO command you can also use the following code: ' Set Cmd = CreateObject("ADODB.Command") ' Specify the connection Cmd.ActiveConnection = AConnection ' Specify command type and text Cmd.CommandText = _ "SELECT * FROM Sales.SalesOrderDetail AS d INNER " & _ "Sales.SalesOrderHeader AS h ON d.SalesOrderID" & _ " = h.SalesOrderID WHERE (h.CustomerID = ?)" Cmd.CommandType = adCmdText ' Create a new parameter Set Prm = Cmd.CreateParameter("@CustID",DB.adInteger, DB.adParamInput) ' Specify the parameter value Prm.Size= 4 Prm.Value = 676 Cmd.Parameters.Append(Prm) ' Execute the command Set RecSet = Cmd.Execute ' Execute the command Dim Sales Sales = 0 While Not RecSet.EOF Sales = Sales + VarToFloat(RecSet("LineTotal").Value)

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Working with Databases

RecSet.MoveNext WEnd Log.Message("Total Sales = " ^ Sales) AConnection.Close End Sub

[JScript] function Main() { try { var AConnection, RecSet, Cmd, Prm; // Create a new Connection object AConnection = ADO.CreateConnection(); // Note that you can also create an ADO connection using the following code: // AConnection = new ActiveXObject("ADODB.Connection"); // Specify the connection string AConnection.ConnectionString = "Provider=SQLOLEDB.1;Integrated Security=SSPI;" + "Persist Security Info=False;" + "Initial Catalog=AdventureWorks;Data Source=.\\SQLExpress"; // Activate the connection AConnection.Open(); // Create a new Command object Cmd = ADO.CreateCommand(); // To create an ADO command you can also use the following code: // Cmd = new ActiveXObject("ADODB.Command"); // Specify the connection Cmd.ActiveConnection = AConnection; // Specify command type and text Cmd.CommandType = adCmdText; Cmd.CommandText = "SELECT * FROM Sales.SalesOrderDetail AS d INNER " + " Sales.SalesOrderHeader AS h ON d.SalesOrderID = h.SalesOrderID" + " WHERE (h.CustomerID = ?)" // Create a new parameter Prm = Cmd.CreateParameter("@CustID",DB.adInteger, DB.adParamInput); // Specify the parameter value Prm.Size = 4; Prm.Value = 676; Cmd.Parameters.Append(Prm); // Execute the command RecSet = Cmd.Execute(); var Sales; Sales = 0; while (! RecSet.EOF ) { Sales = Sales + RecSet("LineTotal").Value; RecSet.MoveNext(); } Log.Message("Total Sales = " + Sales); AConnection.Close(); AConnection.Close(); } catch(exception) { Log.Error("Exception", exception.description); } }

You should get a log file like:

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

173

174

16.5

TestComplete Made Easy

Summary In this section we discussed options for connecting and manipulating datasources using ADO and BDE. You learned how to retrieve ADO data for use within your tests.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Part

XVII Web Page Testing

176

TestComplete Made Easy

17

Web Page Testing

17.1

Objectives This section discusses how TestComplete represents web pages in the Object Browser, how to navigate between web pages and how web checkpoints are used. This section also talks about strategies for locating and testing dynamic HTML elements. In this section you'll learn about: · Web Page Models. · How TestComplete names web page elements. · Web Comparison Checkpoint. · Web Accessibility Checkpoint. · How to find web page object based on properties. · How to handle dynamic HTML elements using mouse hovers.

17.2

Web Page Model TestComplete s four web page models: · DOM - Document Object Model, the native way that Internet Explorer looks at web pages. The DOM model creates a very flat tree in the Object Browser. All items on the web page need to be re-read each time the web page is updated. This is the slowest method for using web pages. · TAG - All HTML elements are sorted by their TAG value. If a link ( HTML tag) gets created, only the "A" node part of the Object Browser tree gets updated. · Tree - Treats a web page like a normal application. This model creates a very deep tree for most web pages. This is the fastest method for using web pages. · Hybrid - This uses both DOM and Tree. All new recording will use the Tree model, while any old TestComplete code using the DOM will continue to work. To set the web page model used for the project: 1. Select the Project Project Item and then click on Properties. 2. Select Open Application | Web Testing. 3. Select the desired Tree model.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Web Page Testing

17.3

177

Naming Conventions The naming convention for HTML elements used by TestComplete depends on the web page model used: · DOM - HTML elements are in the form of Item(index). The index will be either the ID or Name attribute, if any (with the Identification attribute having priority). If the element does not have either attribute, TestComplete will assign an index number based on the order the item was created. · TAG - HTML elements have the same form as DOM but are sorted by type. · Tree - HTML elements have the form ObjectType(Index), for example: (0) - div element, Image ("Logo.gif") - image element.

17.4

Web Comparison Checkpoint A Web Comparison checkpoint is used to compare two web pages. 1. To access the Web Comparison checkpoint, use either the checkpoint drop down from the recording toolbar...

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

178

TestComplete Made Easy

...or the checkpoint drop down from the "Tools" toolbar from the main form of TestComplete.

2. Selecting either option displays the Create Web Comparison Checkpoint dialog.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Web Page Testing

3. Use the target icon

179

to select the web page.

4. The extent of the comparison is controlled by the options below the "Page object" in the dialog. · Compare entire page - The whole HTML page is save and is compared. · Compare only tab structure - Only tag names are compared, not attributes, attributes' values and elements' values. · Compare only specified tags - Only the selected elements will be compared. o Compare links - Only A elements are compared (text and attributes of the element are compare as well). o Compare images - Only IMG elements are compared. o Compare input elements - Only INPUT elements are compare. 5. Press the OK button and you will be presented with the Copy Text to Clipboard dialog. The dialog has the script code that will perform the web page comparison. Note: In this case the dialog contents will be placed into the clipboard so you can paste into your script routine. If you do the comparison while recording, TestComplete puts the code in for you automatically.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

180

TestComplete Made Easy

Tip: If you have a web page that has dynamically created items, you can set a timeout for the web comparison to wait for the page to be populated before doing the comparison (default is the Auto-wait timeout).

17.5

Web Accessibility Checkpoint It is increasingly important to check your that your web pages are accessible. Use the Web Accessibility Checkpoint to accessibility compliance. 1. To create a Web Accessbility Checkpoint use either the recording toolbar...

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Web Page Testing

... or the 'Tools' toolbar in TestComplete.

2. Selecting either option will display the Create Web Accessibility Checkpoint dialog.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

181

182

TestComplete Made Easy

3. The types of accessibilities that TestComplete can check for are: · Check "alt" attribute - All IMG, APPLET, AREA and INPUT elements must have a non-empty ALT attribute. · Check "mailto:" - Web page must have at least one A element (link), whose HREF attribute starts with mailto: · Check image sizes - All IMG elements must have the WIDTH and HEIGHT attributes specified. · Check "title" tag - The web page must have a non-empty TITLE elment. · Check tab indexes - All INPUT, SELECT, and TEXTAREA elements must have the TABINDEX attribute. · Check link accessibility - Checks for broken links. · Check ActiveX objects - Verifies there are no ActiveX objects on the web page. · Check Applet object - Verifies there are no Applet objects on the web page. · Check multimedia links - Verifies there are not AVI or SWF files on the web page. · Check server-side images - Verifies that none of the IMG elements contain SRC attribute with parameters. 4. Press the OK button and TestComplete will present you with a dialog showing code for the Web Accessibility Checkpoint.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Web Page Testing

183

.

17.6

Finding Web Page Elements Since not all web elements have an ID or Name property (or they might have been created dynamically), TestComplete provides a couple of ways to find elements by using properties of the element. The first one uses the Page object's NativeWebObject.Find() method. NativeWebObject.Find takes three parameters, two required and one optional. Find returns the found element or an empty element with the Exists property set to false. The first parameter is the name of the property you are searching for, such as innerText. The second parameter is the value to search for. The optional last parameter is the Tag type to search for, such as "A". For example on http://www.automatedqa.com, the Products link on the header does not have a name or an id. The example below uses Sys.Process to retrieve the Page object. The Page object uses NativeWebObject.Find to search for a link with title element "Products": [VBScript] Sub NativeFind Dim PageObj Dim ProductLink Set PageObj = Sys.Process("iexplore"). Page("http://www.automatedqa.com/") Set ProductLink = PageObj.NativeWebObject.Find("title","Products","A") if ProductLink.Exists Then ProductLink.Click End If End Sub

[JScript] function NativeFind() { var PageObj

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

184

TestComplete Made Easy

var ProductLink PageObj = Sys.Process("iexplore").Page("http://www.automatedqa.com/") ProductLink = PageObj.NativeWebObject.Find("title","Products","A") if (ProductLink.Exists) ProductLink.Click() }

The second method to find objects on a web (or any other application), is to use the TestedObject. Find() method. This method allows you to use multiple properties and values to select a web element. The example below uses the page object again, not the TestedObject. In this case the page object is the TestedObject, TestedObject can be any on-screen object. To perform the same search as above:

[VBScript] Sub TestedObjFind Dim PropArray, ValuesArray Dim PageObj Dim ProductLink ' Creates arrays of properties and values PropArray = CreateVariantArray(0, 1) ValuesArray = CreateVariantArray(0, 1) ' Specifies property names PropArray(0) = "title" PropArray(1) = "tagName" ' Specifies the property values ValuesArray(0) = "Products" ValuesArray(1) = "A" Set PageObj = Sys.Process("iexplore").Page("http://www.automatedqa.com/") Set ProductLink = PageObj.Find(PropArray,ValuesArray,3) if ProductLink.Exists Then ProductLink.Click End If End Sub

[JScript] function ConvertArray(AArray) { // Uses the Dictionary object to convert a JScript array var objDict = Sys.OleObject("Scripting.Dictionary"); objDict.RemoveAll(); for (var j in AArray) objDict.Add(j, AArray[j]); return objDict.Items(); } function TestedObjFind() { var PropArray, ValuesArray, ConvertedPropArray, ConvertedValuesArray; var PageObj; var ProductLink; // Creates arrays of properties and values PropArray = new Array(2); ValuesArray = new Array(2); // Specifies property names PropArray[0] = "title"; PropArray[1] = "tagName"; // Specifies the property values ValuesArray[0] = "Products"; ValuesArray[1] = "A";

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Web Page Testing

185

// Converts arrays ConvertedPropArray = ConvertArray(PropArray); ConvertedValuesArray = ConvertArray(ValuesArray); PageObj = Sys.Process("iexplore").Page("http://www.automatedqa.com/") ProductLink = PageObj.Find(ConvertedPropArray,ConvertedValuesArray,3) if (ProductLink.Exists) ProductLink.Click() }

Note: Notice that the Find() method es a depth value of 3. The depth value indicates that at most, TestComplete will search the object tree three levels below the current selected TestedObject. Choosing the method to use depends on how far down the object tree you are and how complex a search you require. If you are using the page object, NativeWebObject.Find() is the fastest. Below the page object, it will depend on the current depth and how far down you need to search. For more complex searches, TestedObject.Find() provides more flexibility.

17.7

Dynamic HTML Script recording in TestComplete does not record mouse movements, only mouse click and keyboard entry. The lack of mouse movement information can present a problem in dealing with dynamic HTML elements such a Hover Menus which require the mouse to hover (move over) the menu to active. For example the web page http://www.asp.net/AJAX/AjaxControlToolkit/Samples/HoverMenu/HoverMenu. aspx has a hover menu attached to the word "Have project idea". If you were to attempt recording interaction with this menu, the playback would fail as the menu would not be visible to click on. This can be solved by using the HoverMouse method in the script. To get the HoverMouse method in the record you can do the following: 1. Go to the web page. 2. Start recording. 3. Select the Add text button from the recording toolbar

4. Click the Pick Object... button in the Add Text to Script dialog.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

186

TestComplete Made Easy

5. Use the target icon

from the Pick Object dialog to select the right object.

6. Click the OK button. 7. Check mark Add as comment. 8. Click the Add button 9. Continue recording as normal. 10. On the commented line add HoverMouse(10,10) to the end and uncomment. You may have to move the line as well.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Web Page Testing

187

[VBScript - Recorded Code] Sub Test1 Dim w1 'Original recording: 'Sys.Process("iexplore") '.Page("http://www.asp.net/AJAX/AjaxControlToolkit/Samples/HoverMenu/ 'HoverMenu.aspx") '.Form("aspnetForm").("master_page").("master_content"). '("master_contentplaceholder"). '(0).("ctl00_SampleContent_up1").(0). 'Table("ctl00_SampleContent_GridView1"). 'Cell(0, 0).("ctl00_SampleContent_GridView1_ctl02_9"). 'Table(0).Cell(0, 0). 'TextNode("ctl00_SampleContent_GridView1_ctl02_Label1") Set w1 = Sys.Process("iexplore").Page(_ "http://www.asp.net/AJAX/AjaxControlToolkit/Samples/HoverMenu/HoverMenu.aspx") Call w1.ToURL(_ "http://www.asp.net/AJAX/AjaxControlToolkit/Samples/HoverMenu/HoverMenu.aspx") w1.Form("aspnetForm").("master_page").("master_content"). ("master_contentplaceholder").(0).("ctl00_SampleContent_up1"). (0).Table("ctl00_SampleContent_GridView1").Cell(0, 0). ("ctl00_SampleContent_GridView1_ctl02_PopupMenu").(0).(0). Link("ctl00_SampleContent_GridView1_ctl02_LinkButton1").Click End Sub [VBScript - Modified Code] Sub Test1 Dim w1 Set w1 = Sys.Process("iexplore"). Page(_ "http://www.asp.net/AJAX/AjaxControlToolkit/Samples/HoverMenu/HoverMenu.aspx") Call w1.ToURL(_ "http://www.asp.net/AJAX/AjaxControlToolkit/Samples/HoverMenu/HoverMenu.aspx") ' Code Moved Here and HoverMouse added Call Sys.Process("iexplore"). Page("http://www.asp.net/AJAX/AjaxControlToolkit/Samples/HoverMenu/HoverMenu.aspx"). Form("aspnetForm"). ("master_page").("master_content").("master_contentplaceholder"). (0). ("ctl00_SampleContent_up1").(0).Table("ctl00_SampleContent_GridView1"). Cell(0, 0). ("ctl00_SampleContent_GridView1_ctl02_9").Table(0).Cell(0, 0). TextNode("ctl00_SampleContent_GridView1_ctl02_Label1").HoverMouse(10,10) w1.Form("aspnetForm").("master_page").("master_content"). ("master_contentplaceholder").(0).("ctl00_SampleContent_up1"). (0). Table("ctl00_SampleContent_GridView1").Cell(0, 0). ("ctl00_SampleContent_GridView1_ctl02_PopupMenu").(0).(0). Link("ctl00_SampleContent_GridView1_ctl02_LinkButton1").Click End Sub

[JScript - Recorded Code] function Test1() { var w1; var w2; // Original recording: Sys.Process("iexplore"). Page("http://www.asp.net/AJAX/AjaxControlToolkit/Samples/HoverMenu/ HoverMenu.aspx"). Form("aspnetForm").("master_page").("master_content"). ("master_contentplaceholder").(0). ("ctl00_SampleContent_up1").(0). Table("ctl00_SampleContent_GridView1"). Cell(0, 0). ("ctl00_SampleContent_GridView1_ctl02_9"). Table(0).Cell(0, 0). TextNode("ctl00_SampleContent_GridView1_ctl02_Label1")

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

188

TestComplete Made Easy

// w1 = Sys.Process("iexplore"). Page( "http://www.asp.net/AJAX/AjaxControlToolkit/Samples/HoverMenu/HoverMenu.aspx"); w1.ToURL( "http://www.asp.net/AJAX/AjaxControlToolkit/Samples/HoverMenu/HoverMenu.aspx"); w2 = w1.Form("aspnetForm").("master_page").("master_content"); w2.("master_contentplaceholder").(0).("ctl00_SampleContent_up1"). (0).Table("ctl00_SampleContent_GridView1").Cell(0, 0). ("ctl00_SampleContent_GridView1_ctl02_PopupMenu"). (0).(0). Link("ctl00_SampleContent_GridView1_ctl02_LinkButton1").Click(); } [JScript - Modified Code] function Test1() { var w1; var w2; w1 = Sys.Process("iexplore"). Page( "http://www.asp.net/AJAX/AjaxControlToolkit/Samples/HoverMenu/HoverMenu.aspx"); w1.ToURL( "http://www.asp.net/AJAX/AjaxControlToolkit/Samples/HoverMenu/HoverMenu.aspx"); w2 = w1.Form("aspnetForm").("master_page").("master_content"); // Line moved here and HoverMouse added. Sys.Process("iexplore"). Page("http://www.asp.net/AJAX/AjaxControlToolkit/Samples/HoverMenu/HoverMenu.aspx"). Form("aspnetForm").("master_page").("master_content"). ("master_contentplaceholder").(0). ("ctl00_SampleContent_up1").(0).Table("ctl00_SampleContent_GridView1"). Cell(0, 0).("ctl00_SampleContent_GridView1_ctl02_9").Table(0).Cell(0, 0). TextNode("ctl00_SampleContent_GridView1_ctl02_Label1").HoverMouse(10,10); w2.("master_contentplaceholder").(0).("ctl00_SampleContent_up1"). (0).Table("ctl00_SampleContent_GridView1").Cell(0, 0). ("ctl00_SampleContent_GridView1_ctl02_PopupMenu"). (0).(0).Link("ctl00_SampleContent_GridView1_ctl02_LinkButton1").Click(); }

The code above will hover the mouse and allow the menu to be clicked.

17.8

Hands on Lab: Work with Web Pages Basic Web Page 1. Create a new project. 2. Add "Win32 Tested Apps" project item to the project. 3. Add either Internet Explorer or Firefox as the tested application. 4. Click the ellipse button (...) next to the application and add "http://www.activefocus.net/AFDemo" as the command line parameter. Note: With Vista, you need to change the run mode from simple to run as, and run as .

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Web Page Testing

5. Double Click the Project project item to get the project editor. 6. Click the "Properties" button in the project editor. 7. Select "Open Applications | Web Testing". 8. Select "Tree" for the Tree model. 9. Check the "Mark Page Object a child of the browser process".

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

189

190

TestComplete Made Easy

10.Press the recording button in the test engine toolbar. 11.Click the run application button (either IE or Firefox) in the recording toolbar. 12. into ActiveFocus. 13.Select the a project under Recent Projects 14.Stop the recording (Your code may not exactly match the example below). [VBScript] Sub Test1 Dim w1 Dim w2 TestedApps.iexplore.Run Set w1 = Sys.Process("iexplore"). Page(_ "http://www.activefocus.net/AFDemo/.aspx?ReturnUrl=%2fAFDemo%2fdefault.aspx") Call w1. ToURL(_ "http://www.activefocus.net/AFDemo/.aspx?ReturnUrl=%2fAFDemo%2fdefault.aspx") Set w2 = _ w1.Form("form1").("content").("_position").Table("lgin").Cell(0, 0). Table(0)

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Web Page Testing

Call w2.Cell(0, 1).Textbox("lgin_Name").Keys("AFDemo[Tab]") Call w2.Cell(1, 1).Box("lgin_").Keys("AFDemo2008!![Enter]") 'Please wait until completes: "http://www.activefocus.net/AFDemo/.aspx?ReturnUrl=%2fAFDemo%2fdefault.aspx" w1.Wait w1.Form("frmMain").("mainWrapper").("spltMain"). Table("RAD_SPLITTER_spltMain"). Cell(0, 2).("RAD_SPLITTER_PANE_CONTENT_pnContent").("mc"). ("roject_dvStartPage").("left").("recents").(1).(0). Link(0).Click End Sub

[Jscript] function Test1() { var w1; var w2; TestedApps.iexplore.Run(); w1 = Sys.Process("iexplore"). Page( "http://www.activefocus.net/AFDemo/.aspx?ReturnUrl=%2fAFDemo%2fdefault.aspx"); w1.ToURL( "http://www.activefocus.net/AFDemo/.aspx?ReturnUrl=%2fAFDemo%2fdefault.aspx"); w2 = w1.Form("form1").("content").("_position").Table("lgin"). Cell(0, 0).Table(0); w2.Cell(0, 1).Textbox("lgin_Name").Keys("AFDemo[Tab]"); w2.Cell(1, 1).Box("lgin_").Keys("AFDemo2008!!"); w2.Cell(3, 0).SubmitButton("lgin_Button").Click(); w1.Wait(); w1.Form("frmMain").("mainWrapper").("spltMain"). Table("RAD_SPLITTER_spltMain"). Cell(0, 2).("RAD_SPLITTER_PANE_CONTENT_pnContent").("mc"). ("roject_dvStartPage").("left").("recents").(1).(0). Link(0).Click(); }

15.Close the Tested Application (IE or Firefox). 16.Run the recorded test.

Using NativeWebObject.Find Method 1. Copy the recording above to a new method. 2. Change the last line to below (notice the extra space). [VBScript] w1.NativeWebObject.Find("innerText","Sample Project ","A").Click

[JScript] w1.NativeWebObject.Find("innerText","Sample Project ","A").Click();

3. Run the script. 4. Close the Tested Application (IE or Firefox).

Using TestComplete's Find Method 1. Copy the code from above into a new method. 2. Change the code to look like the example below.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

191

192

TestComplete Made Easy

[VBScript] Sub Test3 Dim w1 Dim w2 TestedApps.iexplore.Run Set w1 = Sys.Process("iexplore"). Page( "http://www.activefocus.net/AFDemo/.aspx?ReturnUrl=%2fAFDemo%2fdefault.aspx") Call w1. ToURL( "http://www.activefocus.net/AFDemo/.aspx?ReturnUrl=%2fAFDemo%2fdefault.aspx") Set w2 = w1.Form("form1").("content").("_position").Table("lgin"). Cell(0, 0).Table(0) Call w2.Cell(0, 1).Textbox("lgin_Name").Keys("AFDemo[Tab]") Call w2.Cell(1, 1).Box("lgin_").Keys("AFDemo2008!![Enter]") 'Please wait until completes: "http://www.activefocus.net/AFDemo/.aspx?ReturnUrl=%2fAFDemo%2fdefault.aspx" w1.Wait ' New Stuff below Dim PropArray, ValuesArray ' Creates arrays of properties and values PropArray = CreateVariantArray(0, 1) ValuesArray = CreateVariantArray(0, 1) ' Specifies property names PropArray(0) = "tagName" PropArray(1) = "innerText" ' Specifies the property values ValuesArray(0) = "A" ValuesArray(1) = "Sample Project " w1.Refresh w1.Find(PropArray,ValuesArray,100).Click End Sub

[JScript] function ConvertArray(AArray) { // Uses the Dictionary object to convert a JScript array var objDict = Sys.OleObject("Scripting.Dictionary"); objDict.RemoveAll(); for (var j in AArray) objDict.Add(j, AArray[j]); return objDict.Items(); } function Test3() { var w1; var w2; TestedApps.iexplore.Run(); w1 = Sys.Process("iexplore"). Page( "http://www.activefocus.net/AFDemo/.aspx?ReturnUrl=%2fAFDemo%2fdefault.aspx"); w1. ToURL( "http://www.activefocus.net/AFDemo/.aspx?ReturnUrl=%2fAFDemo%2fdefault.aspx"); w2 = w1.Form("form1").("content").("_position").Table("lgin").Cell(0, 0). Table(0); w2.Cell(0, 1).Textbox("lgin_Name").Keys("AFDemo[Tab]"); w2.Cell(1, 1).Box("lgin_").Keys("AFDemo2008!!"); w2.Cell(3, 0).SubmitButton("lgin_Button").Click(); w1.Wait(); // New Stuff below var PropArray, ValuesArray, ConvertedPropArray, ConvertedValuesArray;

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Web Page Testing

// Creates arrays of properties and values PropArray = new Array(2); ValuesArray = new Array(2); // Specifies property names PropArray[0] = "tagName"; PropArray[1] = "innerText"; // Specifies the property values ValuesArray[0] = "A"; ValuesArray[1] = "Sample Project "; // Converts arrays ConvertedPropArray = ConvertArray(PropArray); ConvertedValuesArray = ConvertArray(ValuesArray); w1.Refresh(); w1.Find(ConvertedPropArray,ConvertedValuesArray,100).Click(); }

3. Run the script. 4. Close the Tested Application (IE or Firefox).

Using Name Mapping 1. Add the NameMapping Project Item to the project. 2. Open IE or Firefox to the page of ActiveFocus. 3. Click the Map Object from Screen button in the Tools toolbar.

4. Use the finder tool

to select the Name textbox.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

193

194

TestComplete Made Easy

5. Click the OK button. 6. Click the Yes button on the "Map Object Name" dialog. 7. Click Skip on the Sys Object. 8. Click Skip on the Process Object. 9. On The Page Object, change the name to "PageAF". 10.Click on the Name Properties. 11.Click on the ellipse button (...). 12.Change the Value to "Page("*")" 13.Click the OK button 14.Click the OK button on the "Object Name Mapping (3/11)" dialog. 15.Click the Skip button on the Form object. 16.Click the Skip button on the object. 17.Change the name to "" and click the OK button. 18.Skip the table object. 19.Skip the cell object. 20.Skip the table object. 21.Skip the cell object. 22.Change the name to "txtName" and click the OK button. Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Web Page Testing

195

23.Use the "Map Object from Screen" to map the textbox. 24.Click the Yes button in the "Map Object Name" dialog. 25.Click the Skip button on the cell object. 26.Change the name to "txt" and click the OK button. 27.Use the "Map Object from Screen" to map the button. 28.Click the Yes button in the "Map Object Name" dialog. 29.Click the Skip button on the cell object. 30.Change the name to "btn" and click the OK button. 31. to ActiveFocus. 32.Use the "Map Object from Screen" to map the "Sample Project" Link under the "Recent Projects" Area. 33.Click the Yes button in the "Map Object Name" dialog. 34.Click Skip on the Form object. 35.Change the name to "Main" and click the OK button. 36.Press the Skip button until the dialog reads "Object Name Mapping (13/13)" 37.Change the name to "SampleProjectLink". 38.Remove the "Name" property from the "Selected Properties". 39.Add the "innerText" property to the "Selected Properties" from the "Available Properties". 40.Click the Highlight button. 41.Click the OK button.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

196

TestComplete Made Easy

42.Close the IE or Firefox browser. 43.Click the Record button. 44.Click the run application button (either IE or Firefox) in the recording toolbar. 45. into ActiveFocus. 46.Select the "Sample Project" under Recent Projects 47.Stop the recording (Your code may not exactly match below). 48.Close the IE or Firefox browser. [VBScript] Sub Test4 Dim w1 Dim w2 Dim w3 TestedApps.iexplore.Run Set w1 = Aliases.PageAF Call w1. ToURL( "http://www.activefocus.net/AFDemo/.aspx?ReturnUrl=%2fAFDemo%2fdefault.aspx") Set w2 = w1. Set w3 = w2.txtName Call w3.Click(26, 8) Call w3.Keys("AFDemo[Tab]") Call w2.txt.Keys("AFDemo2008!!") w2.btn.Click w1.Main.SampleProjectLink.Click

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Web Page Testing

197

End Sub

[JScript] function Test4() { var w1; var w2; var w3; TestedApps.iexplore.Run(); w1 = Aliases.PageAF; w1.ToURL( "http://www.activefocus.net/AFDemo/.aspx?ReturnUrl=%2fAFDemo%2fdefault.aspx"); w2 = w1.; w3 = w2.txtName; w3.Click(17, 8); w3.Keys("AFDemo[Tab]"); w2.txt.Keys("AFDemo2008!!"); w2.btn.Click(); w1.Main.SampleProjectLink.Click(); }

49.Run the recording.

.

17.9

Summary In this section we learned about web page testing, how TestComplete represents web pages in the Object Browser and how to switch between them. In addition, we learned about the different types of web checkpoints TestComplete has, and how to use them. The Find methods made it easier for us to deal with unnamed web elements and the HoverMouse method made it so we could test dynamic HTML elements.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Part

XVIII WebServices Testing

WebServices Testing

18

WebServices Testing

18.1

Objectives

199

This section demonstrates how to test a web service. In this section you'll learn: · Importing Web Services into TestComplete. · Calling Simple Methods of a Web Services in TestComplete. · Creating Web Service Types (objects) in TestComplete. · Calling Complex Method of Web Services. · Creating a Web Service Checkpoint.

18.2

Testing against WSDL TestComplete uses a WSDL (Web Service Definition Language) file to discover information about Web services, web service methods and parameters. The Web services project item is used to perform functional testing of web services. Using the Web services project item, you can perform the following actions: · Explore methods and objects used by the tested Web service. · Create script code that will call the service’s methods. · Check the service response to determine if the methods function properly.

Importing Web service information into TestComplete In order to use a Web service in TestComplete: 1. Add the Web services project item to your project (a place holder for all the child Web Service Project Items) a. Right-Click on the project, select Add | New Item… from the context menu. b. Select the Web services project item 2. Add a Web Service project item to the Web services Project Item. a. Right-Click the newly added Web services project item and select Add | New Item… from the context menu. b. Name the Web Service project Item (SimpleProjectTracker) and click the OK button. 3. Select the WSDL file for the web service. a. Click the Select button for the Web Service Definition URL. b. Enter the URL (location) to the web service. c. Click the Get Services button. d. Select the Web Service to test from the drop down list.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

200

TestComplete Made Easy

e. Click the OK button A list of types and methods that are available for the selected Web service is displayed.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

WebServices Testing

201

Working with the Web service: simple methods Our definition of a “simple” method is one that takes primitive data values (string, numbers, Boolean) as parameters and returns a primitive data value. For example, inside of a method of the project enter: [JScript] Log.Message(WebServices.SimpleProjectTracker.HelloWorld());

[VBScript] Call Log.Message(WebServices.SimpleProjectTracker.HelloWorld)

Using the TestComplete AutoCompletion feature you can import the example Web Service supplied with the book. The previous example above can be generated using AutoCompletion: Copyright © 2008 AutomatedQA Corp. - 1.0 Release

202

TestComplete Made Easy

1. Type “Log.m” in the code editor. 2. Press the "[Enter]" key. 3. Move the cursor between the parenthesis. 4. Type “W[Enter].” 5. Select the Web Service from the code completion (MyWebServiceName). 6. Type “.”. 7. Select the “HelloWorld” method from the code completion.

Working with the Web service, complex methods In order to send complex data element to a web service, an object to hold the data will need to be created. Luckily, TestComplete has a code generator to make the creation of the object easy. The following code sample demonstrates creating a data element as generated by TestComplete.

[JScript] function () { var Result; var TypeFactory; //Get the type factory for the web service TypeFactory = WebServices.SimpleProjectTracker.TypeFactory; Result = TypeFactory.; return Result; }

[VBScript] Function Dim TypeFactory 'Get the type factory for the web service Set TypeFactory = WebServices.SimpleProjectTracker.TypeFactory Set = TypeFactory. End Function

This code creates the object for use with the Web Service (such as invoking the AddNew method). To access the code generator: 1. Expand the list of types in your web service. 2. Select the type desired. 3. Click the “Code” button at the end of the line with the type.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

WebServices Testing

203

4. Copy the generated code to the clipboard.

5. Paste the generated code into the script editor using either " -V" or the Edit | Paste menu option. Now that we have the method to create a , we can use this method to add a new to the database using the Web service. The method we are calling in the Web service is AddNew().

[JScript] function AddA() { var a; a = (); a.Name = "Test"; a.Email = " [email protected]"; Log.Message("New Id is " + WebServices.SimpleProjectTracker.AddNew(a)); }

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

204

TestComplete Made Easy

[VBScript] Sub AddA Dim a Set a = () a.Name = "Test" a.Email = " [email protected]" Log.Message("New Id is " & WebServices.SimpleProjectTracker.AddNew(a)) End Sub

18.3

WebServices Checkpoint You can perform all of the operations needed to call a web service’s method and check the results yourself, or you can use the Create Web Service Checkpoint Wizard to walk you through the process. In general, performing the operations by hand is more flexible, but the wizard helps you create the checkpoints faster and more conveniently, which is important if you are new to TestComplete. The wizard helps you perform the following actions: · Create an XMLCheckpoint project item that stores a baseline copy of a web service’s response. · Generate script code that calls the web service’s method and checks the result. You can invoke the wizard when recording a test or at design time: To display the wizard when recording a test, select Recording toolbar:

Create Web Service Checkpoint from the

To display the wizard at design time, select the Create Web Service Checkpoint from the Tools toolbar. If this toolbar is hidden, right-click somewhere in the toolbar area and select Tools from the ensuing context menu:

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

WebServices Testing

205

In the wizard, the following actions will take place. · selecting the desired web service. · selecting the method to be called. · specifying the method parameters · specifying the expected result. 1. Invoke the wizard. On the "Select Web Service" page of the wizard, select the Web Service project item that corresponds to the tested web service.

2. On the "Select Web Service Method" page of the wizard, choose the web service method to be called.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

206

TestComplete Made Easy

3. On the "Specify Method Parameters" page, enter the method parameter values. If the parameters have a simple value type (a string, integer, Boolean and so on), enter its value directly on the page.

Note: To specify complex parameter values (that refer to objects), invoke the special "Complex Parameter" dialog.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

WebServices Testing

207

4. On the "Store Expected Response" page of the wizard, specify the XMLCheckpoint project item that will store the expected response of the web service method.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

208

TestComplete Made Easy

The response can be saved to a new or to an existing XMLCheckpoint project item. When creating a new project item, that TestComplete will use the project item’s name to address this project item from scripts. So, the name must be a valid script identifier. Scripting languages ed by TestComplete use different naming rules. To specify a name that will conform to the rules of any language, enter a string that starts with a letter and that only contains letters, digits and underscore symbols. TestComplete automatically generates the expected response of a method call. By default, TestComplete uses predefined values for XML document elements that correspond to the result value (or values). For instance, if the method returns an integer value, then TestComplete generates the 0 value for the element that holds the result value. You should replace this pre-defined value with the expected value. Else, the comparison will be meaningless. 5. Press "Finish" to close the wizard. TestComplete automatically creates (or updates) the specified XMLCheckpoint project item and then generates script code that calls the method and compares the result with the data stored by the project item.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

WebServices Testing

209

Part of the Project Explorer with a Web Services checkpoint

If the checkpoint was created during recording, TestComplete displays the generated code in the Add Text to Script dialog. Using this dialog you can insert the generated script instructions into the recorded code. If the checkpoint was created at design time, TestComplete displays the Copy Text to Clipboard dialog. Here, the generated code can be copied to the clipboard and then pasted into the script code.

[VBScript] Call WebServices.SimpleProjectTracker.AddNewProject(XML.project) If (Not XML.AddNewProject.Compare(WebServices.SimpleProjectTracker)) Then Call Log.Error("The AddNewProject method of the SimpleProjectTracker web" _ " service returned an incorrect value.") End If

[JScript] WebServices.SimpleProjectTracker.AddNewProject(XML.project); if(!XML.AddNewProject.Compare(WebServices.SimpleProjectTracker)) Log.Error("The AddNewProject method of the SimpleProjectTracker web" + " service returned an incorrect value.");

18.4

WebServices Testing Dialogs The testing of web services can occur across multiple computers. TestComplete has settings to ensure that the test will complete even if one of the computers involved gets disconnected. Using the "Web Services Options" dialog, you can configure the HTTP Proxy settings as well as the timeout values used to close inactive connection. TestComplete will throw an exception if a timeout occurs.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

210

TestComplete Made Easy

Web Services Options Settings Proxy Settings: Select the "Use HTTP Proxy" checkbox if your computer requires a proxy server to connect to the web service. You can obtain proxy connection information from your IT department. Timeout Settings: The timeout settings are used by TestComplete to close inactive connections to the web service. The timeout logic works with the connect, receive and send timeout settings in the following order: · TestComplete will first make a connection request to the web service. If the web service does not respond in the time specified by the "Connect" timeout, TestComplete treats the connection as inactive and raises an exception. · TestComplete then sends the request to the web service, if the request takes longer than the "Send" timeout, TestComplete treats the connection as inactive and raises an exception. · After sending the request, TestComplete waits for a response, if this takes longer than the "Receive" timeout, TestComplete will treat the connection as inactive and raises an exception.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

WebServices Testing

18.5

211

XML Checkpoint The XML checkpoint is use to compare two different XML documents (such as the response from a Web Service method call). TestComplete stores the XML checkpoint information under the "Stores | XML " project item folder.

TestComplete compares two XML documents by moving down the hierarchy of document elements and comparing each document node. The comparison starts at the root node for each document. The following steps are performed for each node: · Finds the "matching" node from each document and compares each of the node values. Nodes are matched on the baseName, namespaceURI properties as well as node prefix and type. · Compares node attributes and namespace declarations · Gets a list of child nodes and performs a comparison. If the node or any of the child nodes are different, TestComplete will report the differences.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

212

TestComplete Made Easy

By configuring the Checkpoint Options of a XML checkpoint, the default behavior of the comparison can be changed.

The checkpoint options are: · Ignore node order - TestComplete does not check if the node was found in the same place in both documents. Copyright © 2008 AutomatedQA Corp. - 1.0 Release

WebServices Testing

213

· Ignore attributes - TestComplete only compares names and values for the XML elements. · Ignore namespace declarations - TestComplete does not check the namespace attribute of the XML nodes. · Ignore prefixes - TestComplete does not check the prefix on the name of the XML node. · Compare in subtree mode - The comparison results will not include nodes that only exist in the actual document and not in the stored (expected) document (Good for checking only part of an XML document).

18.6

Hands on Lab: Testing a SOAP 1.2 Web Service In this lab, we will: · Call a simple Web service method. · Create a Web service type (object) and use the object for calling a method. · Create a Web service checkpoint.

Calling a Simple Web Service Method 1. Create a new project in TestComplete. 2. Add the "Web Services" project Item to the project. 3. Right-click the "Web Services" project item and select Add | New Item…. 4. Name the Web service “TrainingWS”. 5. Click the Select button in the “TrainingWS” workspace editor. 6. If you have IIS installed on your computer, enter the URL: http://localhost/SimpleProjectTracker/SimpleProjectTrackerWebService.asmx?WSDL If IIS is not installed, enter the following URL: <supplied.by.instructor>/SimpleProjectTracker/SimpleProjectTrackerWebService.asmx?WSDL

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

214

TestComplete Made Easy

7. Click the "Get Services" button. 8. Select the SimpleProjectTrackerWS (SOAP 1.2) as the tested service. 9. Click the "OK" button. 10.Create a new method in the script editor. Call the method "GetTask". 11. Create a variable for your scripting language. Call the variable "ReturnValue". 12.Assign the value to the results of "WebServices.TrainingWS.GetTaskByID(1)". Caution: This result is actually a complex value (object) so be careful with the assignment (use SET for VBScript). 13.Add a line to Log the value of "ReturnValue.Name"

[VBScript] Sub GetTask Dim ReturnValue Set ReturnValue = WebServices.TrainingWS.GetTaskByID(1) Log.Message("Task 1 is " & ReturnValue.Name) End Sub

[JScript] function GetTask() { var ReturnValue; ReturnValue = WebServices.TrainingWS.GetTaskByID(1); Log.Message("Task 1 is " + ReturnValue.Name); }

14.Right-click inside the method just created and select Run Current Routine.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

WebServices Testing

215

Create a Web Service Type and Call a Method 1. In the project created above, select the Web Service Workspace editor for the TrainingWS (the tab named TrainingWS or double click the TrainingWS project Item). 2. Expand the Types in the Objects and Methods section of the editor. 3. Select the “Project” Type. 4. Click the Code button in the editor. 5. Rename the function from "Project" to "ProjectType". Note: Project is a keyword in TestComplete. In VBScript the Set Project = TypeFactory.Project needs to be changed to Set ProjectType = TypeFactory.Project. 6. Click the Copy button in the Generated Code dialog. 7. Move to the script editor and paste the code in the editor. 8. Create a new method in the editor called “ AddProject”. 9. Add a variable to the method called “Prj”. 10.Set the value of "Prj" to the results of the “ProjectType” method. 11.Assign the value of “TestComplete Training Lab” to the “Name” property of the “Prj”. Object. 12.Assign the value of 1 to the “Manager” property of the “Prj” Object. 13.Assign the value of Utilities.Date()+7 to the "DueDate" property of the "Prj" Object. 14.Create another variable. Call the variable "ReturnValue". 15. Assign the result of the "WebServices.TrainingWS.AddNewProject using the "Prj" variable as the input parameter to the web service method call to "ReturnValue" 16.Log the result:

[VBScript] Function ProjectType Dim TypeFactory 'Get the type factory for the web service Set TypeFactory = WebServices.TrainingWS.TypeFactory Set ProjectType = TypeFactory.Project End Function Sub AddProject Dim Prj Set Prj = ProjectType Prj.Name = "TestComplete Training Lab" Prj.Manager = 1

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

216

TestComplete Made Easy

Prj.DueDate = Date() + 7 Dim ReturnValue ReturnValue = WebServices.TrainingWS.AddNewProject(Prj) Log.Message("New Project Id is " & ReturnValue) End Sub

[JScript] function ProjectType() { var Result; var TypeFactory; //Get the type factory for the web service TypeFactory = WebServices.TrainingWS.TypeFactory; Result = TypeFactory.Project; return Result; } function AddProject() { var Prj; Prj = ProjectType(); Prj.Name = "TestComplete Training Lab" Prj.Manager = 1; Prj.DueDate = Utilities.Date() + 7; var ReturnValue; ReturnValue = WebServices.TrainingWS.AddNewProject(Prj); Log.Message("New Project Id is " + ReturnValue); }

17.Right Click inside the method just created and select "Run Current Routine"

Creating a Web Service Checkpoint 1. Click the Web services checkpoint button (

) in the Tools toolbar.

2. Select the TrainingWS Web Service and click the Next button. 3. Select the “GetProjectByID” method from the list. 4. Set the 'id' parameter value to 1 and click the Next button. 5. Set the values on the node to match the values shown in the image below inside the soap:Body area only.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

WebServices Testing

6. Click the Finish button. 7. Click the Copy button of the Copy Text to Clipboard dialog. 8. Create a new method in the script edited called "Checkpoint1". Copyright © 2008 AutomatedQA Corp. - 1.0 Release

217

218

TestComplete Made Easy

9. Paste the copied code in the routine.

[VBScript] Sub CheckPoint1 Call WebServices.TrainingWS.GetProjectByID(1) If (Not XML.GetProjectByID.Compare(WebServices.TrainingWS)) Then Call Log.Error(_ "The GetProjectByID method of the TrainingWS web service returned an"_ " incorrect value.") End If End Sub

[JScript] function CheckPoint1() { WebServices.TrainingWS.GetProjectByID(1); if(!XML.GetProjectByID.Compare(WebServices.TrainingWS)) Log.Error( "The GetProjectByID method of the TrainingWS web service returned an incorrect"+ "value."); }

10.Right click in the routine and select Run Current Routine.

11.An error message is displayed in the test log. Expand the details of the XML node in the test log to see the errors.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

WebServices Testing

12.Double-click the "GetProjectByID" project item of the "Stores | XML" project item. 13.Expand the nodes until the Description and DueDate nodes are shown. 14.Delete the Description and DueDate nodes.

15.Check the "Compare in subtree mode" 16.Re-run the "Checkpoint1" Routine. No error will be displayed in the test log.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

219

220

18.7

TestComplete Made Easy

Summary In the section we learned how to retrieve information about web services in order to perform web service testing. We started by testing with a simple web service method using primitive types and worked up to testing a web service with a complex interface. We also learned how to change the default behavior of TestComplete for timeouts and about XML checkpoints.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Part

XIX HTTP Performance Testing

222

TestComplete Made Easy

19

HTTP Performance Testing

19.1

Objectives This section explores HTTP performance testing and other types of performance testing (e.g. load, stress, scalability). You will also learn about HTTP traffic recording and modification. In this section you will learn: · What is HTTP performance testing? · The different types of HTTP performance testing · How TestComplete records HTTP traffic · How to modify the HTTP traffic

19.2

Performance Testing Your Web Applications Performance testing of a web application is an important part of the development process. It will let you know if your application is multi- friendly and at what point does the application "break-down". Some of the things that TestComplete can show through analysis are: · Scalability Testing: Do hardware changes to the web server cause change to the performance of the web application? · Load Testing: Do the server's change with different number of s? · Stress Testing: Will enough s cause the web server to crash? · Load Testing or Stress Testing: At what number of s does the web server break or slow down too much? By recording different HTTP tasks, you can create realistic scenarios of interaction with the web site. Note: TestComplete can record traffic against HTTP as well as HTTPS connections.

19.3

HTTP Load Testing Options 1. Select Tools | Options from TestComplete main menu. 2. Select Engines | HTTP Load Testing from the options tree on the left of the dialog. The default HTTP Load Testing options will display:

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

HTTP Performance Testing

223

TestComplete can record both HTTP and HTTPS web traffic and automatically captures these protocols without any specific proxy setting requirements. Traffic Transponder · Cookie handling - Configures how TestComplete handles sending of cookies during playback. See the cookie handling section below for more information. · Send timeout - The number of seconds that TestComplete will wait for a acknowledgement from the web server that a connection has been made. · Receive times - The number of seconds that TestComplete will wait for a reply from the web server. · Simulate request to third-party site - If checked, TestComplete will not ask for images or other information from other sites that the web page might request. · Store request details - If unchecked, TestComplete will only store the header information and not the details of a web request.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

224

TestComplete Made Easy

· Synchronize requests - Forces the order of requests to remain the same as when recording, i.e. get the web page before the images on the page. Requests can get out of order if network traffic is high. Recorder Proxy port: the port TestComplete will listen for http traffic on. HTML Hidden Controls Certain web pages, like ASP.NET, utilize hidden HTML controls to transfer information from server to client and back. TestComplete allows you to specify which hidden values should be updated during playback to better simulate interaction with the server. You can specify which controls TestComplete should update during playback by editing the HTTP Load Testing Project Item simply right click and select "Edit" (see Hidden Controls editor below). By default, TestComplete populates the list with common ASP.NET hidden field names though you can add any values necessary for your testing requirements.

19.4

Cookie Handling A cookie is data stored on the client side, such as a security token used to authorize an request to a secured web site. The type of cookies that a web site generates makes a difference in how a web server responds to a request. Cookie data can change from run to run of a load test and TestComplete allows different methods for handling cookies: · Do not use cookies - This is the same as disabling cookies in your Internet browser. TestComplete will ignore all cookies while running the load test. · Use recorded cookies - Cookies will affect the server response and the server should produce the same responses as recorded. However, since cookies can have expiration dates, the response may be an error. · Use real-time cookies - The default selection, TestComplete will replace the cookies as needed from the web server responses. The default for a visually created tests is to set the ClearCookies property of the virtual s to true. When the ClearCookies property is true, all cookies are automatically recreated. If you want cookies to be recreated, cookies need to be cleared before starting a load test for virtual s created in script.

19.5

Recording Recording HTTP traffic is similar to standard recording. One difference - it is easier if you have your client application (Internet Explorer, Firefox, etc) started, and in the case of web browsers, on the web page you want to start on. Also, if not using Internet Explorer, you will need to configure TestComplete as the proxy server for the client application.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

HTTP Performance Testing

225

Note: It is also a good idea to clear the cache of the web browser you are using before recording. Tip: If you are planning to modify the recorded HTTP traffic and using 'classic' ASP.NET (using viewstate), turn off HTTP 1.1 in the web browser before recording. This will prevent the web server from using HTTP compression, but makes it easier to modify the traffic. 1. Start by clicking the record button in TestComplete. On the recording toolbar, click the "Record an HTTP task" button.

2. To select a load testing task either: Enter a name under Record a new task for a new task. Select Append traffic to the following task and select an existing task. This will add the http traffic to an existing task.

3. If you are using Internet Explorer and have not setup TestComplete as proxy server, TestComplete will offer to set itself up as a proxy server, click the Yes button.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

226

TestComplete Made Easy

Tip: If you are using Internet Explorer 7 and are recording against the localhost, IE will ignore your proxy server settings. You can get around this problem by adding a period after the localhost. Example use "http://localhost./loadtesting/LoadTestingDemo.dll?action=new" instead of "http://localhost/loadtesting/LoadTestingDemo.dll?action=new". Now just record your activities as you would normally do.

4. When the recording is done, you will end up with a script for running a load test with one single virtual .

[VBScript] Sub Test1 Dim HTTPTask Dim Virtual Set HTTPTask = LoadTesting.HTTPTaskByName("Task") Set Virtual = LoadTesting.CreateVirtual("Virtual1") Set Virtual.Task = HTTPTask Call Virtual.Run("Task") End Sub

[JScript] function Test1() { var HTTPTask; var Virtual; HTTPTask = LoadTesting.HTTPTaskByName("Task"); Virtual = LoadTesting.CreateVirtual("Virtual1"); Virtual.Task = HTTPTask; Virtual.Run("Task"); }

5. The recorded task will be under the Tasks project item under the LoadTesting project item in the Project Explorer.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

HTTP Performance Testing

227

6. Double-click on the Task to get a look at the recorded HTTP traffic.

19.6

Connections, Requests and Responses A load testing task in TestComplete will consist of one or more connections to the web server. Within these connections are requests that TestComplete sends and the recorded or expected response that TestComplete receives.

The request page holds the properties of the currently selected requestion in the Connections tree. The fields of the request header are shown in the table. All of these fields can be modified directly or in script code. The request method (POST or GET) is shown in the edit box above the fields (note: the protocol version is also shown). The "Raise Events" option is used to indicate this request will trigger an OnLoadTestingRequest event during playback. OnLoadTestingRequest will allow modification of the request before sending to the web server. Copyright © 2008 AutomatedQA Corp. - 1.0 Release

228

TestComplete Made Easy

The response page shows the properties and contents of the response from the web server for the selected request. Depending on the Content-Type, TestComplete will show the response content below the properties grid. For example, an image request will show the image, a SOAP request will show the SOAP response, etc. Again, the information can be edited here or changed in script code. The "Raise Events" checkmark will call the OnLoadTestingResponse for the selected request/ response pair.

19.7

Visual Creation of a Load Test Load Tests can be created both visually and in script. To create a load test visually: 1. Select the "Tests" project item under the Load Testing project item

2. Right-click and select Add | New Item... 3. Name the Test.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

HTTP Performance Testing

229

4. Enter a "Description" for the test 5. Enter or select a "Result Group". Result groups are used to categorize groups of test runs for analysis. 6. Right-click in the Virtual s area and select New Item.

7. Enter a name for the group of s 8. Enter the number of virtual you want for this group (it is not recommend that more the 300 virtual s be assigned to a computer). 9. Choose which task this group of is going to perform. 10.Assign the group to run on a particular computer (Master is the local computer). 11.Choose which browser to simulate in the request. 12.The start delay is how long after the test starts to kick off this group (simulating a gradual increase in load). 13.Change the connection speed to simulate the speed of the . Once you are finished creating the test, you can run the test by right clicking and selecting Run.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

230

19.8

TestComplete Made Easy

Analysis of the Test Log The load test log is broken up into parts. The top part shows how each virtual did overall.

The column headings are as follows: · Virtual # in the order they complete their task. · Did the complete the task without error/warnings · Virtual Name. · The task performed. · Which station the task was performed. · The total time need to complete the task. · The number of connections simulated in the task. The middle section shows how each of the connections did for the currently selected from the s section.

The green line in graph shows the actual request execution sum, the red line show the total time to perform all requests. Column heading are: · State (did this connection or fail). · Host that the connection was run against. · Which port the connection used. · How long it took to Initialize the connection. · Number of requests in this connect. · The total time to simulate this connection. · Total Bytes received from the web server for this connection. · Total Bytes sent to the web server for this connection. · How long after the start of the load test was this request sent. · How many bytes per a second where sent/received. Copyright © 2008 AutomatedQA Corp. - 1.0 Release

HTTP Performance Testing

231

· The time of day the connection was started. · How long it took to do the request. · The minimum response time for all the requests in this connection · The maximum response time for all the requests in this connection The bottom section is divided into two parts, Requests and Headers:

Requests columns are: · Request # in the selected connection. · The State of the request. · The time to do the request. · # of bytes sent. · how long until a response. · # of bytes received. · # of bytes sent/received per a second. · # of bytes sent per a second. · # of bytes received per a second. The Headers area shows the actual headers sent and received for the selected request.

Comparing Multiple Test Runs There is another type of log created that allows comparisons of multiple test runs. Found in the project explorer under the project suite name and ending with the word "Analysis"

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

232

TestComplete Made Easy

Select the named group you are interested in and you will get the results of all the test runs for that group.

19.9

Modifying HTTP Traffic With TestComplete you can modify HTTP traffic as necessary. For example, you may want to change the properties of the HTTP request and modify it directly before running the HTTP task. [VBScript] Sub Test1 Dim HTTPTask Dim Request Dim Virtual Set HTTPTask = LoadTesting.HTTPTaskByName("Order") Set Request = HTTPTask.Connection(0).Request(0) Randomize Request.Variables.Item("paints") = Int(1000 * Rnd()) + 1 Request.Variables.Item("pencils") = Int(1000 * Rnd()) + 1 Request.Variables.Item("albums") = Int(1000 * Rnd()) + 1 Set Virtual = LoadTesting.CreateVirtual("Virtual1") Set Virtual.Task = HTTPTask Call Virtual.Run("Order") End Sub

[JScript] function Test1() { var HTTPTask var Request var Virtual HTTPTask = LoadTesting.HTTPTaskByName("Order") Request = HTTPTask.Connection(0).Request(0) Request.Variables.Item("paints") = Math.round(100 * Math.random()) + 1 Request.Variables.Item("pencils") = Math.round(100 * Math.random()) + 1 Request.Variables.Item("albums") = Math.round(100 * Math.random()) + 1

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

HTTP Performance Testing

233

Virtual = LoadTesting.CreateVirtual("Virtual1") Virtual.Task = HTTPTask Virtual.Run("Order") }

Caution: There is one warning with this method, since you are making a copy of the HTTP task for each virtual , it is possible to consume too much memory causing a slow down of the test.

The Second method is to use the OnLoadTestingRequest event to modify the traffic. To use OnLoadTestingRequest, first checkmark the raise events on all the request you wish to modify.

You can also configure events to be raised in code: [VBScript] Sub Test1 Dim HTTPTask Dim Virtual Set HTTPTask = LoadTesting.HTTPTaskByName("Task") HTTPTask.Connection(0).Request(0).RequestEventTrigger = True Set Virtual = LoadTesting.CreateVirtual("Virtual1") Set Virtual.Task = HTTPTask Call Virtual.Run("Task") End Sub

[JScript] function Test4() { var HTTPTask; var Virtual HTTPTask = LoadTesting.HTTPTaskByName("Order") HTTPTask.Connection(0).Request(0).RequestEventTrigger = true Virtual = LoadTesting.CreateVirtual("Virtual1"); Virtual.Task = HTTPTask; Virtual.Run("Task"); }

Next, add the OnLoadTestingRequest event handler. Open the editor for Events from the Project Explorer and click the New button next to the OnLoadTestingRequest in the HTTP LoadTesting Events category.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

234

TestComplete Made Easy

Click OK in the New Routine Dialog and add script code to modify the request: [VBScript] Sub GeneralEvents_OnLoadTestingRequest(Sender, , Request) Request.Variables.Item("paints") = Int(1000 * Rnd()) + 1 Request.Variables.Item("pencils") = Int(1000 * Rnd()) + 1 Request.Variables.Item("albums") = Int(1000 * Rnd()) + 1 End Sub

[JScript] function GeneralEvents_OnLoadTestingRequest(Sender, , Request) { Request.Variables.Item("paints") = Math.round(100 * Math.random()) + 1 Request.Variables.Item("pencils") = Math.round(100 * Math.random()) + 1 Request.Variables.Item("albums") = Math.round(100 * Math.random()) + 1 }

19.10 Hands on Lab: Working with HTTP Traffic Basic HTTP Recording and Playback 1. Create a new project and project suite using HTTP load testing template

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

HTTP Performance Testing

2. Start up Internet Explorer and open the www.automatedqa.com web page. 3. Switch from recording a script to recording HTTP traffic.

4. Record an HTTP Load Test. · Enter ‘TestComplete in the search and hit the Enter key. · Click the ‘ Us’ link. · Click the ‘Home’ link. · Stop the recording. 5. Double-click the newly created Task in the Project Explorer. 6. In the task editor, delete connections that do not point to www.automatedqa.com:

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

235

236

TestComplete Made Easy

7. Right-click on the Tests Project Item of the LoadTesting Project Item in the Project Explorer and Select Add | New Item... 8. Press OK in the Create Project Item Dialog. 9. Create an HTTP Load Testing with five virtual s. · Add a description "HTTP Lab" · Add a Result Group "HTTP Lab" · Make sure that "Run concurrently" is check marked. · Right-click the white area under virtual s and select New Item from the context menu. · Change the Count to 5 · Set the Task to the name of new created task. · Set the workstation to "Master" 10.Right-click the newly created Test and select Run from the context menu. 11.Examine the newly created test log.

Modify Traffic Using the OnLoadTestingRequest Event. 1. In the HTTP Task select the first request and check mark Raise Events.

2. In the Events Editor, select OnLoadTestingRequest and click the New button.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

HTTP Performance Testing

237

3. Click the OK button in the New Routine dialog. 4. Add the following code:

[VBScript] Dim SearchValues SearchValues = Array("TestComplete","AQtime","Automated Build Studio") Randomize Sub GeneralEvents_OnLoadTestingRequest(Sender, , Request) Request.Variables.Item("search") = Escape(SearchValues(Int(3 * Rnd()))) End Sub

[Jscript] var SearchValues = new Array("TestComplete","AQtime","Automated Build Studio"); function GeneralEvents_OnLoadTestingRequest(Sender, , Request) { Request.Variables.Item("search") = escape(SearchValues[Math.round(3 * Math.random())]) }

5. Right-click on the Test created from the first part of the lab and select Run from the context menu. 6. Examine the Headers for the different to see the changes in the traffic.

19.11 Summary In this section, we have learned about HTTP Performance testing and the types of performance testing such as load, stress and scalability. We have learned how to record HTTP traffic and how to modify the traffic before sending request to the web server.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Part

XX Remote Agent

Remote Agent

20

Remote Agent

20.1

Objectives

239

Remote Agent is a tool that allows for the distribution of HTTP loads tests across a network of computers. In this section you will learn: · Installing Remote Agent · Running Remote Agent · Configuring Remote Agent · Using Remote Agent for HTTP Load Testing

20.2

Installing Remote Agent AutomatedQA provides a separate, standalone installation of Remote Agent allowing for easy deployment to other machines on a network. Remote Agent can be installed in two modes, console mode which runs on your Windows Desktop or as a Windows service. In both instances Remote Agent is started when the machine starts though if there is no active logged onto the machine the Service mode will still be available for use whereas console mode requires a to be logged onto the machine. During installation, you will be prompted to select which mode you want Remote Agent to use:

20.3

Running Remote Agent During the installation of Remote Agent you selected a mode indicating how it should be executed either console mode or as a Windows service. In both cases, Remote agent is launched automatically when Windows starts. In the case of console mode, Remote Agent is started as soon as a logs onto the machine whereas in service mode, Remote Agent is started when Windows is started regardless of whether or not a is logged on.

Console Mode When running Remote Agent in console mode you'll see this window on your Windows Desktop:

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

240

TestComplete Made Easy

To exit Remote Agent from this mode simple activate the window by clicking on it and press Escape.

Service Mode When Remote Agent is installed in service mode there is no visible UI that will appear. To control the execution of Remote Agent you need to change the settings under Windows Services. In XP, you can view Windows Services Window by running the command "services.msc" from the Run command on the Windows Start menu.

You should see a window that looks like this:

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Remote Agent

241

From this window you can right click on TestComplete 6 HTTP Load Testing Remote Agent and change its Startup Type.

20.4

Configuring Remote Agent Remote Agent s several different configuration settings stored in an XML file located in \Program Files\Automated QA\TestComplete 6\RAS\Bin\ras.config which is created when Remote Agent is executed for the first time. This file is an XML file that can be edited using any plain text file editor such as Windows Notepad. Below is a table listing the available options that can be configured via the ras. config XML file: NOTE: In TestComplete 6.3 and later Remote Agent (RA) is implemented as a Distributed COM (DCOM) server meaning it listens in on the standard Microsoft DCOM port of 135. Additionally, TestComplete will try to connect to Remote Agent through port 135 as well. Setting

Description

ra port

As of TestComplete 6.3 this setting is obsolete.

description

Any descriptive string concerning the Remote Agent instance on the computer.

use proxy

0-1. Set this option to 1, if -· There is a proxy server between the computer where the Remote Agent and the

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

242

TestComplete Made Easy

tested Web server is installed. · There is a proxy server between the Remote Agent computer and the computer where TestComplete executes. · If the Remote Agent has direct access to the tested Web site and the TestComplete computer, you may set this option to 0. Default value: 0. proxy host

Specifies the proxy server that the Remote Agent uses to connect to the tested Web site and to the computer where TestComplete runs. This can be either the computer name, or IP address. This option is ignored if the use proxy option is set to 0.

proxy port

Specifies the port which the Remote Agent uses to connect to the proxy server specified by proxy host. Default value: 8080. This option is ignored if the use proxy option is set to 0.

proxy

Specifies the name under which you want to connect to the proxy server (if it requires authentication).

proxy

Specifies the that confirms the identity of the under whose name you want to connect to the proxy server (if it requires authentication).

Note: Do not forget to end the RA process (stop its service) before changing its settings and then restarting RA afterwards.

The XML file appears as follows: ]>

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Remote Agent

243



Configuring a Proxy Server If your organization uses a proxy server to connect to the web you'll need to configure Remote Agent to use the proxy server. To do that you need to edit the above XML file using any plain text editor like Windows Notepad. For example, to configure a proxy server you would: 1. Start Windows Notepad 2. Open \Program Files\Automated QA\TestComplete 6\RAS\Bin\ras.config 3. Look for the with the following Name attributes and change them accordingly: · proxy host - change the value attribute to the server domain name or IP address of the proxy server · proxy - change the value attribute to the for the proxy server, if any · use proxy - change the value attribute to 1 to enable the proxy · proxy port - change the value attribute to the port number used for the proxy

20.5

Hands on Lab: Working with Remote Agent for HTTP Load Testing To use Remote Agent you need to setup an HTTP Load Testing project in TestComplete. The Load Testing project has features that allow you to leverage Remote Agent running on multiple machines for testing web applications or services.

Creating an HTTP Load Testing Project 1. Start TestComplete and select File|New|Project

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

244

TestComplete Made Easy

2. On the Create New Project dialog select HTTP Load Testing and click OK 3. Click the Finish button on the Project Wizard dialog to create your new project Once created the new project will display the following nodes (based on your TestComplete settings your project may vary slightly):

The LoadTesting node contains the items of interest for conducting HTTP Load testing. These

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Remote Agent

245

nodes are: · Stations - represents the machines that will be conducting the tests. The Master sub-node represents the machine that TestComplete is running on. · Tasks - is the HTTP traffic you’re interested in testing. · Tests - allows you to assign tasks to various stations for test execution.

Working with Stations In order to leverage Remote Agent running on networked machines you'll need to configure the machines under the Stations node. To add a machine that is running Remote Agent do the following: 1. Right click the stations node and select Add|New Item... You will see a dialog that allows you to configure a networked machine that's running Remote Agent.

2. In the Host edit box enter the machine name or IP address. 3. Change the Name edit box to something more meaningful. Note: You'll be able to change all of these settings from the project's Workspace so don't worry if you make a mistake. You can add and remove Stations from your project as necessary from the Project Explorer. Also, note that as of TestComplete 6.3 the port setting is obsolete, the standard Microsoft DCOM port of 135 will be used instead.

Setting up Tasks The next step is to create the HTTP traffic you want to load test your server with. The easiest way to

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

246

TestComplete Made Easy

produce traffic is using TestComplete’s recording facilities. For HTTP load testing this requires setting TestComplete to be a proxy for your web browser. 1. Configure Internet explorer to use TestComplete as a proxy allowing it to monitor and record HTTP traffic. For IE you can do that from the Connections tab of the Internet Options dialog setting the proxy to localhost on port 9999. For Firefox open the Tools | Options dialog and look on the Advanced page, under the Network tab. 2. Click the record button on the TestComplete toolbar and once recording begins click the Record an HTTP Task button (circled in red below):

3. This will bring up the Select Load Testing dialog where you can decide to record a new HTTP traffic or append it to an existing task. 4. Once you click OK you can begin recording HTTP traffic by simply using your browser. TestComplete will record the HTTP traffic and add it to the task you specified.

Asg Tasks to be Executed by Remote Agents Once you've added Stations to your project and created HTTP Tasks for execution you need to configure which Tasks which be executed by which Stations: 1. Right-click the Tests node in the Project Explorer and select Add | New Item... 2. On the Create Project Item dialog Name the testing accordingly and click OK. 3. Right-click the Virtual s grid and select New Item. This will create a new entry in the Virtual s table and allow you to assign work for a particular Remote Agent. 4. To specify a Task to execute, click the Task cell in the grid and select a task from the drop down list. 5. To specify a Workstation (a.k.a. Remote Agent) click the Workstation cell and use the dropdown to specify a particular Remote Agent. Once completed your Virtual s should appear something like this:

At this point, you're ready to leverage Remote Agent and execute your tests harnessing the power of your networked machines to HTTP Load Test your web applications.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Remote Agent

20.6

247

Summary Remote Agent is a tool that allows for the distribution of HTTP loads tests across a network of computers. With Remote Agent installed a single TestComplete can quickly and easily harness the power of a network to provide real world load testing of HTTP based web applications. In addition, Remote Agent has a small footprint and separate install allowing it to be easily deployed for rapid HTTP load testing.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Part

XXI Distributed Testing

Distributed Testing

21

Distributed Testing

21.1

Objectives

249

This section explains how tests are run on several computers at the same time. In this section you'll learn: · What is a Distributed Test. · What are the parts of a Distribute Test. · How to setup a Distribute Test. · How to use Synoints. · How to use Network Suite Variables.

21.2

Network Suites Distributed Testing is the ability of TestComplete to control test cases running on several computers at the same time. In addition to running the tests, the computers involved can communicate with each other using TestComplete. In order to perform a distributed test, all projects involved must contain the Network Suite project item. In additional, all the computers involved must have the same version of TestComplete/TestExecute on them (including the minor version number). Most of the setup of a distributed test, takes place in the master project. The minimum you need to run a distributed test is a master project with at least one host machine and at least one task for that host machine to run. The root level of Distributed Testing is the Network Suite:

The workspace editor for NetworkSuite consists of three parts: 1. Properties - This is where you can setup a shared path for all the computers to use in testing. TestComplete uses this path to create a network shared folder during the run of the network suite.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

250

TestComplete Made Easy

2. Variables - Using these variables, the computers involved in the test can data to each other. This data can only be of types; string, integer, double or Boolean.

3. Run State - This displays the state of each computer during the test run.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Distributed Testing

21.3

251

Hosts Hosts are the secondary computers involved in the test. Hosts need to have either TestComplete or TestExecute on them and can be addressed by either name or IP address. The base path is where the computer will start looking for the project to run the test (not required).

Since firewall and other network communication issues can happen, it is recommend that you the existence of the host. Right-click the workspace to get the context menu and click .

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

252

21.4

TestComplete Made Easy

Jobs/Tasks Jobs and Tasks are where tests to be run are controlled. A Job consists of one or more host computers tasks. Each job is run to completion before the next job is run. Under each Job are the Tasks (tests) to be run on the host computer. Each host computer can only be used once in a job for an active task.

Tasks have the following properties: 1. Active - Whether or not the test is run. 2. Name - Name of the task. 3. Path - Path to the TestComplete project that holds the test to be run (relative to the host computer). 4. Copy the remote log - Controls if the master computer gets a copy of the log file from the host computer.

5. Action after run - Determines the action to take after the test completes on the host computer.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Distributed Testing

253

6. Tag - A value sent to the host computer at the start of the test. 7. Test - The test to be run. If left blank it will be the project/project suite from the path property. 8. Use previous instance - Controls what to do if TestComplete/TestExecute is already running on the host computer.

9. Remote application - Whether to use TestComplete or TestExecute on the host computer.

.

21.5

SynchPoints SynchPoints delay execution of the test until all computers with that synch point name reach the synchronization point. When all the computers with a named SynchPoint hit that Synchronize Point, they will continue on with their test. An example of an effective use for SynchPoints: you want to avoid where two or more s try to edit the same record at the same time and post the data.

21.6

Setup Simple Distributed Test

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

254

TestComplete Made Easy

1. Create a master project with a NetworkSuite Project Item. 2. Create a hosted (slave) project with a NetworkSuite Project Item.

3. Add notepad to the TestedApps project Item of the hosted project. 4. Modify the File Path property of the TestedApp to "" (blank) 5. Create (or record) a script method to type something into notepad.

[VBScript] Sub Test1 Dim p1 Dim w1 TestedApps.notepad.Run Set p1 = Sys.Process("notepad") Set w1 = p1.Window("Notepad", "*").Window("Edit") w1.HScroll.Pos = 0 w1.VScroll.Pos = 0 Call w1.Click(135, 29) Set w1 = p1.Window("Notepad", "*") Call w1.Window("Edit").Keys("TestComplete Training - Distributed Testing") w1.Close p1.Window("#32770", "Notepad").Window("Button", "&No").ClickButton End Sub

[JScript] function Test1() { var p1 var w1 TestedApps.notepad.Run(); p1 = Sys.Process("notepad"); w1 = p1.Window("Notepad", "*").Window("Edit"); w1.HScroll.Pos = 0;

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Distributed Testing

255

w1.VScroll.Pos = 0; w1.Click(135, 29); w1 = p1.Window("Notepad", "*"); w1.Window("Edit").Keys("TestComplete Training - Distributed Testing"); w1.Close(); p1.Window("#32770", "Notepad").Window("Button", "&No").ClickButton(); }

6. Save the project. 7. Select the NetworkSuite Project Item in the Master Project and enter the path to the project suite in the Shared Path.

8. Expand the Hosts Project Item and select Host1 9. Enter the name (or IP address) of the hosting (slave) computer. 10.In the Base path property enter "\\<Master Computer Name>\ "

11.Right-click on Host1 and select from the context menu. 12.Expand the Jobs Project Item. 13.Expand the Job1 Project Item. 14.Select the Task1 Project Item. 15.In the Path property enter "\ \ .mds". 16.In the Copy remote log property select "[Always]". 17.In the Use previous instance property select "[Use]". 18.In the Test property enter " \Script\Unit1\Test1".

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

256

TestComplete Made Easy

19.Right-click Task1 and select from the context menu. 20.With verification, the NetworkSuite is ready to run. Right-click the NetworkSuite project item and select Run from the context menu.

Using NetworkSuite Variables NetworkSuite variables allow TestComplete to send data from one computer to another. 1. Modify the test in the hosted (slave) project.

[VBScript] Sub Test1 Dim p1 Dim w1 TestedApps.notepad.Run Set p1 = Sys.Process("notepad") Set w1 = p1.Window("Notepad", "*").Window("Edit") w1.HScroll.Pos = 0 w1.VScroll.Pos = 0 Call w1.Click(135, 29) Set w1 = p1.Window("Notepad", "*") Call w1.Window("Edit").Keys(NetworkSuite.Variables.Var1) w1.Close p1.Window("#32770", "Notepad").Window("Button", "&No").ClickButton End Sub

[JScript] function Test1() { var p1 var w1 TestedApps.notepad.Run(); p1 = Sys.Process("notepad"); w1 = p1.Window("Notepad", "*").Window("Edit"); w1.HScroll.Pos = 0; w1.VScroll.Pos = 0; w1.Click(135, 29); w1 = p1.Window("Notepad", "*"); w1.Window("Edit").Keys(NetworkSuite.Variables.Var1); w1.Close(); p1.Window("#32770", "Notepad").Window("Button", "&No").ClickButton(); }

2. Add the variable "Var1" to the master project.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Distributed Testing

257

3. Change the Local Value property to "TestComplete Rocks" 4. Right-click the NetworkSuite project item and select Run from the context menu. On the host (slave) computer, you will see "TestComplete Rocks" typed into notepad.

Synchronizing computers There are times when you want to have one computer wait for another computer to complete at least part of its task before finishing the first computer's task. For example, you want the consumer's computer to wait until the bank's computer has processed a debit before the consumer's computer checks it balance. We will show a couple of ways to synchronize. Using Synoints 1. Modify the test in hosted (slave) project.

[VBScript] Sub Test1 Dim p1 Dim w1 TestedApps.notepad.Run Set p1 = Sys.Process("notepad") Set w1 = p1.Window("Notepad", "*").Window("Edit") w1.HScroll.Pos = 0 w1.VScroll.Pos = 0 Call w1.Click(135, 29) Set w1 = p1.Window("Notepad", "*") Call w1.Window("Edit").Keys(NetworkSuite.Variables.Var1) Call w1.Window("Edit").Keys("[Enter]") NetworkSuite.Synchronize("SynchPoint1") Call w1.Window("Edit").Keys(NetworkSuite.Variables.Var1) w1.Close p1.Window("#32770", "Notepad").Window("Button", "&No").ClickButton End Sub

[JScript] function Test1() { var p1 var w1 TestedApps.notepad.Run(); p1 = Sys.Process("notepad"); w1 = p1.Window("Notepad", "*").Window("Edit"); w1.HScroll.Pos = 0; w1.VScroll.Pos = 0; w1.Click(135, 29); w1 = p1.Window("Notepad", "*"); w1.Window("Edit").Keys(NetworkSuite.Variables.Var1); w1.Window("Edit").Keys("[Enter]"); NetworkSuite.Synchronize("SynchPoint1"); w1.Close();

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

258

TestComplete Made Easy

p1.Window("#32770", "Notepad").Window("Button", "&No").ClickButton(); }

2. Right-click the Synoints Project Item, select Add | New Item... from the context menu. 3. Hit Enter on the Create Project Item dialog. 4. Create a script in the master project.

[VBScript] Sub Test1 NetworkSuite.Run(false) NetworkSuite.WaitForState(ns_Running) Delay(30000) NetworkSuite.Variables.Var1 = "Rocks" NetworkSuite.Synchronize("SynchPoint1") NetworkSuite.WaitForState(ns_Idle) End Sub

[JScript] function Test1() { NetworkSuite.Variables.Var1 = "TestComplete"; NetworkSuite.Run(false); NetworkSuite.WaitForState(ns_Running); Delay(30000); NetworkSuite.Variables.Var1 = "Rocks"; NetworkSuite.Synchronize("SynchPoint1"); NetworkSuite.WaitForState(ns_Idle); }

5. Right-click the Synoints Project Item, select Add | New Item... from the context menu. 6. Hit Enter on the Create Project Item dialog. 7. Right-Click in the newly created script and select Run Current Routine from the context menu. On the hosted computer, "TestComplete" will be typed, followed by a delay and then on a new line "Rocks" will be typed. Using NetworkSuite Variables 1. Modify the test in hosted (slave) project.

[VBScript] Sub Test1 Dim p1 Dim w1 TestedApps.notepad.Run Set p1 = Sys.Process("notepad") Set w1 = p1.Window("Notepad", "*").Window("Edit") w1.HScroll.Pos = 0 w1.VScroll.Pos = 0 Call w1.Click(135, 29) Set w1 = p1.Window("Notepad", "*") Call w1.Window("Edit").Keys(NetworkSuite.Variables.Var1) Call w1.Window("Edit").Keys("[Enter]") NetworkSuite.Variables.Var2 = True Call NetworkSuite.WaitForNetVarChange("Var2",false) Call w1.Window("Edit").Keys(NetworkSuite.Variables.Var1) w1.Close

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Distributed Testing

259

p1.Window("#32770", "Notepad").Window("Button", "&No").ClickButton End Sub

[JScript] function Test1() { var p1 var w1 TestedApps.notepad.Run(); p1 = Sys.Process("notepad"); w1 = p1.Window("Notepad", "*").Window("Edit"); w1.HScroll.Pos = 0; w1.VScroll.Pos = 0; w1.Click(135, 29); w1 = p1.Window("Notepad", "*"); w1.Window("Edit").Keys(NetworkSuite.Variables.Var1); w1.Window("Edit").Keys("[Enter]"); NetworkSuite.Variables.Var2 = true; NetworkSuite.WaitForNetVarChange("Var2",false); w1.Window("Edit").Keys(NetworkSuite.Variables.Var1); w1.Close(); p1.Window("#32770", "Notepad").Window("Button", "&No").ClickButton(); }

2. Create a script in the master project. [VBScript] Sub Test2 NetworkSuite.Variables.Var1 = "TestComplete" NetworkSuite.Run(false) Call NetworkSuite.WaitForNetVarChange("Var2",true) NetworkSuite.Variables.Var1 = "Rocks" NetworkSuite.Variables.Var2 = False NetworkSuite.WaitForState(ns_Idle) End Sub

[JScript] function Test2() { NetworkSuite.Variables.Var1 = "TestComplete"; NetworkSuite.Run(false); NetworkSuite.WaitForNetVarChange("Var2",true); NetworkSuite.Variables.Var1 = "Rocks"; NetworkSuite.Variables.Var2 = false; NetworkSuite.WaitForState(ns_Idle); }

3. Add the variable "Var2" to the master project in the NetworkSuite project item. 4. Right-click in the newly created script and select Run Current Routine from the context menu. The hosted computer will do the same things as the Synoint demo, but with less delay in the project. Notice that the hosted computer can data back to the master computer.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

260

21.7

TestComplete Made Easy

Summary In this section we learned how tests are run on several computers at the same time. We also learned how to script Distributed Tests using Synchronize Points and Network Suite Variables.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Part

XXII Forms

262

TestComplete Made Easy

22

Forms

22.1

Objectives This section demonstrates how to create forms and manipulate them using script: In this section you'll learn: · What is a form. · Learn how to create an form. · How to access forms in script.

22.2

Creating Creating a form in TestComplete is very similar to creating a form in most development IDEs (Visual Studio, Eclipse, Rad Studio). First add the Forms project Item to the project. The Forms project item is a holder (folder) for all the forms created in the project. The next step is to add an form to the project (right-click of the Forms project item and Add | New Items...". In our example, we will create a simple name and dialog.

The left side of the editor contains the components that can be added to the form. The middle is the actual form. And the right side is where the properties and events are setup. Components are added by dragging with the mouse and dropping on the form. The components that we use are TcxTextEdit (from the Editors Category), TcxButton (Buttons Category) and TcxLabel (Helpers Category). We will two of each.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Forms

263

We will also need to set the properties for all of the components (only changed properties shown): Property

Value

Form Caption

Enter Information:

Height

130

Width

450

cxButton1 Caption

OK

Default

True

ModalResult

mrOK

cxButton2 Cancel

True

Caption

Cancel

ModelResult

mrCancel

cxLabel1 Caption

Name:

cxLabel2 Caption

:

edt (Renamed from cxTextEdit1) Name

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

edt

264

TestComplete Made Easy

edt (Renamed for cxTextEdit2)

22.3

Name

edt

Properties.EchoMode

eem

Scripting Now that we have created a form, we need to learn how to use the form in a script. There are two method used to display an form - Show() and ShowModal(). In our example we will use ShowModal(), which displays the form and stops the script from playing until the answers the dialog. Note: Show() will continue with the next line in the script code. [VBScript] Sub Main 'Fill in the current name Forms.NameAnd.edt.Text = Sys.Name if Forms.NameAnd.ShowModal = mrCancel Then Runner.Halt(" Cancelled Test") end If Log.Message(": " & Forms.NameAnd.edt.Text &_ " Logged in with : " &_ Forms.NameAnd.edt.Text) End Sub

[JScript] function Main() { //Fill in the current name Forms.NameAnd.edt.Text = Sys.Name; if (Forms.NameAnd.ShowModal() == mrCancel) Runner.Halt(" Cancelled Test"); Log.Message(": " + Forms.NameAnd.edt.Text + " Logged in with : " + Forms.NameAnd.edt.Text); }

22.4

Summary In this chapter, we learned the basics of creating a form. Then we learned how to display the form to the and get information from the form.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Part

XXIII Best Practices

266

TestComplete Made Easy

23

Best Practices

23.1

General The following are general tips and best practices to help you get the most out of TestComplete: · Record/Playback is a quick and easy way to get automated tests up and running but tend to be brittle leading to problems when the application changes, etc. · Use the TestItems of the project as a framework for Test Cases.

· Separate Data from the Test Framework (see Data-Driven Testing). · Use the code metrics of the Code Explorer to improve the quality of the script code.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Best Practices

267

· Use Name Mapping and Aliases whenever possible, it is worth the time to setup. · Use reusable routines whenever possible. · Keep routines short (less than a page of code). · Use meaningful variable names (The default variable names of a recording are not very good variable names).

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

268

23.2

TestComplete Made Easy

Web Page The following are tips for making effective use of TestComplete when testing web pages: · Make the Page object a child of the browser process.

· Use either the Hybrid or Tree "Tree Model".

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Part

XXIV Cheat Sheet

270

TestComplete Made Easy

24

Cheat Sheet

24.1

Keyboard Shortcuts Global Shortcuts (keys that work when TestComplete is running even if TestComplete does not have focus) Command

Default Key

Pause script execution

SHIFT-10

Fix Information

SHIFT-CTRL-A

Record

SHIFT-F1

Stop

SHIFT-F2

Run

SHIFT-F3

Pause recording

SHIFT-F11

Load Testing Record

SHIFT-F6

Low Level Record

SHIFT-F4

Key Mapping (keys that work when TestComplete has focus, generally in the editors) Command/Section

Default

Visual Studio

Borland Classic

Run

F9

F5

F9

Reset

CTRL-F2

SHIFT-F5

CTRL-F2

Step Over

F8

F10

F8

Trace Into

F7

F11

F7

Run to Cursor

F4

F4

F4

Switch Breakpoint

F5

F9

CTRL-F8

View Evaluate

CTRL-F7

CTRL-F2

CTRL-F4

View Call Stack

CTRL-ALT-S

ALT-7

CTRL-ALT-S

View Watches

CTRL-ALT-W

ALT-3

CTRL-ALT-W

View Break Points

CTRL-ALT-B

CTRL-B

CTRL-ALT-B

CTRL-F4

CTRL-F4

ALT-F3

Debugging

Project/Units Close Page

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Cheat Sheet

Save Unit

CTRL-S

CTRL-S

CTRL-S

Open Project

CTRL-F11

CTRL-SHIFT-0

CTRL-F11

New Project

CTRL-SHIFT-N

Save All

CTRL-SHIFT-S

CTRL-SHIFT-S

271

Display previous page

CTRL-SHIFT-TAB

CTRL-SHIFT-TAB

CTRL-SHIFT-TAB

Display next page

CTRL-TAB

CTRL-TAB

CTRL-TAB

Cursor Left

LEFT

LEFT

LEFT

Cursor Right

RIGHT

RIGHT

RIGHT

Beginning of Line

HOME

HOME

HOME

End of Line

END

END

END

Up one line

UP

UP

UP

Down one line

DOWN

DOWN

DOWN

Up one page

PGUP

PGUP

PGUP

Down one page

PGDN

PGDN

PGDN

Beginning of Document

CTRL-HOME

CTRL-HOME

CTRL-PGUP

End of Document

CTRL-END

CTRL-END

CTRL-PGDN

Move to word before

CTRL-LEFT

CTRL-LEFT

CTRL-LEFT

Move to word after

CTRL-RIGHT

CTRL-RIGHT

CTRL-RIGHT

Delete character at cursor

DEL

DEL

DEL

Delete character before cursor

BACKSPACE

BACKSPACE

BACKSPACE

Delete current line

CTRL-Y

CTRL-SHIFT-L

CTRL-Y

Delete previous word

CTRL-BACKSPACE

CTRL-BACKSPACE

CTRL-BACKSPACE

Delete next word

CTRL-T

CTRL-DEL

CTRL-T

CTRL-SHIFT-I or TAB

CTRL-SHIFT-I

CTRL-SHIFT-I

CTRL-SHIFT-U

CTRL-SHIFT-U

Cursor movement

Delete operations

Miscellaneous Indent selected block

Unindent selected block CTRL-SHIFT-U or SHIFT-TAB

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

272

TestComplete Made Easy

Toggle insert/overwrite mode

INS

INS

INS

Undo

CTRL-Z or ALTBACKSPACE

CTRL-Z or ALTBACKSPACE

ALT-BACKSPACE

Redo

SHIFT-CTRL-Z or

SHIFT-CTRL-Z or

ALT-SHIFTBACKSPACE

ALT-SHIFTBACKSPACE

ALT-SHIFTBACKSPACE

CTRL-P

CTRL-P

CTRL-P

Scroll display up one line CTRL-UP

CTRL-UP

CTRL-W

Scroll display down one line

CTRL-DOWN

CTRL-DOWN

CTRL-Z

Display context menu

ALT-F10 (Code Editor only)

ALT-F10 (Code Editor only)

ALT-F10 (Code Editor only)

Find

CTRL-F

CTRL-F

CTRL-F

Replace

CTRL-R

CTRL-H

CTRL-R

Search Again

F3

F3

CTRL-L

Select All

CTRL-A

CTRL-A

Print

Invoke Code Completion CTRL-SPACE

CTRL-SPACE

CTRL-SPACE

Code Templates

CTRL-J

CTRL-J

Set Numbered Bookmark CTRL-SHIFT-#

CTRL-SHIFT-#

CTRL-SHIFT-#

Goto Numbered Bookmark

CTRL-#

CTRL-#

CTRL-#

Set Unnumbered Bookmark

CTRL-SHIFT-'

CTRL-SHIFT-'

CTRL-SHIFT-'

Goto Unnumbered Bookmark

CTRL-'

CTRL-'

CTRL-'

Cut to Clipboard

CTRL-X or SHIFT-DEL

CTRL-X or SHIFT-DEL

CTRL-X or SHIFT-DEL

Copy to Clipboard

CTRL-C or CTRL-INS

CTRL-C or CTRL-INS

CTRL-C or CTRL-INS

Paste from Clipboard

CTRL-V or SHIFT-INS

CTRL-V or SHIFT-INS

CTRL-V or SHIFT-INS

CTRL-J

Bookmarks

Clipboard

24.2

Code Completion TestComplete will automatically display the code completion dialog by default. If you accidentally close Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Cheat Sheet

273

this dialog (or you have turned Autocompletion), the code completion dialog can be invoked by press "CTRL-SPACE"

For method known by TestComplete, you can find out what parameters are needed by the method by pressing "CTRL-SHIFT-SPACE" inside the parentheses.

24.3

Keyboard Handling in Recorder TestComplete will record all keys entered to the active control while recording except for any keys that are in the Global Shortcuts. Global Shortcuts (keys that work when TestComplete is running even if TestComplete does not have focus)

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

274

24.4

TestComplete Made Easy

Command

Default Key

Pause script execution

SHIFT-10

Fix Information

SHIFT-CTRL-A

Record

SHIFT-F1

Stop

SHIFT-F2

Run

SHIFT-F3

Pause recording

SHIFT-F11

Load Testing Record

SHIFT-F6

Low Level Record

SHIFT-F4

Global Shortcuts/Changing Keyboard Emulation To access and change the Global Shortcuts: · Select "Tools | Options" from the main menu · Select "General | Global Shortcuts" from the Options dialog.

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Cheat Sheet

275

· Select the Action · Type in the new keyboard shortcut (note: if it is already in use, you will need to clear the one using it first). To access and change the keyboard emulation: · Select "Tools | Customize Keyboard..." from the main menu. · Choose the keyboard emulation that you want. (You can also set keyboard shortcuts for any command in this dialog).

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

276

TestComplete Made Easy

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Part

XXV Professional Offering

278

25

TestComplete Made Easy

Professional Offering

and Services You can get your questions answered by emailing [email protected] or by posting a message on the AutomatedQA message boards www.automatedqa.com/forums. Visit www.automatedqa.com/ for all your options.

Services AutomatedQA’s worldwide network of partners can provide your organization with training and services to help you ramp up more quickly or help with your existing automated testing projects. Go to www.automatedqa.com/partners to find a partner that fits your needs.

TestComplete Training and Services from Falafel Software The authors of this book are from Falafel Software, AutomatedQA’s premier services partner. Falafel has a wide range of services ranging from TestComplete training and consulting to large-scale custom enterprise application development. The professionals from Falafel Software are great to work with and we hear nothing but effusive praise about them from our customers. Here’s a description of some of their TestComplete related services: TestComplete Training from Falafel Software Onsite Training: A highly knowledgeable Falafel Software trainer will come to you and provide your team with an enlightening 3-5 day class. This is the best way to ramp up quickly. Online Training: For companies that have team in multiple locations or in situations where onsite training is not feasible, online training is a great option. Training Summit: If your team only has a few individuals in need of training, this open-enrollment option is the most cost effective solution. TestComplete Consulting from Falafel Software On a deadline? Need assistance from the Pros? Let Falafel provide you with world-class consulting for all your TestComplete needs. Falafel’s consultants have been working with TestComplete since the very beginning and are the highest qualified individuals to assist you. TestCompleteTV.com from Falafel Software TestComplete TV from Falafel Software provides an abundance of training videos that let you to learn at

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Professional Offering

279

your own pace in an innovative environment. This is an inexpensive subscription solution the guys at Falafel Software know you will love. Check out TestCompleteTV.com for more information. For more info on Falafel Software, go to www.falafel.com or call 1-888-GOT-FALAFEL (1-888-468-3252).

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

280

TestComplete Made Easy

Index -..NET

11, 43

-332 bit

11

-664 bit

Code Completion 46, 272 Code Explorer 31, 266 Code Options 48 Code Templates 48 Complex types 204 Condition 50 Configuration 12 Connections 227 Consulting 278 Continuous Integration 24, 26 Cookie Handling 224 Copy Script to Editor 34 U 33 CSVDriver 147 Customize 29

11

-AActivate 123 ActiveFocus 129 Add Text To Script 115 ADO 164 ADODriver 147 AJAX 185 Aliases 89 Analysis 230 AppendFolder 72 Application 23 AQDevTeam 17 AQTime 17 Automated Build Studio 17 AutomatedQA 11, 17

-BBDE 166 Black Box 42 Bookmarks 47 Borland 166 Breakpoints 50 Build 23

-CCall Stack 51 Checkpoint 129, 133, 136

-DDDT 147 Debugging 50, 51, 52, 53 Delay 123 DHTML 185 Distributed Testing 23, 253 DOM 176 DUnit 91

-EEditor 46, 47 Email 73 Eric Holton 17 Evaluate 53 ExcelDriver 147 Extended Information

72

-FFile Comparison 133 Files 133 Find 183 Finder tool 36 Firewall Settings 222 Functional Testing 23

-GGeneral Events

154

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Index

Global Variables Gutter 48

52

Maunal Test Events 107 Maunal Testing 23 Menus 29 Mouse events 123 MSTest 91

-HHighlight Object 86 Highlight on Screen 36 Hosts 251 HTTP Load Test 253 HTTP Load Testing 222, 224, 228, 239 HTTP Performance Testing 23 HTTP Traffic 232 Hybrid 176

-IInterbase

Object Browser 33 Object Comparison 136 Object Name Mapping 88 Object Properties 34 Objects 136 OnBeforeStep 107 OnLogError 156 OS 33

11 252 91

-K-

-P-

Keyboard 270, 273, 274 Keyboard events 123

-LLoad Testing 23, 222 Local Variables 52 Locals 52 LockEvents 74 Log Tree 72 Low Level Procedure 120 Low Level Procedure Collection

Named Mappings 77, 86, 88, 89 Naming convention 177 NativeWebObject 183 Network Suites 249 Notepad 36 NUnit 91, 92

-O-

166

-JJava Jobs JUnit

-N-

120

-MManual Steps 100 Manual Test 107 Map to Object 77 Mapping Dialog 88 Maunal Test 99, 100 Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Parameter Completion 46, 272 Count 50 Pausing 117 Playback 113 Plug-ins 67 PopLogFolder 72 Process Filter 34 Professional Offering 278 Profile 68 Project Anatomy 59 Project Explorer 31 Project Item 31, 59 Project Items 67 Project Structure 59 Project Suite 31 Project Template 62 Project Wizard 59 Project Worksapce 31 Proxy Settings 222

281

282

TestComplete Made Easy

-QQA

23

-RR&D 23 RAM 33 Recording 113, 116, 224 Recording Toolbar 114 Reflection 43 Region Comparison 129 Regions 129 Regression Testing 23 Remote Agent 239, 241 Remote Agent Port 241 Remote Agent Proxy 241 Requests 227, 232 Requirements 12 Responses 227, 232 Result Logs 31, 230 Run As 68 Run Mode 68

-SScalability Testing 222 Screen Coordinates 120 script Log 72 Service mode 239 SetFocus 123 Shortcuts 270, 273, 274 ShowModal 264 Smoke Test 26 Sort 34 Source Code Control 24 SQL Server 164 SQL Server 2005 164 Stations 224, 243 Stopping 117 Stress Testing 222 SynchPoints 253

Tasks 224, 243, 252 TCUnitTest 91 Test Items 266 Test Log 230 Test Logs 73 TestComplete 11, 17 TestedApps 68 TestExecute 17 TestRecorder 17 Tests 224 Toolbar 29 Training 278 Tree 176

-UUnexpected Windows 157 Unit Testing 23, 91, 95 Forms 262, 264

-VVirtual s

228

-WWatch List 53 Web Accessibility Checkpoint 180 Web Comparison Checkpoint 177 Web Page 268 Web Page Model 176 Web Services Options 209 Web Services Testing 199, 204, 211 Web Services Testing Dialogs 209 Web Testing 185 WebServices Checkpoint 204 White Box 42 White Box Application 43 Window Coordinates 120 Windows 11 WinformsObject 43 WndCaption 36 Workspace 31 WSDL 199

-TTag

176 Copyright © 2008 AutomatedQA Corp. - 1.0 Release

Index

-XXAML 11 XML Checkpoint

211

Copyright © 2008 AutomatedQA Corp. - 1.0 Release

283

Copyright (c) 2008 - AutomatedQA Corp.