Test Methods and Strategies Glossary

Test Strategy

A test strategy describes how the test effort will reach the quality goals set out by the development team.

Sometimes called the test approach, test strategy includes, among other things, the testing objective, methods and techniques of testing and the testing environment.

Test strategies describe how the product risks of the stakeholders are mitigated at the test-level and which types of test are to be performed. The strategy can be documented on its own or is more commonly included as part of a test plan. Test strategies layout plans for how much manual and automated testing will happen at what phases and using which methods, such as unit testing, code review, UI validation, API testing, regression testing, etc.

A Test Plan is…

A document describing the scope, approach or strategy, resources, and schedule of intended testing activities. It defines test items, the features to be tested, the testing tasks, who will do each task, and any risks requiring contingency planning.

The ANSI/IEEE Standard 829 for Software Test Documentation.

Test Design is…

Thinking about what you are testing and examining the product you are about to develop. It is the process of analyzing test requirements and arriving at test objectives and then test cases. It starts with an analysis of what areas will be tested then later, how they will be tested.

Test design could require all or one of:

  • Knowledge of the software, and the business area it operates on.
  • Knowledge of the functionality being tested.
  • Knowledge of testing techniques and heuristics.

Test Methods

Test methods are structures, ideas, or approaches to how you will design the test cases to execute the test strategy. Test methods may be determined by standards, regulatory agencies, or contractual agreements. They may be dependent on available documentation- or lack of documentation. Test methods often go hand-in-hand with the test strategy as how you will design and execute the test cases.

Black Box Testing — The technique of testing without having any knowledge of the interior workings of the application. The tester is oblivious to the system architecture and does not have access to the source code. Typically, when performing a black box test, a tester will interact with the system’s user interface by providing inputs and examining outputs without knowing how and where the inputs are worked upon.

White Box Testing — The detailed investigation of internal logic and structure of the code. White box testing is also called glass testing or clear box testing. In order to perform white box testing on an ap-plication, the programmer or tester needs to possess detailed knowledge of the internal working of the code.

Grey Box Testing — A technique to test the application with limited knowledge of the internal workings of an application, system, or platform. In software testing, the term the more you know the better carries a lot of weight when testing an application.

Coverage

Test coverage is a measurement of the extent of testing based on some criteria. Common measurements are code coverage, platform coverage, requirements coverage, user story coverage, form coverage, data coverage. There are many ways to measure coverage and report back to the team on testing progress and confidence.

Sources: Wikipedia, Tutorials Point

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

“Happy About Global Software Test Automation: A Discussion of Software Testing for Executives” Author: Hung Q. Nguyen, Michael Hackett, and Brent K. Whitlock Publisher: Happy About (August 1, 2006) Finally, a testing book for executives!, November 17, 2006 By Scott Barber “Chief Technologist, PerfTestPlus” Happy About Global Software Test Automation: A Discussion of Software Testing ...
An automation framework is a way to organize your code in meaningful manner so that any person who is working with you can understand what each file contains. Automation frameworks differ based on how you organize your code – it can be organized based on your data, so that any person who wants to use ...
Many organizations rely on HP Quality Center to design test plans and track test results. TestArchitect’s Quality Center integration makes working with QC as easy as pie. TestArchitect (TA) is a three-in-one tool for Test Management, Test Development, and Test Automation. Users can create and manage test assets, execute tests, track and analyze test results, ...
The 12 Do’s and Don’ts of Test Automation When I started my career as a Software Tester a decade ago, Test Automation was viewed with some skepticism.
Based in Alberta, Canada, Jonathan Kohl takes time out of his busy schedule to discuss his views on software testing and automation.
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. ...
The path to continuous delivery leads through automation Software testing and verification needs a careful and diligent process of impersonating an end user, trying various usages and input scenarios, comparing and asserting expected behaviours. Directly, the words “careful and diligent” invoke the idea of letting a computer program do the job. Automating certain programmable aspects ...
Regardless of your current state of tools, building an effective Continuous Integration suite of significant automated regression tests is the key to moving to a higher level of confidence in today’s development world. In the evolution timeline of software development tools, new tools have recently proliferated. We have all been sold on collaboration, transparency and ...
September Issue 2018: The Secrets to Better Test Automation  
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 ...
This article was developed from concepts in the book Global Software Test Automation: Discussion of Software Testing for Executives. Introduction There are many potential pitfalls to Manual Software Testing, including: Manual Testing is slow and costly. Manual tests do not scale well. Manual Testing is not consistent or repeatable. Lack of training. Testing is difficult ...
Automated Testing is a huge part of DevOps, but without human-performed quality assurance testing, you’re increasing the risk of  lower-quality software making it into production.  Automated Testing is an essential DevOps practice to increase organizations’ release cadence and code quality. But there are definitely limits to only using Automated Testing. Without human quality assurance (QA) ...

Leave a Reply

Your email address will not be published.

Stay in the loop with the lastest
software testing news

Subscribe