Test Tool and Automation Glossary

Utility: A program that performs a specific task related to the management of computer functions, resources, or files, as password protection, memory management, virus protection, and file compression.

Tool: A program or application that software development teams use to create, debug, maintain, or otherwise support other programs and applications. The term usually refers to programs that can be combined together to accomplish a task, much as one might use multiple hand tools to fix a physical object. The ability to use a variety of tools productively is one hallmark of a skilled software engineer.

Automation Engineer: A discipline within systems engineering that focuses on how to design and manage complex engineering projects over their life cycles. Issues such as reliability, logistics, coordination of different teams (requirements management), evaluation measurements, and other disciplines become more difficult when dealing with large or complex projects.

Coach: A coach is a person with special skills, knowledge or competency who works with individuals to improve their skills or performance. As opposed to just providing instruction, a coach works along-side, or with, an individual or small group to assist them in learning.

Jump Start: Slang for energizing a start-up process so that momentum can be created faster. It was adopted from the actual meaning of temporarily connecting a fully charged battery to drained battery in order to start a combustion engine.

Test Harness: A test harnesses is a collection of software and test data configured to test a program by running it under varying conditions. The test harness is a hook to the developed code which can be tested using an automation framework.

Shelfware: A slang term used to describe owning or licensing software that you don’t actually need or use (e.g. it sits on a shelf). Shelfware is a phrase that is commonly used in the enterprise and corporations where volume license prices are given and the corporation purchases more software than really needed to obtain that discount.

Test Automation Framework: A test automation framework is an integrated system that sets the rules of automation of a specific product. This system integrates the function libraries, test data sources, object details and various reusable modules. These components act as small building blocks which need to be assembled to represent a business process. The framework provides the basis of test automation and simplifies the automation effort.

Application Lifecycle Management (ALM): ALM is the product lifecycle management (governance, development, and maintenance) of application software. It encompasses the requirements management, software architecture, computer programming, software testing, software maintenance, change management, project management and release management.

Integrated Development Environment (IDE): An IDE is a software application that provides comprehensive facilities to computer programmers for software development. An IDE normally consists of a source code editor, build automation tools and a debugger. It can also include test tools.

Continuous Integration (CI): CI is the practice of merging all developer working copies with a shared mainline several times a day.

Testability: The effort required to test a product to ensure that it performs its intended function.

Design for Testability: The architectural and design decisions in order to enable us to easily and effectively test a system.

This includes traditional software development terms such as Controllability, Observability and Test Point Insertion. But also designing a low maintenance UI, and includes low level design ideas such as using as many standard controls as possible and as few custom controls as possible. The awareness of “design for testability” and the effort toward this type design will have a big benefit for testing and a huge benefit for lower maintenance test automation.

High Volume Automation: A test automation program not for a small set of tests, but for a large set of tests, devices, platforms or data. More thought must be used in architecting a larger system with better test design, lower maintenance, better defect analysis, easier data management, more visibility into what is actually being tested and better reporting. Small scale automation is, in many cases, no longer worth the effort. While high volume automation presents much greater value, it needs to be more carefully built.

LogiGear Corporation

LogiGear Corporation provides global solutions for software testing, and offers public and corporate software-testing training programs worldwide through LogiGear University. LogiGear is a leader in the integration of test automation, offshore resources and US project management for fast and cost-effective results. Since 1994, LogiGear has worked with hundreds of companies from the Fortune 500 to early-stage startups, creating unique solutions to exactly meet their needs. With facilities in the US and Vietnam, LogiGear helps companies double their test coverage and improve software quality while reducing testing time and cutting costs.

For more information, contact Joe Hughes + 01 650.572.1400

LogiGear Corporation
LogiGear Corporation provides global solutions for software testing, and offers public and corporate software testing training programs worldwide through LogiGear University. LogiGear is a leader in the integration of test automation, offshore resources and US project management for fast, cost-effective results. Since 1994, LogiGear has worked with Fortune 500 companies to early-stage start-ups in, creating unique solutions to meet their clients’ needs. With facilities in the US and Viet Nam, LogiGear helps companies double their test coverage and improve software quality while reducing testing time and cutting costs.

The Related Post

Two dominant manual testing approaches to the software testing game are scripted and exploratory testing. In the test automation space, we have other approaches. I look at three main contexts for test automation: 1. Code context – e.g. unit testing. 2. System context – e.g. protocol or message level testing. 3. Social context – e.g. ...
LogiGear Magazine – The Big Testing Issue – April 2012
Are you frustrated with vendors of test automation tools that do not tell you the whole story about what it takes to automate testing? Are you tired of trying to implement test automation without breaking the bank and without overloading yourself with work? I experienced first-hand why people find test automation difficult, and I developed ...
“Testing Applications on the web” – 2nd EditionAuthors: Hung Q. Nguyen, Bob Johnson, Michael HackettPublisher: Wiley; edition (May 16, 2003) This is good book. If you test web apps, you should buy it!, April 20, 2001By Dr. Cem Kaner – Director of Florida Institute of Technology’s Center for Software Testing Education & Research Book Reviews ...
When automated tests are well-organized and written with the necessary detail, they can be very efficient and maintainable. But designing automated tests that deal with data can be challenging if you have a lot of data combinations. For example, let’s say we want to simulate a series of 20 customers, along with the number of ...
June Issue 2019: Testing the Software Car
It can be complicated to automate model-based testing. Here’s how to employ action words to get the job done.
LogiGear Magazine – March 2011 – The Agile Test Automation Issue
I got some comments on my post “Test Everything all the Time” — most notably people commenting that it’s impossible to test “everything”. I can’t agree more. The intention of the post was to make the point that we need to be able to test “everything we can” all the time. That is, you should ...
5 roadblocks in vehicular autonomy that complicate Software Testing Experts in the field have previously referred to air travel as somewhat of a gold standard for autonomous vehicle safety, but after Boeing’s two tragedies, that analogy can no longer be used when talking about self-driving cars. This was after Boeing’s 737 MAX Jets have found ...
Framework: An abstraction in which software providing generic functionality can be selectively changed by additional user written code, thus providing application specific software. A software framework is a universal, reusable software platform used to develop applications, products and solutions. Harness: A collection of software and test data configured to test a program unit by running it under varying conditions and monitoring ...
Source: From I.M.Testy (BJ Rollison’s blog) I just finished reading Implementing Automated Software Testing by E.Dustin, T. Garrett, and B. Gauf and overall this is a good read providing some well thought out arguments for beginning an automation project, and provides strategic perspectives to manage a test automation project. The first chapter made several excellent ...

Leave a Reply

Your email address will not be published. Required fields are marked *

Stay in the loop with the lastest
software testing news

Subscribe