TestArchitect™ Frequently Asked Questions

1. What is TestArchitect?

2. What is Action Based Testing?

3.  Is TestArchitect a replacement for my current test automation tool?

4.  Does TestArchitect support data-driven test automation?

5.  I'm already doing test automation. Why should I use keyword-driven test automation?

6.  Is TestArchitect only used for test automation?

7.  For what types of applications can TestArchitect be used to test?

8.  What skills are necessary to use TestArchitect?

9.  How does an organization get started using TestArchitect?

10.  Is there training available for learning how to use TestArchitect?

11.  Are there implementation services available for TestArchitect?

12.  What are the system requirements for TestArchitect?


1.   What is TestArchitect?

TestArchitect is a versatile and effective test development and test automation framework that enables teams to improve quality through better test coverage, while reducing time-to-market and reducing costs.   Based on the Action Based Testing™ methodology, TestArchitect allows organizations to routinely achieve 95% or more highly automation coverage, while other tools commonly result in 25% or less.

With TestArchitect, everyone on the test team can focus on what they do best with a new level of effectiveness:

  • Test engineers and business analysts design executable tests composed of reusable actions
  • Automation engineers use their programming skills to automate and maintain individual actions, rather than entire tests, resulting in far better maintainability and scalability
  • Managers and test leads stay in control with customizable reporting and version control

2.  What is Action Based Testing?

Action Based Testing is a proven methodology for software testing and test automation that has been successful in many industries around the world. Hans Buwalda, CTO of LogiGear Corporation, first presented the concept of keyword-driven test automation frameworks to the public in 1996. Action Based Testing saves time and money in test design, test automation and test management. It is a framework for the transformation of your entire testing organization.

3.  Is TestArchitect a replacement for my current test automation tool?

This depends on your needs. TestArchitect is designed to well blend in with and complement your current 3rd-party and in-house test automation solution. However, it can also serve as replacement, partially or in full, since it includes cutting edge automation support for virtually all of today's most popular platforms, and effective test-management capabilities.

4.  Does TestArchitect support data-driven test automation?

Yes. Apart from the action keyword driven test development that forms the core of TestArchitect, you have the ability to define "data sets" and apply your keyword tests to them, in which case the columns in the data set will form the values in your test. You can choose to repeat a test for all rows in the data set, or you can use filters to select them, either predefined as part of the data set, or in place when you apply it to a test.

5.  I'm already doing test automation. Why should I use keyword-driven test automation?

To improve the effectiveness of your scripts. Your scripts can be mapped to action keywords to perform well-defined singular operations, like log into your system. These action keywords can then be re-used numerous times across your tests. If changes in the interface or behavior your system under test make it necessary, in most cases it will suffice to maintain the individual keyword scripts, after which all your tests will run again.

The keywords also allows for an easier specialization in your team. The testers can focus on developing creative and effective tests, without having to worry about details of their execution, since those are "hidden" by the keywords. On the other hand the automation engineer can concentrate on the automation challenges, often dealing with complex problems like the timing or operations towards your system under test.

6.  Is TestArchitect only used for test automation?

No. In fact the keyword method is most of all a standard for test development. For most of the action keywords, it is transparent whether they are actually automated and how. There have been various projects where the execution of action based tests were performed manually.

7.  For what types of applications can TestArchitect be used to test?

TestArchitect is suitable for any kind of testing that involves software. It has been used to successfully test applications built on Windows, Java, Unix, mainframes, the Web, mobile devices, embedded software, graphical software, multi-media, and more.

8.  What skills are necessary to use TestArchitect?

Test engineers and business analysts can use TestArchitect to create tests, without a need for technical automation knowledge. Even though such test development is not technical, the tests are still fully automation-ready, since are written with action keywords. 

Using built-in action components either included in the program or added by your organization's automation engineers, most keywords in any test can actually be assembled in so-called "action definitions", with little or no programming. Any new coding that is required for new actions can be worked on in parallel by the automation engineers, improving delivery speed for everyone on the team.

9.  How does an organization get started using TestArchitect?

This depends very much on the available skill-sets in the teams. TestArchitect itself is a straightforward application, that after an initial brief period of installation and training will not be difficult to use. Many organizations, even those with advanced skills available in their teams, will choose to use additional training and coaching programs to get used to the keyword model, and to learn how to effectively use it to develop effective and manageable test ware. Such relatively small initial efforts have proven to yield a profound long-term benefit in effectiveness and efficiency.

Also a common option is to use our inexpensive off-shore services to quickly re-use  and/or develop a sizable automated test collection, while your own team can retain ownership. Since our teams are specialized and have extensive experience, they can off-load the initial bulk-efforts and set you up with a manageable situation right off the bat. 

10.  Is there training available for learning how to use TestArchitect?

Yes. LogiGear offers training courses in basic and advanced automation theory and practice, including Action Based Testing. LogiGear can also create customized training courses and corporate certification tracks based on your unique needs.

11.  Are there implementation services available for TestArchitect?

Yes. LogiGear offers Action Based Testing™ solutions, providing everything from high-level test automation strategy and framework design, to test development and automation engineering services.

12.  What are the system requirements for TestArchitect?

TestArchitect Client Requirements

  • Microsoft® Windows® XP, Vista or 7
  • also available is a Linux version that will work in most distributions.

TestArchitect Server Requirements

  • Microsoft® Windows® XP, Vista, 7, Server 2003, Server 2008, Linux


Contact Us today to discuss Our Unique Solutions for Your Unique Needs.


 
Back Top