Software Testing

Software testing glossary

Short, plain definitions of the terms you'll meet in articles, job ads and interviews, with the Romanian equivalent of each.

A

Acceptance criteria (Romanian: criterii de acceptare)
The conditions a user story must meet to be accepted, written so they can be tested. For example: 'Orders of 200 lei or more get free shipping.' Read more →
Acceptance testing (Romanian: testare de acceptare)
Testing whether a system meets the needs of its users or customer, usually the last test level before release. When done by business users, it's often called UAT (user acceptance testing). Read more →
Accessibility testing (Romanian: testarea accesibilității)
Checking that people with disabilities can use the product, for example with a screen reader, keyboard only, or high zoom. Usually measured against the WCAG guidelines. Read more →
Agile (Romanian: Agile)
A way of building software in small increments with frequent feedback and adaptation, instead of one big release at the end. Scrum and Kanban are common Agile frameworks. Read more →
API (Romanian: API (interfață de programare))
Application Programming Interface: the set of requests a system accepts from other programs. In web apps, the screens call the server's API behind the scenes. Read more →
API testing (Romanian: testare API)
Testing a system by sending requests directly to its API and checking the responses, without the user interface. Faster and more precise than testing through screens. Read more →
Assertion (Romanian: aserțiune (verificare))
The part of an automated test that checks the result, for example 'expect the page to show Welcome, Ana'. A test without assertions checks nothing. Read more →

B

BDD (behaviour-driven development) (Romanian: BDD (dezvoltare ghidată de comportament))
A practice where the team describes behaviour with examples in a shared format, often Given–When–Then, which can also become automated tests. Read more →
Black-box testing (Romanian: testare black-box)
Designing tests from the specification (what the software should do) without looking at the code. Read more →
Boundary value analysis (Romanian: analiza valorilor-limită)
A test design technique that tests values at and just outside the edges of valid ranges, where bugs often cluster. For ages 18–65: test 17, 18, 65 and 66. Read more →
Branch coverage (Romanian: acoperirea ramurilor)
The percentage of decision outcomes (both the true and false side of each condition) executed by the tests. A white-box measure. Read more →
Bug life cycle (Romanian: ciclul de viață al unui bug)
The statuses a bug moves through, such as New, Assigned, In progress, Fixed, Ready for retest and Closed, plus Reopened, Rejected, Duplicate or Deferred. Read more →
Bug report (Romanian: raport de bug)
A written description of a defect with a clear title, steps to reproduce, expected and actual results, environment, severity and evidence. Read more →

C

Chaos engineering (Romanian: chaos engineering)
Deliberately injecting failures, such as stopping servers or adding network delay, in a controlled way to check that a system keeps working. Read more →
CI/CD (Romanian: CI/CD (integrare și livrare continuă))
Continuous integration and continuous delivery/deployment: automatically building, testing and releasing every code change through a pipeline. Read more →
Code coverage (Romanian: acoperirea codului)
A measure of how much of the code the tests execute, such as statement or branch coverage. It shows what is untested, not that tested code is correct. Read more →
Component testing (unit testing) (Romanian: testare de componentă (testare unitară))
Testing the smallest pieces of code, such as a function or class, in isolation. Usually written by developers and run automatically. Read more →
Contract testing (Romanian: testare de contract)
Checking that two services agree on the format of the messages they exchange, so each can be changed and released independently. Read more →
Crowdtesting (Romanian: crowdtesting)
Testing done by many independent testers on their own devices, organised through a platform, often paid per valid bug or test cycle.

D

Decision table testing (Romanian: testarea cu tabele de decizie)
A technique that lists combinations of conditions and the expected action for each, so every meaningful combination of business rules gets tested. Read more →
Defect (bug) (Romanian: defect (bug))
A flaw in code, a requirement or a design that can cause the system to behave incorrectly. Bug is the everyday word for it. Read more →
Definition of Done (Romanian: Definition of Done)
A team's shared checklist that every item must meet to count as done, for example: code reviewed, tests passing, tested on staging, no open major bugs. Read more →
DevTools (Romanian: DevTools (unelte pentru dezvoltatori))
Developer tools built into browsers (F12). Testers use them to see errors, network requests and responses, cookies and mobile layouts. Read more →
DNS (Romanian: DNS)
Domain Name System: the internet's directory that translates names like example.com into the IP addresses of servers. Read more →

E

End-to-end testing (Romanian: testare end-to-end)
Testing a complete user flow through all parts of the system, often through the UI, such as from search to payment confirmation. Read more →
Entry criteria (Romanian: criterii de intrare)
Conditions that must be met before a test activity starts, such as 'the test environment is ready and the smoke test passes'. Read more →
Equivalence partitioning (Romanian: partiționarea în clase de echivalență)
A technique that divides inputs into groups the system should treat the same way, then tests one value from each group. Read more →
Error (mistake) (Romanian: eroare (greșeală))
A human action that produces an incorrect result, such as misreading a requirement or typing the wrong condition. Errors create defects. Read more →
Exit criteria (Romanian: criterii de ieșire)
Measurable conditions that must be met to consider testing done, such as 'all high-risk tests run and no open critical bugs'. Read more →
Exploratory testing (Romanian: testare exploratorie)
Learning, designing and running tests at the same time, guided by a goal (charter) and a time box, adapting as you discover things. Read more →

F

Failure (Romanian: defecțiune (failure))
Visible incorrect behaviour of the system when it runs, caused by a defect, such as a wrong total or a crash. Read more →
Flaky test (Romanian: test instabil (flaky))
An automated test that sometimes passes and sometimes fails without any change to the code, often because of timing, shared data or unstable environments. Read more →
Functional testing (Romanian: testare funcțională)
Testing what the system does: its features and business rules, such as whether a discount is calculated correctly. Read more →

H

HTTP status code (Romanian: cod de status HTTP)
A three-digit code in every server response: 2xx success, 3xx redirect, 4xx client error (such as 404), 5xx server error (such as 500). Read more →

I

Integration testing (Romanian: testare de integrare)
Testing how components or systems work together, such as the app and its database, or two services exchanging data. Read more →
ISTQB (Romanian: ISTQB)
International Software Testing Qualifications Board: a non-profit that defines testing syllabi and certifications, such as the Foundation Level (CTFL).

J

Jira (Romanian: Jira)
A widely used tool for tracking work items such as stories, tasks and bugs through a workflow. Testers use it to log and follow bugs. Read more →
JQL (Romanian: JQL)
Jira Query Language: the search language for building filters in Jira, such as all open bugs reported by you. Read more →

L

Load testing (Romanian: testare de încărcare)
Performance testing under expected levels of use, such as 1,000 users at once, to check response times and stability. Read more →

M

Manual testing (Romanian: testare manuală)
Testing performed by a person using the software and judging the results, without automation scripts. Read more →
Mobile testing (Romanian: testare mobilă)
Testing apps on phones and tablets, including device and OS variety, interruptions, permissions, network conditions and app updates. Read more →
Mutation testing (Romanian: testare prin mutații)
Deliberately introducing small changes (mutants) into code to check whether the tests detect them. It measures how good the tests are. Read more →

N

Negative testing (Romanian: testare negativă)
Testing with invalid input or unexpected actions to check that the system handles them gracefully, with clear errors and no crashes or corrupted data.
Non-functional testing (Romanian: testare nefuncțională)
Testing how well the system works: performance, security, usability, accessibility, reliability and compatibility. Read more →

P

Pairwise testing (Romanian: testare pairwise)
A combinatorial technique that covers every pair of parameter values with far fewer tests than all combinations. Read more →
Performance testing (Romanian: testare de performanță)
Testing speed, responsiveness and stability under load. Includes load, stress, spike and endurance testing. Read more →
Playwright (Romanian: Playwright)
A free, open-source tool for automating web browsers, widely used for end-to-end UI tests. Read more →
Postman (Romanian: Postman)
A popular tool for sending API requests, inspecting responses and writing automated API checks. Read more →
Priority (Romanian: prioritate)
How urgently a bug should be fixed. A business decision, usually made by the product owner or during triage. Read more →
Production (Romanian: producție)
The live environment with real users and real data. Testing there is limited and must be planned carefully. Read more →

Q

QA (quality assurance) (Romanian: QA (asigurarea calității))
Activities that ensure quality by improving processes and preventing defects. Testing is part of QA; in job ads the terms are used interchangeably. Read more →

R

Regression testing (Romanian: testare de regresie)
Re-testing existing functionality after a change to check that nothing that used to work has broken. Read more →
Requirement (Romanian: cerință)
A statement of what the system must do or how well it must do it. Good requirements are clear, complete, consistent and testable. Read more →
Retesting (confirmation testing) (Romanian: retestare (testare de confirmare))
Running the tests that found a defect again, after the fix, to confirm the defect is gone. Read more →
Risk-based testing (Romanian: testare bazată pe risc)
Deciding what to test, how deeply and in what order based on the likelihood and impact of failures. Read more →

S

Sanity testing (Romanian: testare sanity)
A quick, narrow check that a specific fix or change works as expected, before deeper testing. Read more →
Scrum (Romanian: Scrum)
An Agile framework where a team works in short sprints, with a Product Owner, a Scrum Master and Developers, and events such as planning, daily stand-up, review and retrospective. Read more →
SDLC (Romanian: SDLC (ciclul de viață al dezvoltării software))
Software development life cycle: the stages of building software, from idea and requirements to design, coding, testing, release and maintenance. Read more →
Security testing (Romanian: testare de securitate)
Testing that a system protects data and functions from unauthorised access or misuse, such as one user seeing another's data. Read more →
Severity (Romanian: severitate)
How much impact a defect has on the system or its users, from critical (data loss, no workaround) to trivial (cosmetic). Read more →
Shift left (Romanian: shift left)
Moving testing activities earlier in development, such as reviewing requirements and testing small pieces as soon as they exist. Read more →
Smoke testing (Romanian: testare smoke)
A quick, broad check that a new build's most important functions work, so it's worth testing further. Read more →
Sprint (Romanian: sprint)
A fixed period, usually two weeks, in which a Scrum team delivers a working, tested increment. Read more →
SQL (Romanian: SQL)
Structured Query Language: the language for reading and changing data in relational databases. Testers use it to check and prepare test data. Read more →
Staging (Romanian: staging)
An environment that closely copies production, used for final testing before a release. Read more →
State transition testing (Romanian: testarea tranzițiilor de stare)
A technique that tests how a system moves between states, such as an order going from created to paid to shipped, including invalid transitions. Read more →
Statement coverage (Romanian: acoperirea instrucțiunilor)
The percentage of code statements executed by the tests. A basic white-box measure. Read more →
Static testing (Romanian: testare statică)
Examining work products such as requirements, designs or code without running them, for example through reviews. Read more →
STLC (Romanian: STLC (ciclul de viață al testării))
Software testing life cycle: the phases of testing, from requirement analysis and planning to design, environment setup, execution and closure. Read more →
System testing (Romanian: testare de sistem)
Testing the complete, integrated system against its requirements, as a whole. Read more →

T

Test automation (Romanian: automatizarea testelor)
Using code and tools to run tests and check results automatically, typically for repetitive checks such as regression. Read more →
Test case (Romanian: caz de test)
A set of preconditions, steps, data and expected results that checks one specific behaviour of the system. Read more →
Test charter (Romanian: charter de testare)
A short goal for an exploratory testing session, such as 'Explore checkout with discount codes to find calculation errors'. Read more →
Test data (Romanian: date de test)
The data needed to run tests: accounts, products, orders and so on. Good test data is realistic, varied and never real customers' personal data. Read more →
Test environment (Romanian: mediu de testare)
A complete running copy of the system used for testing: application, database, configuration and connected services. Read more →
Test oracle (Romanian: oracol de test)
The source used to decide whether a test result is correct, such as a requirement, a previous version or a calculation done another way. Read more →
Test plan (Romanian: plan de testare)
A document describing how a project or release will be tested: scope, approach, resources, schedule, risks and criteria. Read more →
Test pyramid (Romanian: piramida testelor)
A model for balancing automated tests: many fast unit tests, fewer integration/API tests and few slow UI tests. Read more →
Test strategy (Romanian: strategie de testare)
The general approach to testing across an organisation or product: what kinds of testing, at which levels, with which tools and standards. Read more →
Traceability matrix (Romanian: matrice de trasabilitate)
A table linking requirements to the tests that cover them, and to results and bugs. It shows coverage gaps and what to retest after a change. Read more →
Triage (Romanian: triaj)
Reviewing new bugs to confirm them, set priority and assign them, usually in a regular meeting. Read more →

U

Usability testing (Romanian: testare de utilizabilitate)
Checking how easily real users can understand and use the product, often by watching them complete tasks. Read more →
Use case testing (Romanian: testare pe cazuri de utilizare)
Designing tests from complete user interactions with the system, including the main flow, alternatives and error cases. Read more →
User story (Romanian: user story)
A short description of a feature from the user's point of view: 'As a [user], I want [goal], so that [benefit]', with acceptance criteria. Read more →

V

Validation (Romanian: validare)
Checking that the product meets the users' real needs: 'Are we building the right product?' Read more →
Verification (Romanian: verificare)
Checking that the product matches its specification: 'Are we building the product right?' Read more →

W

White-box testing (Romanian: testare white-box)
Designing tests from the internal structure of the code, such as its conditions and branches, and measuring coverage. Read more →