-
Outsourced Software Testing Services | Software Test Automation | Software Development Services | Software QA Training | Software Quality Assurance Consulting | Downloads | About Us | Contact Us
#
LogiGear
search: Search
>>
>> Test Automation
>> TestArchitect™
>>
Features and Benefits
FAQ
Datasheet
Whitepaper
Case Study
Business Case
>> Global Test Automation
>> Action Based Testing™
>> Client Testimonials
>> Books
>> Security
>> White papers
>> Newsletter archives
>> RSS feed
>> QA City: Resources

Frequently Asked Questions (FAQ)

For more information:
Contact Us

TestArchitect™ Frequently Asked Questions

What is TestArchitect?

What is Action Based Testing?

Is TestArchitect a replacement for my current test automation tool?

Does TestArchitect support data-driven test automation?

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

Is TestArchitect only used for test automation?

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

What skills are necessary to use TestArchitect?

How does an organization get started using TestArchitect?

Is there training available for learning how to use TestArchitect?

Are there implementation services available for TestArchitect?

What are the system requirements for TestArchitect?


What is TestArchitect?

TestArchitect is a powerful test automation framework that allows 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 achieve 80 - 95% test automation, while other tools only result in 20-25% test automation

With TestArchitect, everyone on the test team can focus on what they do best, and work in parallel 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.

What is Action Based Testing?

Action Based Testing is the 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 1994.  Action Based Testing saves time and money in test design, test automation and test management, and is a framework for the transformation of your entire testing organization.

Is TestArchitect a replacement for my current test automation tool?

TestArchitect is designed to complementwith your current 3rd party or homegrown test automation tools, or can server as a replacement, since it includes built-in support for today's most popular platforms

Does TestArchitect support data-driven test automation?

Data driven testing is powerfully supported by TestArchitect's spreadsheet-focused interface and database architecture. TestArchitect goes far beyond data-driven testing with the Action Based Testing keyword framework.

To use project management "work breakdown structure" as an analogy, the data-driven approach breaks down automation work into two parts: script and data. Action Based Testing breaks down the work even further, with scripts, tests and data each broken out into small, separately maintainable building blocks. This results in a much more advanced, structured and elegant approach.

Separating script and data with the data-driven approach allows testers to make changes to data without help from automation engineers, and of course makes the data component far more scalable. In Action Based Testing, external data is simply one aspect of the approach, and in fact is far better supported within the keyword framework. The result is improved control and effectiveness over all aspects of testing, including data.

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

Traditional test automation techniques provide a significant improvement over manual testing, but require tests to be created by test automation engineers with programming skills for all but the most simple of applications. Test designers traditionally document their test cases in a word processing application, and then pass these documents to automation engineers who code automation scripts.

Using the traditional test automation approach can introduce a number of problems into the testing effort:

  • Hundreds or thousands of test cases means hundreds or thousands of test scripts, which must be maintained, at a significant cost, each time the application under test (AUT) is modified.
  • In order to keep tests from becoming outdated, test scripts and test documents must be updated, increasing the burden on the testing team.
  • Automated tests must be maintained by automation engineers, who are skilled programmers
  • Scripts created through record and playback are notoriously unstable and often end up being abandoned

With Action Based Testing:

  • Each team member can focus on what they do best. Test designers can focus on using their product and testing knowledge to create effective tests, while automation engineers can focus on using their technical skills to implement the actions needed in the tests.
  • The amount of code needed to create test automation is significantly reduced, easing the burden of future maintenance. A typical project will have tens to hundreds of keywords, or "actions", and hundreds to thousands of test cases. Actions can be reused and reordered as needed to create new test cases. Only actions are created as scripts, and TestArchitect already contains many low-level actions built-in.

In TestArchitect, test cases are organized in a spreadsheet format. Each spreadsheet is both an executable test and documentation. This further reduces the maintenance required whenever the application is updated.

Is TestArchitect only used for test automation?

TestArchitect provides a powerful framework for improving manual and well as automated testing, and is the focus for implementing Action Based Testing throughout your organization.

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

TestArchitect can be used on almost any type of application. It has been used to successfully test applications built on Windows, Java, Unix, mainframes, the Web, devices and more.

What skills are necessary to use TestArchitect?

Test engineers and business analysts can use TestArchitect, without any knowledge of coding scripts, to create executable tests. Using their test design skills and product knowledge, they create test tests which are defined as a series of action keywords.

Using built-in action components included in the program or added by your organization's automation engineers, most steps in any test can be developed with 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.

How does an organization get started using TestArchitect?

A TestArchitect license includes installation, setup and initial training. If your key people have an understanding of keyword-driven testing you should be good-to-go. Many organizations choose to participate in the Action Based Testing "ABT Jumpstart" program, which is a 1-2 week program of consulting, implementation, and informal training sessions. In ABT Jumpstart, LogiGear's experienced consultants will work onsite with your staff to lay the groundwork for your test automation effort. At the end of the program, your entire team will be familiar with using TestArchitect and the Action Based Testing method to design and automate tests.

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.

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.

What are the system requirements for TestArchitect?

TestArchitect Client Requirements

  • Microsoft© Windows 98,ME,2000, or XP
  • Microsoft Excel 2000, XP or 2003

TestArchitect Server Requirements

  • Microsoft Windows 2000, XP Professional, or Server 2003

TestArchitect Database Requirements

  • Microsoft SQL Server 7.0 or 2000 with latest service pack
    or
    Microsoft Access 2000, XP, or 2003

Contact us today to learn how LogiGear can help your company meet your software quality goals!


Download the white paper 'Achieving the Full Potential of Test Automation'

-      
newsletter | RSS | site map |
-

1 (800) 322-0333   © 2009 LogiGear Corporation. All rights reserved.   Legal Notice.   Privacy Policy.