Systems | Development | Analytics | API | Testing

This session is about a TestComplete test lab. It gives an overview of how we built our environment and how we manage it in the TestComplete QA Team. It would be of special interest for anyone in the process of creating/updating your test lab or you are simply curious about our way of doing things.

This video explains the new mode of working with Web Objects in TestComplete. This mode is based on using the Selenium framework. Today, this framework is widely used in web testing and that’s why the transition to TestComplete will be smooth and easy. The new mode is the combination of the two powerful products - TestComplete and Selenium.

In its early inception Collaborator was known as Code Collaborator, with the focus of offering a platform for peer review of code files. Parts of that first moniker are still present in the current version of Collaborator: In the name of the executables for example, in case one wonders why there’s the extra ‘c’ at the beginning of those file names. Dropping the ‘Code’ piece of the name, Collaborator evolved into a much more expansive peer review tool, moving beyond just code files, to include document review for many types of files, and with the latest integration, Simulink model files.

Jennifer talks about her work at SmartBear and various tasks that the Marketing team performs. She also deep-dives into UI testing trends and shares her thoughts on why TestComplete is such a successful tool.

Integrations are a key component to Collaborator’s peer review functionality and workflow. With options to connect to more than a dozen source control management (SCM) systems, and other tools such as Atlassian’s Jira and Mathworks Simulink®, Collaborator is an easy fit into almost any tool string, allowing teams to peer review code, user stories, test plans, and other artifact types in a transparent, collaborative framework.