SDLC & STLC

BVA is similar to Equivalence Partitioning but focuses on "corner cases" or values that are usually out of range as defined by the specification. his means that if a function expects all values in range of negative 100 to positive 1000, test inputs would include negative 101 and positive 1001.

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.

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.

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

The set of tests derived using basis path testing.

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.

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

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

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

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 formalized set of software calls and routines that can be referenced by an application program in order to access supporting system or network services.

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

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

SDLC is Software Development Life Cycle.

STLC is Software Testing Life Cycle.

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.

 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.

Testing which covers all combinations of input values and preconditions for an element of the software under test.

A technique used during planning, analysis and design; creates a functional hierarchy for the software.

A portion of a component's input or output domains for which the component's behavior is assumed to be the same from the component's specification.

A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes.

 A test tool that records test input as it is sent to the software under test. The input cases stored can then be used to reproduce the test at a later time. Most commonly applied to GUI test tools.

The specification of tests that are conducted from the end-user perspective. Use cases tend to focus on operating software as an end-user would conduct their day-to-day activities.

Testing of individual software components.

Checks for memory leaks or other problems that may occur with prolonged execution.

Testing a complete application environment in a situation that mimics real-world use, such as interacting with a database, using network communications, or interacting with other hardware, applications, or systems if appropriate.

Testing in which all branches in the program source code are tested at least once.

A test suite that exercises the full functionality of a product but does not test features in detail.

Computer Aided Software Testing.