Key terms in E2E testing, test automation, agent-based QA, and compliance.
A flaky test produces inconsistent results when the relevant code and expected behavior have not changed. Causes can include timing, shared state, infrastructure and external dependencies.
Read more →End-to-end testing verifies a complete user journey through an application. A browser E2E test performs user actions and asserts an outcome visible through the web app.
Read more →A self-healing test can recover a target after a UI change while preserving the original interaction and expected outcome. The category describes target maintenance, not permission to change the requirement.
Read more →Test flakiness describes inconsistent results that do not correspond to a relevant change in the behavior under test. A flake rate is meaningful only when its measurement method is defined.
Read more →Selector brittleness is the tendency of an element locator to fail after a UI implementation change even when the intended user behavior remains the same.
Read more →Visual testing compares rendered appearance with an expected visual state. Depending on the tool, that may mean screenshot comparison, layout rules or human review.
Read more →Test maintenance is the work of keeping test data, setup, actions and assertions aligned with the application’s intended behavior.
Read more →Pull-request gating prevents a change from merging until required conditions, such as a successful CI workflow, are met.
Read more →Diff-aware testing selects or proposes tests using information about a code change. It can use file mappings, dependency analysis or other signals; the exact mechanism depends on the tool.
Read more →Agentic testing uses an AI agent to interpret a test objective and make decisions while interacting with an application. Scope varies: some tools draft tests, some execute them, and some propose exploratory tasks.
Read more →A QA agent is software that tests a running application the way a person would. It reads a plain-English step, looks at the live page, chooses an action, performs it in a real browser and checks the outcome, recording evidence for every step. It performs testing work; it does not own quality.
Read more →Test automation uses software to execute defined tests and report observed results. Automated tests can target individual functions, service interactions or full user journeys.
Read more →AI testing can mean testing an AI system or using AI to help test software. In browser automation, it commonly describes AI-assisted authoring, target resolution or semantic assertions.
Read more →No-code testing lets someone define tests without writing a conventional test program. It can use a visual editor, recorded actions or natural-language descriptions.
Read more →Test coverage describes what a set of tests exercises. Code coverage measures executed code; behavioral coverage asks which user outcomes and edge cases have been tested.
Read more →CI/CD testing runs automated tests as part of integrating and delivering software changes. Different stages can execute different tests against suitable environments.
Read more →Regression testing reruns tests to look for unintended changes in previously expected behavior after the application changes.
Read more →Smoke testing runs a small set of high-value tests to determine whether the application is usable enough for further testing or release review.
Read more →Compliance-related testing is testing selected to support an organization’s own control and review requirements. A software test result alone does not certify compliance.
Read more →Shift-left testing means checking assumptions and behavior earlier in development, when changing an implementation is usually easier than after release.
Read more →Continuous testing runs relevant tests throughout the delivery process so changes receive repeated feedback. The schedule and scope should match the team’s release decisions.
Read more →Test orchestration coordinates which tests run, where they run, their required setup and how results affect a delivery process.
Read more →Cross-browser testing verifies an application in more than one browser engine or browser environment to identify compatibility differences.
Read more →Test data management prepares and maintains the accounts, records and application state a test needs to run predictably.
Read more →Codeless test automation expresses a test through an interface other than a conventional programming language, such as editable actions or natural-language steps.
Read more →A test automation framework provides conventions and tools for defining tests, preparing setup, executing assertions and reporting results.
Read more →Autonomous testing is a broad term for systems that perform testing work with limited intervention. Vendors use it for different levels of planning, authoring, execution and maintenance.
Read more →Test automation maintenance keeps automated tests useful as requirements, interfaces, environments and dependencies evolve.
Read more →The testing pyramid is a model for balancing many focused lower-level tests with fewer broad end-to-end tests. It emphasizes placing checks at a useful level rather than forcing every assertion through the UI.
Read more →Functional testing verifies whether a system behaves according to a specified requirement, such as saving a setting or returning the expected search result.
Read more →Test automation metrics describe the usefulness and operating cost of a test suite. Examples include feedback time, investigation effort, meaningful coverage and inconsistent results.
Read more →