quality - Concepts

Explore concepts tagged with "quality"

Total concepts: 22

Concepts

Dummy Object - A test double passed around to fill parameter lists but never actually used, serving only to satisfy method signatures or constructor requirements.
E-E-A-T - Google's quality criteria: Experience, Expertise, Authoritativeness, and Trustworthiness.
Code Review - A quality assurance practice where one or more developers examine code written by a peer before it's merged into the codebase.
Unit Testing - A software testing practice where individual units of code are tested in isolation to verify they behave correctly and meet their specifications.
Acceptance Criteria - Specific conditions that must be met for a user story or feature to be considered complete and acceptable.
Definition of Done - A shared checklist of criteria that must be met for work to be considered complete.
Standard Operating Procedure - A documented set of step-by-step instructions for carrying out routine operations consistently and efficiently.
Slow Productivity - Cal Newport's philosophy of doing fewer things, working at a natural pace, and obsessing over quality rather than visible busyness.
Continuous Improvement - The ongoing effort to incrementally improve processes, products, and practices over time through small, consistent changes.
Six Sigma - A data-driven methodology for eliminating defects and reducing process variation to achieve near-perfect quality.
Integration Testing - A software testing practice where multiple components or modules are combined and tested together to verify they interact correctly as a group.
Test Double - A generic term for any object that replaces a production dependency during testing, including dummies, fakes, stubs, spies, and mocks.
Test Spy - A test double that records information about how it was called, allowing verification of interactions after the code under test has executed.
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.
Definition of Ready - Shared criteria that must be met before a work item can be started by a team.
Usability - The degree to which a product can be used by specified users to achieve specified goals with effectiveness, efficiency, and satisfaction.
Customer Satisfaction (CSAT) - A metric measuring how products or services meet or exceed customer expectations.
Test-Driven Development - A software development approach where tests are written before the code they validate, following a red-green-refactor cycle.
Mock Object - A test double pre-programmed with expectations about calls it should receive, used to verify interaction behavior between objects under test.
Test Stub - A test double that provides canned answers to calls made during a test, replacing real dependencies with predictable, pre-programmed responses.
Test Fake - A test double with a working but simplified implementation that takes shortcuts unsuitable for production, such as an in-memory database.
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.

← Back to all concepts