TestKIT Conference Site

Nick Olivo, SmartBear

Upon starting to create automated tests many test automators realize, to their dismay, that some of the objects within the application aren't as easy to work with as expected; buttons on ribbons aren't easily recognized, there is difficulty in figuring out how to detect tree nodes, or controls embedded within a grid. The solution to this is to tap into the native properties and methods of your application, and this session will show you how. Additionally, this talk will touch on automating certain actions outside your GUI, such as how to verify your application has sent an email, how to verify that files from an installer were laid down properly, and more. The techniques taught in this session can be incorporated into any automation framework, be it commercial or open source. JScript and Python will be used in the session, but the concepts can be translated to any language.

Anand Ramdeo, Testing Geek

Tools can provide invaluable insight, help teams become more effective and increase collaboration among developers, testers and product owners. This presentation will follow the day-to-day routine of a fast paced development team during an Agile sprint and showcase the kinds of tools used during sprint planning, story kick-off, development, testing, demo and sign-off. The tools discussed will range from high level tools such as mindmap to low level check-style and coverage tools.

Tom Wimsatt, Sotera Defense Solutions, Inc.

Dharma Ganesan, Fraunhofer CESE

In recent years, several software test case execution frameworks (e.g., JUnit, CppUnit, Selenium, etc.) have been developed and used in many organizations. Such frameworks are very helpful to automatically run the test cases during nightly builds. They also help the programmers verify their source code modifications (a.k.a. regression testing). However, the job of designing the test cases is outside the scope of these test execution frameworks. Programmers (or testers) have to construct test cases manually. To overcome this limitation, model-based testing (MBT), which is a technique that derives test cases from an explicit behavioral model, has been proposed. In this presentation, we will present our experiences and lessons learned of applying an advanced MBT tool, called Spec Explorer, for automatically generating and executing innumerable number of test cases for NASA’s GMSEC API, which implements a software bus in different programming languages and also support different middleware technologies. We will explain how we were able to generate tests for several languages using one common model, and detected previously unknown behavioral errors and several requirements-level issues such as contradictions and incompleteness.

Dion Johnson, Automated Testing Institute

Dion Johnson, Automated Testing Institute