You are here
Testing Terms: T
- Test
- A set of one or more test cases.
- Test approach
- A testing view methodology on how to implement, types of testing approach are: White-Box testing, Black testing, Gray testing, and Visual testing
- Test automation
- The use of software to perform or support test activities, e.g. test management, test design, test execution and results checking.
- Test basis
- All documents from which the requirements of a component or system can be inferred. The documentation on which the test cases are based. If a document can be amended only by way of formal amendment procedure, then the test basis is called a frozen test basis.
- Test Case
- A set of input values, execution preconditions, expected results and execution postconditions, developed for a particular objective or test condition, such as to exercise a particular program path or to verify compliance with a specific requirement.
- Test condition
- An item or event of a component or system that could be verified by one or more test cases, e.g. a function, transaction, feature, quality attribute, or structural element.
- Test data
- Data that exists (for example, in a database) before a test is executed, and that affects or is affected by the component or system under test.
- Test Data Generator
- Test Data Generator is any tool which creates random and/or large quantities data for testing purposes.
- TDD
- Test Driven Development, is a software development process that relies on the repetition of a very short development cycle: first the developer writes a failing automated test case that defines a desired improvement or new function, then produces code to pass that test and finally refractors the new code to acceptable standards.
- Test effort
- A measure of the expenses, current and future for tests, with relation to failure costs.
- Test environment
- An environment containing hardware, instrumentation, simulators, software tools, and other support elements needed to conduct a test.
- Test estimation
- The calculated approximation of a result related to various aspects of testing (e.g. effort spent, completion date, costs involved, number of test cases, etc.) which is usable even if input data may be incomplete, uncertain, or noisy.
- Test execution
- The process of running a test on the component or system under test, producing actual result(s).
- Test execution automation
- The use of software, e.g. capture/playback tools, to control the execution of tests, the comparison of actual results to expected results, the setting up of test preconditions, and other test control and reporting functions.
- Test infrastructure
- A set of tools and capabilities that can be used to build the automatic test case required
- Test management
- The planning, estimating, monitoring and control of test activities, typically carried out by a test manager.
- Test method
- A definitive procedure that produces a test result.
- Testing method
- A testing approach, which is directed to challenge the SUT on a specific way of use or influence by specific system behavior, like: Regression testing, functional testing, Agile testing, etc.
- Testing objective
- A testing strategy that was design to meet a specific type of SUT and environment, like: Web testing, Gui testing, SOA testing, etc.
- Test Plan
- A document describing the scope, approach, resources and schedule of intended test activities. It identifies amongst others test items, the features to be tested, the testing tasks, who will do each task, degree of tester independence, the test environment, the test design techniques and entry and exit criteria to be used, and the rationale for their choice, and any risks requiring contingency planning. It is a record of the test planning process.
- Test process
- The fundamental test process comprises test planning and control, test analysis and design, test implementation and execution, evaluating exit criteria and reporting, and test closure activities.
- Test strategy
- The design and implementation of testing strategy for a specific project. It typically includes the decisions made that follow based on the (test) project’s goal and the risk assessment carried out, starting points regarding the test process, the test design techniques to be applied, exit criteria and test types to be performed.
- Test Suite
- A set of several test cases for a component or system under test, where the post condition of one test is often used as the precondition for the next one.
- Tester
- A skilled professional who is involved in the testing of a component or system.
- Testing
- The process consisting of all lifecycle activities, both static and dynamic, concerned with planning, preparation and evaluation of software products and related work products to determine that they satisfy specified requirements, to demonstrate that they are fit for purpose and to detect defects.
- Testware
- Artifacts produced during the test process required to plan, design, and execute tests, such as documentation, scripts, inputs, expected results, set-up and clear-up procedures, files, databases, environment, and any additional software or utilities used in testing.
- TMAP
- A Test management approach, a testing methodology, which combines insights on how to test and what to manage, as well as techniques for the individual test consultant.
- TTCN-3 (Testing and Test Control Notation version 3)
- A strongly typed test scripting language used in conformance testing of communicating systems and a specification of test infrastructure interfaces that glue abstract test scripts with concrete communication environments.
- Type testing
- some call it Conformance testing is testing strategy that determine whether a product or system meets some specified standard that has been developed for efficiency or interoperability.
| Logo | Title | Type |
|---|---|---|
| Test Automation Framework | Testing Tool Article | |
| The Crucial Need for Quality Assurance Testing in the Software Industry | Testing Tool Article | |
| The Open Source Definition | Testing Tool Article | |
| Top 4 Challenges for Test Data Management and How QA Outsourcing Can Help | Testing Tool Article | |
| Top 4 Reasons Why Load Testing is a MUST for Businesses | Testing Tool Article | |
| Top Challenges Of Crowdsourced Testing | Testing Tool Article | |
| Top Trends In Artificial Intelligence 2018 | Testing Tool Article | |
| Transformation is the Differentiator for ETL | Testing Tool Article | |
| Types of Security Threats to an E-commerce Company | Testing Tool Article | |
 |
T3 | Testing Tool |
 |
TAZ | Testing Tool |
 |
Tellurium (aost) | Testing Tool |
 |
Tessy | Testing Tool |
 |
Test Analytics | Testing Tool |
 |
Test Automation Framework for Embedded Systems | Testing Tool |
 |
TestBench | Testing Tool |
 |
TestDrive | Testing Tool |
 |
TestDrive-Assist | Testing Tool |
 |
TestingBot | Testing Tool |
 |
Testlink | Testing Tool |
Pages
- Log in to post comments
Theme by Danetsoft and Danang Probo Sayekti