Study your flashcards anywhere!

Download the official Cram app for free >

  • Shuffle
    Toggle On
    Toggle Off
  • Alphabetize
    Toggle On
    Toggle Off
  • Front First
    Toggle On
    Toggle Off
  • Both Sides
    Toggle On
    Toggle Off
  • Read
    Toggle On
    Toggle Off

How to study your flashcards.

Right/Left arrow keys: Navigate between flashcards.right arrow keyleft arrow key

Up/Down arrow keys: Flip the card between the front and back.down keyup key

H key: Show hint (3rd side).h key

A key: Read text to speech.a key


Play button


Play button




Click to flip

23 Cards in this Set

  • Front
  • Back
Ad Hoc Testing
A testing phase where the tester tries to 'break' the system by randomly trying the systems functionality. Can include negative testing as well. See also Monkey Testing.
Black Box Testing
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.
Breadth Testing
A test suite that exercises the full functionality of a product but does not test features in detail.
Component Testing
See Unit Testing.
Dynamic Testing
Testing software through executing it. See also Static Testing.
End-to-End testing
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.
Exhaustive Testing
Testing which covers all combinations of input values and preconditions for an element of the software under test.
Functional Testing
Testing the features and operational behavior of a product to ensure they correspond to its specifications. May be Black Box or White Box testing.
Gray Box Testing
A combination of Black Box and White Box testing methodologies: testing a piece of software against its specification but using some knowledge of its internal workings.
Integration Testing
Testing of combined parts of an application to determine if they function together correctly. Usually performed after unit and functional testing. This type of testing is especially relevant to client/server and distributed systems.
Monkey Testing
Testing a system or an Application on the fly, i.e just few tests here and there to ensure the system or an application does not crash out.
Negative Testing
Testing aimed at showing software does not work. Also known as "test to fail". See also Positive Testing.
Performance Testing
Testing conducted to evaluate the compliance of a system or component with specified performance requirements. Often this is performed using an automated test tool to simulate large number of users. Also know as "Load Testing".
Positive Testing
Testing aimed at showing software works. Also known as "test to pass". See also Negative Testing
Regression Testing
Retesting a previously tested program following modification to ensure that faults have not been introduced or uncovered as a result of the changes made.
Sanity Testing
Brief test of major functional elements of a piece of software to determine if its basically operational. See also Smoke Testing.
Stress Testing
Testing conducted to evaluate a system or component at or beyond the limits of its specified requirements. Often this is performance testing using a very high level of simulated load.
Static Testing
Testing software without executing it.
System Testing
Testing that attempts to discover defects that are properties of the entire system rather than of its individual components.
Usability Testing
Testing the ease with which users can learn and use a product.
Unit Testing
Testing of individual software components.
White Box Testing
Testing based on an analysis of internal workings of a piece of software.
Workflow Testing
Scripted end-to-end testing which duplicates specific workflows which are expected to be utilized by the end-user.