Software Testing World
/

           Quality Software by Quality Testers

 

Glossary

These definitions based on the best practices of Software Testing of the community of Software Testing World.

Every day we will be adding more. You can send your suggestions at vocabulary@softwaretestingworld.com 

Ad  Hoc Testing

Known also as Monkey Testing, the testing is performed without following test cases, randomly the user test the functionalities of the system, the test cases could be positives or negatives.

Agile Testing

Agile Testing is the process of validating the software with agile methodologies, with developers, customers, product owner, scrum master, less documentation for testing. The validation of the software is gradually and then a regression testing is performed for all the iterations done before.

Assertion

Validate that an specific object or string has been shown or is present on the system application.

API

Known as Application Program Interface, an API is used to transport information between system applications. One system could be doing request using the API to get, update, delete, create information from another Application.

Atomic Test Case

It is when a test case is designed to validate an specific single rule from the requirement specification while other test cases validate several rules.

Automated Testing

Process to execute a Regression Testing but through the use of Automation Tools or Automation Frameworks.

Beta Testing

Is the process where the software is released to be tested just for the customer.

Black Box Technique

It is a technique when we are doing our testing we don't take care about what path or flow our data takes into the software code, we just take care about the inputs and outputs. This technique is commonly done by Testing Team. There are different techniques as Decision Table, Equivalence Partitioning, Boundary value Analysis, cause-effect graph, Error guessing, State transition, use case, all-pairs, mental maps, user stories among others.

Bug

A deffect or commonly know as a Bug in Software Testing may be a discrepancy between functionality and specification, or error presented during the Test Project, and also some discrepancies you may find in the specifications before the Test begin.

Compatibility Testing

This is the process to validate that the components of the system works and can operate over different plataforms, browsers, devices, hardware.

Data Driven Framework

Data driven is the way you can separate data from your test scripts,parameterizing this data,  managed from different sources as xml, csv, xls, JSON files or taken from databases.

Dinamic Testing

It is the validation of the software, called also Test Execution.

Estimation Effort

Estimation Effort is to prepare a budget for the Testing project, it could have information as man hours primarily and/or total cost per activity. The estimation effort needs to be detailed in order you can say what is every cent or hour for. You can estimate the effort for your Test Plan construction, Test Analysis, Test Design, Smoke Test, Test Execution, Test Certification construction, Test Management, Data Preparation among others.

Gray Box

Technique

This technique is commonly used when your testing validation needs to do some  validations in the database, for example in the front of the application you register a record, you go to the database and validate that the record is inserted according the test performed in the front.

Static Testing

Static Testing is the validation without executing the program.

Test Case

Test Case is a set of inputs and pre conditions that are delivered in to the system application with the intention of finding defects, the result will be outputs and post conditions.

Test Cycle

Is the number of times that our test is planned to be executed. For a best practice you normallly we do estimation effort for three test cycles one for Stabilization Test Cycle, other for Regression Test Cycle and the last one for Acceptance Test Cycle.

Test Case Design

Test Case Design, is to write Test Cases related to our Test Requirement, remember we need to design positive and negative test cases, Happy Path, Alternative Path, Exceptional Path, our test cases need to be pointing to validate what the system needs to do and what not needs to do.

Test Environment

Test Environment is the place where the test will be conducted, normally there would be several environments where the software passes Development, QA, Preproduction, Production. Consider that QA environment should have closely the same features as real life, production environment. 

Test Matrix

Is a set of Test Cases which may be grouped specific functionalities, type of Test, Team to validate or others.

Test Plan

It is a document where is placed all the information related to our Test Project. It will tell us how we are going to do our Software Testing, placing Test Objective, Test Strategy, Test Team, Test Gantt, What to test, where the test is going to be done, tools, risk management, acceptance criterials among others.

Test Procedure

It was called also test script, the test procedure is the structure to follow the execution of test steps in order to validate an specific feature or functionality of the system. The test procedure can have several test cases associated, in other words several different data can be executed using the same test procedure getting different results.

Test Scenario

Is a validation of one functionality of the system, an scenario could have several test cases.

Test Script

Test script is a set of test steps created to be executed automatically by an automation framework or automation test tool.

Test Set

It is a group of Test Cases selected to be executed for an specific purpose.

Test Strategy

The Test Strategy is a document that place all the information about what is in the scope in our Test Project, what we are going to test, what kind of tests we are going to do, and what we are not going to test and why. Also you can prepare a brief description about how the test need to be executed.

Quality Assurance

It is the Testing area responsible for create, mantain, imrpove and update all the processes and methodology according the newest best practices and standards of Testing.

Quality Control

It is the area of testing which is responsible for doing the activity of testing using the processes and methodologies implemented by quality assurance team.

Unit Testing

Unit testing is the process where the Dev team perform testing to the code generated.

Usability Testing

Usability Testing is the process to do ad hoc testing through the system application but with the intention of validating the system usability is easy to use and understandable for the user

Use Case

Document where is specified the flow of the functionality of the system with end user perspective. The use case contains besides the functionalities flow, its happy path, alternative paths, exceptional paths, profiles, priority for the business among others. 

User Acceptance Testing

User Acceptance Testing is the phase of the Testing Process where the user is involved to execute an specific test set designed for the user. Here the QA Team just provide access and data to the user.

Validation

We validate our software has been built correctly.

Verification

We verify that our software is being built correctly.

Volume Testing

Volume Testing is part of the none functional testing activities, this particular kind of test is focused to validate that the system is prepared to manage huge volume of data and can process it, the process is inserting the information to the system and releasing all of it, and validate that ths system still working correctly.

White box Technique

It is the process of validate the software but in different conditions, we take care about the path that our data takes when goes into the software. This activity is mainly done by developers. There are several kind of white box techniques which have different ways to validate our code as Statement coverage, branch coverage, path coverage y data flow.