QA Testing

The use of software tools, such as automated testing tools, to improve software quality.

The set of tests derived using basis path testing.

Verifying a product is accessible to the people having disabilities (deaf, blind, mentally disabled etc.).

A testing phase where the tester tries to 'break' the system by randomly trying the system's functionality. Can include negative testing as well. See also Monkey Testing.

Testing practice for projects using agile methodologies, treating development as the customer of testing and emphasizing a test-first design paradigm. See also Test Driven Development.

A specification defining requirements for portability of applications in binary forms across different system platforms and environments.

A formalized set of software calls and routines that can be referenced by an application program in order to access supporting system or network services.

Testing conducted to enable a user/customer to determine whether to accept a software product. Normally performed to validate the software meets a set of agreed acceptance criteria.

Testing employing software tools which execute tests without manual intervention. Can be applied in GUI, performance, API, etc. testing. The use of software to control the execution of tests, the comparison of actual outcomes to predicted outcomes, the setting up of test preconditions, and other test control and test reporting functions.

A metalanguage used to formally describe the syntax of a language.

A sequence of one or more consecutive, executable statements containing no branches.

A white box test case design technique that uses the algorithmic flow of the program to design tests.

The point at which some deliverable produced during the software engineering process is put under formal change control.

Testing of a rerelease of a software product conducted by customers.

What would you like to do five years from now?

Testing an executable application for portability across system platforms and environments, usually for conformation to an ABI specification.

Testing based on an analysis of the specification of a piece of software without reference to its internal workings. The goal is to test how well the component conforms to the published requirements for the component.

Test which focus on the boundary or limit conditions of the software being tested. (Some of these tests are stress tests).

An approach to integration testing where the lowest level components are tested first, then used to facilitate the testing of higher level components. The process is repeated until the component at the top of the hierarchy is tested.

If software misses some feature or function from what is there in requirement it is called as defect.