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

There is no one recipe to make big testing a big success. It takes planning and careful execution of the various aspects, like test design, infrastructure and organization – a mix that can be different for each situation in which you may find yourself. In writing about big testing, the first question that comes up ...
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 ...
Learn how to leverage TestArchitect and Selenium for turnkey, Automated Web testing. TestArchitect lets you create, manage, and run web-based automated tests on different types of browsers—using either a WebDriver or non-WebDriver technique. In this article, we will explore employing WebDriver for testing a web-based application with TestArchitect. TestArchitect with WebDriver is a tool for automating ...
We’re excited to share with you the latest and greatest features of TestArchitect Gondola, as well as how to use them. So, check them out below! Gondola Studio UI/UX ImprovementsGondola Studio’s new Test Execution Dialog makes it easy to configure and run your test. You can choose the browser or device you’d like to run ...
In order to make the right choices among tools, you must be able to classify them. Otherwise, any choice would be at best haphazard. Without functioning classification, you would not be able to understand new tools fast, nor come up with ideas of using, or creating new tools.
Test automation can provide great benefits to the software testing process and improve the quality of the results…. but its use must be justified and its methods effective. The reasons to automate software testing lie in the pitfalls of manual software testing… As we all know too well, the average manual software testing program:
Introduction Many executives have some very basic questions about Software Testing. These questions address the elements of quality (customer satisfaction) and money (spending the least amount of money to prevent future loss). The basic questions that executive have about Software Testing include: Why care about and spend money on testing? Why should testing be treated ...
LogiGear Magazine September Test Automation Issue 2017
Introduction A characteristic of data warehouse (DW) development is the frequent release of high-quality data for user feedback and acceptance. At the end of each iteration of DW ETLs (Extract-Transform-Load), data tables are expected to be of sufficient quality for the next ETL phase. This objective requires a unique approach to quality assurance methods and ...
Introduction A common issue that I come across in projects is the relationship between test automation and programming. In this article I want to highlight some of the differences that I feel exist between the two.
In recent years, much attention has been paid to setting up Test Automation frameworks which are effective, easy to maintain, and allow the whole testing team to contribute to the testing effort. In doing so, we often leave out one of the most critical considerations of Test Automation: What do we do when the Test ...
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 ...

Leave a Reply

Your email address will not be published.

Stay in the loop with the lastest
software testing news

Subscribe