testing - Concepts

Explore concepts tagged with "testing"

Total concepts: 32

Concepts

Summative Assessment - Evaluation at the end of a learning period to measure what has been learned.
Dummy Object - A test double passed around to fill parameter lists but never actually used, serving only to satisfy method signatures or constructor requirements.
Determinism - The principle that given the same inputs and initial conditions, a system or process will always produce the same outputs.
Test Fake - A test double with a working but simplified implementation that takes shortcuts unsuitable for production, such as an in-memory database.
Penetration Testing - Authorized simulated attacks on systems to identify security vulnerabilities before malicious actors do.
Chaos Engineering - The discipline of experimenting on distributed systems to build confidence in their ability to withstand turbulent conditions.
Given-When-Then - A structured format for writing acceptance criteria and test scenarios that specifies context, action, and expected outcome in plain language.
Unit Testing - A software testing practice where individual units of code are tested in isolation to verify they behave correctly and meet their specifications.
User Acceptance Testing - The final phase of testing where actual users or stakeholders verify that a system meets their requirements and is ready for deployment.
Red Teaming - An adversarial testing practice where a dedicated team attempts to find vulnerabilities, flaws, or failure modes in a system by simulating attacks or misuse scenarios.
Specification by Example - A collaborative approach to defining software requirements using concrete examples that serve as both living documentation and automated tests.
Continuous Integration - A software development practice where developers frequently merge code changes into a shared repository, with each integration automatically verified by building and testing.
Test-Driven Development - A software development approach where tests are written before the code they validate, following a red-green-refactor cycle.
Prototyping - Creating preliminary versions of products or ideas to test concepts and gather feedback.
Guerrilla Usability Testing - Steve Krug's low-budget, do-it-yourself approach to usability testing: a few users, once a month, on whatever you've got — valuing frequency and simplicity over scientific rigor.
Data Masking - Hiding sensitive data by replacing it with realistic but fictional values while preserving data format and usability
Architectural Fitness Functions - Automated tests and metrics that objectively assess how well a software architecture meets its intended quality goals, enabling continuous architectural governance.
AI Skill Testing - Validating AI skill correctness, reliability, and performance before deployment through structured evaluation and automated test suites.
Test Stub - A test double that provides canned answers to calls made during a test, replacing real dependencies with predictable, pre-programmed responses.
Integration Testing - A software testing practice where multiple components or modules are combined and tested together to verify they interact correctly as a group.
Shift Left - The practice of moving testing, quality checks, and security measures earlier in the software development lifecycle to catch issues sooner.
Behavior-Driven Development - A software development methodology that extends TDD by writing tests as human-readable specifications describing expected behavior from the user's perspective.
Mock Object - A test double pre-programmed with expectations about calls it should receive, used to verify interaction behavior between objects under test.
Legacy Code - Inherited code that is difficult to change safely due to lack of tests, documentation, or understanding.
Extreme Programming - An agile software development methodology that emphasizes technical excellence, continuous feedback, and close customer collaboration through practices taken to their logical extremes.
Screenshot Driven Development - A development approach using visual screenshots as specifications and documentation for UI development.
Test Double - A generic term for any object that replaces a production dependency during testing, including dummies, fakes, stubs, spies, and mocks.
Vulnerability Assessment - The systematic process of identifying, quantifying, and prioritizing security weaknesses in systems.
Code Coverage - A metric that measures the percentage of source code executed during automated testing.
Test Spy - A test double that records information about how it was called, allowing verification of interactions after the code under test has executed.
Pure Functions - Functions that always return the same output for the same input and produce no side effects.
Acceptance Criteria - Specific conditions that must be met for a user story or feature to be considered complete and acceptable.

← Back to all concepts