1/44
Comprehensive practice flashcards defining core vocabulary, processes, test design techniques, levels, and web testing methodologies across all four lecture modules.
Software Testing
The process consisting of all life cycle 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, demonstrate that they are fit for purpose, and detect defects.
Software Testing Cost Impact
Testing activities typically contribute to 30%−50% of total software development cost.
Defect Clustering
The principle of testing stating that testing effort shall be focused proportionally to the expected and the observed defect density of modules.
Absence-of-Errors Fallacy
The principle of testing stating that a system without failures does not imply that the system will meet the users' expectations.
Exhaustive Testing
The testing principle recognizing that complete or exhaustive testing is not feasible except for trivial, non-complex programs.
Early Testing
The principle stating that testing is not a phase in software development that happens only at the end, but must be started as early as possible in the lifecycle.
Test Policy
A high-level document describing the principles, approach, and major objectives of the organization regarding testing.
Test Strategy
A high-level description of the test levels to be performed and the testing within those levels for an organization or program.
Test Control
An ongoing test management task that deals with developing and applying a set of corrective actions to get a test project on track when monitoring shows a deviation from what was planned.
Test Analysis and Design
The testing process activity where general testing objectives are transformed into tangible test conditions, test designs, and test procedures (scripts).
Evaluating Exit Criteria
The activity where test execution is assessed against defined objectives by checking test logs against criteria specified in test planning to determine whether more tests are needed or exit criteria should be modified.
Test Closure Activities
The activity where data from completed test activities are collected to consolidate experience, archive testware, ensure incident reports are resolved, hand over testware to maintenance, and analyze lessons learned.

The V-Model
A lifecycle framework mapping construction phases to corresponding test levels: Requirements Definition corresponds to Acceptance Testing, Functional System Design to System Testing, Technical System Design to Integration Testing, and Component Specification to Component Testing.
Prerequisite (Testing)
A condition or requirement (such as environment, browser, or application state) that must be available and satisfy minimal requirements prior to starting test case execution.
Test Condition
An item or event that could be verified by a test, establishing 'what' can be tested.
Test Case
A set of tests performed in a sequence and related to a test objective, determining 'how' the 'what' is tested and comprising specific input values, expected outcomes, and execution prerequisites.
Test Script
Data and/or instructions with a formal syntax used by a test execution automation tool, typically held in a file, to implement one or more test cases, navigation, set-up, or verification.
Test Procedure
A manual test script that outlines the step-by-step actions for a tester to execute a test manually.

Test Development Activities
The five core sequential development activities for any test case: identify test conditions, design test cases, build test cases, execute test cases, and compare test case outcomes to expected outcomes.

Software Test Document (Test Plan)
A document describing the objectives, approach, resources, and schedule of planned test activities.
Comparing versus Verifying
Comparing checks whether actual outcomes match expected outcomes (a task tools can perform), whereas verifying determines whether the outcomes are in fact correct (which requires a human tester).
Component Testing
The process of testing individual software components (subprograms, modules, or procedures) as they are written to discover discrepancies between their interface specifications and actual behavior.

Level of Design Abstraction (CSCI to CSU)
A hierarchical system decomposition where a Computer Software Configuration Item (CSCI) decomposes into Computer Software Components (CSCs) in high-level design, and further decomposes into Computer Software Units (CSUs) in low-level design.
Stub
A dummy subprogram that replaces modules subordinate to or called by the module under test, simulating their behavior and returning predefined values to the caller.
Driver
A 'main program' procedure that initializes input data, calls the module to be tested, controls information used by stubs, and prints or evaluates execution results.
Functional Testing (Black-Box Testing)
A testing approach that demonstrates software functions are operational, inputs are accepted, and outputs are correctly produced without using knowledge of the program's internal structure.
Equivalence Partitioning
A black-box technique that divides input data into valid and invalid classes, where a test on any single value within a class is considered equivalent to testing any other value in that same class.
Boundary Value Analysis
A black-box testing technique that refines equivalence partitioning by selecting test cases that exercise the extreme outer boundaries of input and output equivalence classes.

Cause-Effect Graphing
A formal black-box specification technique where natural language requirements are translated into a digital combinatorial logic network connecting causes (input conditions) to effects (actions), which is then mapped into a decision table to derive test cases.
Robustness Testing
Testing designed to prove that no catastrophic event can be produced when abnormal input data or values outside operational boundaries are introduced.
Structural Testing (White-Box Testing)
A testing approach that examines the internal structure of a component to exercise independent logical paths, decisions on true/false sides, loop boundaries, and internal data structures.
Cyclomatic Complexity (V(G))
A metric that provides the minimum number of independent paths through a control/flow graph, calculated as V(G)=NbArcs−NbNodes+2=Predicates+1=Regions+1.
Instruction Block (IB)
A set of sequential instructions in which the execution of the first instruction invariably leads directly to the execution of all subsequent instructions in the block.
Decision-to-Decision Path (DDP)
A path that begins at the start of a program or at a decision node (branching point) and ends at the next decision node or the end of the program.
Integration Testing
An intermediate phase between unit testing and system testing that tests modules in executable combination to verify interfaces between modules and interfaces between the integrated assembly and its environment.
Static Verification (Web Testing)
The scanning of HTML web pages without execution to detect structural faults, navigation anomalies, unreachable pages (pages that cannot be reached from the initial page), and ghost pages (links pointing to non-existent pages).
Dynamic Validation (Web Testing)
White-box web testing that evaluates coverage criteria such as page testing (visiting every page at least once) and hyperlink testing (traversing every hyperlink from every page) by requesting sequences of URLs.
Navigation Semantic Unit (NSU)
A pathway defined by a set of navigation paths connecting navigation nodes (web pages, content objects, or functionality) that allows a user from a defined user category to achieve a specific use-case requirement.
Syntactic Navigation Testing
Testing the syntax and operational mechanisms of navigation items, including navigation links, redirects, bookmarks, frames and framesets, site maps, and internal search engines.
Proxy Server
Software whose purpose is to act as the sole intermediary connection between a private network and the internet, caching data to improve performance and controlling files entering or leaving the network.
Scalability (Web Applications)
The capacity of a web application to sustain an increasing number of concurrent users and/or transactions while maintaining sufficient response times.
Load Testing
A performance testing method that models real-world user experience by generating large numbers of simultaneous users or requests to evaluate system behavior under expected normal and peak volumes.
Stress Testing
A performance testing method that subjects a web system to varying and maximum loads, or sustains operation near known memory and processor limits, to evaluate resulting performance and stability.
End-to-End Transaction Testing
Testing that follows the entire workflow of a user visit from beginning to end across all underlying architectural components, including browsers, web servers, application servers, databases, and middleware.
Rollback Plan
A contingency strategy in post-implementation testing that outlines a clean procedure to revert the production environment to its original state if a deployment fails, followed by acceptance test verification.