API testing
Learn HTTP, request checks, and negative testing scenarios.
QA HUB / Software testing knowledge base
Software testing
knowledge base
API, test design, Web, Mobile, automation, and QA Engineering.
- Articles in English
- 154
- Topics to explore
- 12
Recently updated
All topics and articles01 / Getting started
How to Use This Knowledge Base
A short guide to QA Hub: choosing a learning path, getting practical value from articles, and avoiding theory overload.
02 / Getting startedGetting Started in QA
A practical roadmap for your first 3–6 months in QA: what to learn, in which order, and how to recognize a working foundation.
03 / Getting startedGrowing as a Mid-Level QA Engineer
What distinguishes mid-level QA from junior QA and which topics advance your career beyond adding to a list of completed courses.
Materials
154 availableFound: 154
How to Use This Knowledge Base
A short guide to QA Hub: choosing a learning path, getting practical value from articles, and avoiding theory overload.
Getting Started in QA
A practical roadmap for your first 3–6 months in QA: what to learn, in which order, and how to recognize a working foundation.
Growing as a Mid-Level QA Engineer
What distinguishes mid-level QA from junior QA and which topics advance your career beyond adding to a list of completed courses.
Growing into a Senior QA or QA Lead Role
A path toward Senior and Lead roles: the skills that make QA a quality strategist rather than simply the most experienced individual contributor.
Getting into Test Automation
A realistic path into automation: foundations before your first framework, a sensible learning sequence, and useful first projects.
Getting into AI QA
Starting in AI QA: what to know before testing an LLM product, how AI risks differ from conventional applications, and how to build a sound test strategy.
What Is Software Testing?
A precise, practical explanation of testing: why it matters, what QA work includes, and why "finding bugs" is too narrow a definition.
QA vs. QC vs. Testing
How QA, QC, and testing differ and why companies often use these terms interchangeably.
Testing Objectives and Principles
The main testing objectives and seven principles that support sound QA decisions without dogmatism.
Verification and Validation
How verification and validation differ in practice and why products usually need both.
SDLC and STLC
How development and testing lifecycles connect, and why QA engineers should understand both rather than only their own checks.
The Role of QA in Agile and Scrum
What QA contributes to an Agile team, how to participate throughout Scrum, and where to add the most value.
Testing Levels
What each testing level checks, which risks it covers, and why one level cannot replace another.
Types of Testing
Understanding testing types by objective, scope, and the risks they address.
Smoke, Sanity, Regression, and Retesting
Clear distinctions between smoke, sanity, regression, and retesting: when to use each and which terminology mistakes disrupt teams.
Black-Box, White-Box, and Gray-Box Testing
What these approaches mean, how they help QA, and how to choose the right depth of system knowledge for a task.
Shift-Left and Shift-Right
Understanding shift-left and shift-right in practical terms: which activities move earlier or later, and how this supports product quality.
Overview of Test Design Techniques
Why test design techniques matter, how they bring structure to testing, and which ones to learn first.
Equivalence Partitioning
How equivalence partitioning reduces test counts while preserving meaningful coverage and selecting representative data.
Boundary Value Analysis
Why defects often occur at boundaries and how to apply boundary value analysis to fields, ranges, and transition conditions.
Decision Tables
How decision tables clarify multi-condition logic and preserve important business-rule combinations.
State Transition Testing
How to test systems whose behavior depends on object status and find defects in workflow logic.
Use Case Testing
Testing through user goals and scenarios: when use case testing is more useful than checking individual fields and screens.
Pairwise Testing
How pairwise testing reduces parameter combinations and where it saves effort while maintaining useful coverage.
Cause-Effect Graphing
How to turn complex conditions and business rules into a cause-and-effect model and derive more precise tests for decision logic.
Error Guessing
How QA experience and intuition form a testing technique, and how to use error guessing systematically.
Checklist-Based Testing
How to build useful QA checklists, where they work well, and when they provide faster guidance than detailed test cases.
Exploratory Testing
What exploratory testing means in practice, how to keep it systematic, and why it is an effective technique for finding unexpected risks.
Risk-Based Testing
How to organize testing around risk instead of equal coverage everywhere, and why this is a mature QA approach.
Test Plan
What a useful test plan contains, when one is needed, and how to keep it practical.
Test Strategy
How a test strategy differs from a test plan and how to write one that guides product quality.
Test Scenario vs. Test Case
The practical difference between a test scenario and a test case: when each is useful and how confusing them weakens documentation.
Test Cases
How to write test cases that improve quality instead of becoming burdensome documentation with little practical value.
Checklists
How a checklist document differs from checklist-based testing as a technique, and how to create checklists the team actually uses.
Bug Report
How to write bug reports that help teams understand, reproduce, and prioritize problems quickly.
Severity vs. Priority
How to distinguish severity from priority and why QA should discuss them separately.
Traceability Matrix
Why traceability matrices matter, when they help, and how to track requirements coverage without unnecessary overhead.
Test Summary Report
How to write a test summary report that supports release decisions and provides practical value to the team.
QA Metrics
Which QA metrics support quality decisions and which create misleading confidence or harm team behavior.
What Is an API?
A concise introduction to APIs for QA: what they are, how systems communicate through them, and why understanding them enables deeper product testing.
Client–Server Architecture
How client–server architecture works and why QA needs to see the entire chain behind a UI button: the client, server, data, and integrations.
HTTP and HTTPS
A clear, accurate introduction to HTTP and HTTPS for QA: requests, responses, and secure data transmission.
REST, SOAP, GraphQL, gRPC, and WebSocket
A QA-oriented overview of the main API and integration approaches and their differences.
Methods, Status Codes, and Headers
How to read HTTP requests as a QA professional: what methods, status codes, and headers mean, and which defects they help you identify quickly.
JSON and XML
What QA should understand about JSON and XML, where each format appears, and common data-structure defects.
Authentication and Authorization
How authentication differs from authorization and what QA should test to protect access and enforce business restrictions.
JWT, OAuth 2.0, and API Keys
A concise, practical introduction to common API access mechanisms and what QA engineers should test in each one.
Negative API Testing
Why negative API checks matter and which classes of invalid requests QA engineers should test regularly.
Pagination, Filtering, and Sorting
Common defects in list APIs and how to test pagination, filters, and sorting thoroughly.
Contract Testing
What contract testing is, where it helps most, and how it catches client and service incompatibilities earlier.
Mock Servers
When mock servers help QA and when they create false confidence and hide integration problems.
Database Testing
What database testing involves for QA and which checks reveal data problems hidden from the UI and API.
SQL for QA
The SQL skills QA actually needs and how basic queries improve defect investigation and data verification.
NoSQL Basics
What QA engineers should know about NoSQL systems, how they differ from relational databases, and their common data risks.
Kafka and RabbitMQ Basics
Message queues and brokers for QA engineers: what matters in asynchronous systems and where defects commonly arise.
Testing Microservices
What microservice architecture means for QA and how to maintain quality in a system with many dependencies.
API Performance Basics
What QA needs to understand about API performance, even without doing full-scale performance testing every day.
API Security Basics
Essential API security checks for QA: what to look for in access controls, data, and errors, even without being a security engineer.
Understanding Web Applications
What QA engineers need to understand about web applications, from browsers and networks to client state and common sources of defects.
HTML, CSS, and JavaScript for QA
The HTML, CSS, and JavaScript fundamentals testers need to understand web applications and isolate defects faster.
DevTools for QA Engineers
How to use browser DevTools in everyday QA work: Network, Console, Elements, storage, and debugging.
Cookies, sessionStorage, and localStorage
A practical introduction to browser storage and its impact on testing.
Cross-Browser Testing
How to build a risk-based browser matrix, verify key scenarios across engines, and isolate compatibility problems.
Responsive Testing
How to test responsive interfaces at layout boundaries with realistic content, zoom, keyboard interaction, and state changes.
Testing Forms and Validation
Systematic checks of fields, boundaries, client and server rules, accessible errors, and form resubmission.
SEO and Meta Tag Basics
Essential SEO checks for QA: HTTP responses, titles, descriptions, robots rules, canonical URLs, rendering, and release diagnosis.
Accessibility Testing
How to check web accessibility through keyboard use, screen readers, contrast, zoom, errors, and measurable WCAG 2.2 criteria.
Visual Regression Testing
How to build useful visual checks: select states, stabilize environments, analyze diffs, and control baseline updates.
Website Testing Checklist
A practical web release checklist with expected results: scenarios, data, access, errors, compatibility, and documenting residual risk.
What Makes Mobile Testing Different
How mobile QA differs from web testing: lifecycle, networks, permissions, upgrades, devices, and failure diagnosis.
iOS vs. Android
Practical differences between iOS and Android for QA: environments, navigation, lifecycle, permissions, browsers, and comparing defects.
Native, Hybrid, Mobile Web, and PWA
How native, hybrid, mobile web, and PWA approaches differ, and how architecture shapes environments, updates, offline risks, and integration checks.
Installation, Update, and Uninstall
How to test the mobile application lifecycle: first installation, updates, rollback, and removal.
Permissions, Interruptions, and Notifications
How to test mobile apps in real user contexts: permissions, system interruptions, and push and local notifications.
Deep Links and App Links
What QA engineers should check in deep-link scenarios: routing, authorization, fallback behavior, and navigation security.
Network and Offline Testing
How to test mobile applications with weak connectivity, lost connections, and transitions between online and offline states.
Device Matrix
How to build a practical mobile QA device matrix without trying to test every possible configuration.
ADB Basics
Android Debug Bridge fundamentals for QA: logs, build installation, and troubleshooting.
Xcode and Android Studio Basics
The Xcode and Android Studio basics QA should know, even without working as a developer.
Charles / mitmproxy for Mobile QA
How proxy tools help mobile QA analyze traffic, debug APIs, and reproduce network scenarios.
Push Notifications
What QA should check in push notifications: delivery, display, deep links, access control, and behavior across application states.
Mobile Performance Testing
What QA should measure in mobile performance: startup, responsiveness, memory, battery, networking, and a consistent user experience.
Mobile Accessibility Testing
Practical accessibility checks for mobile QA: screen readers, text size, contrast, touch targets, and navigation.
Mobile Testing Checklist
A compact reference for checking a mobile application before a release, smoke test, or quick audit.
What Is Nonfunctional Testing?
An accessible introduction to nonfunctional testing: what it evaluates and why a product with working features can still fall short.
Performance Testing Overview
A practical map of performance testing for QA: goals, common questions, and responsibility boundaries.
Load, Stress, Spike, Endurance, and Volume Testing
How the main performance testing types differ and which question each helps answer.
RPS, Throughput, Latency, and Percentiles
The main performance metrics for QA, and how to distinguish attractive numbers from a useful picture of system behavior.
SLA, SLO, and SLI
How SLA, SLO, and SLI differ and why QA should understand them even outside an SRE role.
Security Testing Overview
A practical security testing introduction for QA: essential checks and the boundary with specialist security expertise.
OWASP Top 10
Why QA engineers should know the OWASP Top 10 and use it as a map of common web risks rather than a list to memorize.
SQL Injection, XSS, and CSRF
Three classic web security risks QA engineers should understand in practice: how they work and where they are commonly missed.
Compatibility Testing
A systematic approach to compatibility across devices, operating systems, browsers, versions, integrations, and external dependencies.
Localization and Internationalization
What QA needs to know about i18n and l10n: formats, text, layout, writing direction, and hidden localization risks.
Reliability, Recovery, and Failover
How QA engineers assess system reliability: resilience to failures, recovery, and switching to backup mechanisms.
Usability Testing
How QA can support usability testing without being a UX researcher, and what to observe in user scenarios.
When to Automate
How to identify checks worth automating and those better handled manually or moved to another level.
Automation ROI
How to assess automation realistically: time savings, signal quality, maintenance costs, and release impact.
The Testing Pyramid
Why the testing pyramid matters and how to use it as a principle of balance rather than a rigid rule.
Unit, Service, UI, and E2E
How automated test levels differ and what signal each provides.
Page Object Model
Why Page Object Model exists, where it helps, and why it cannot rescue poor UI automation by itself.
Screenplay Pattern
How Screenplay differs from the Page Object Model and when it makes automated test architecture easier to maintain.
Data-Driven, Keyword-Driven, and Hybrid Testing
A concise guide to common automation framework approaches and their practical value for teams.
BDD, Cucumber, and Gherkin
When BDD helps a team and when it becomes a decorative layer over ordinary automated tests.
Selenium WebDriver
What QA should know about Selenium WebDriver: strengths, limitations, and common sources of maintenance problems.
Cypress
What makes Cypress useful for frontend QA and where its architectural limitations become apparent.
Playwright
Why Playwright has become a strong option for modern web automation and which tasks it handles particularly well.
Appium
An introduction to Appium for mobile automation: its coverage, practical uses, and why mobile tests are especially sensitive to architecture.
Pytest + Requests
Why Pytest and Requests work well for API automation and what they teach QA engineers beyond writing tests.
REST Assured
Why REST Assured is a strong Java API automation option and what matters in test architecture.
Allure Reports
How Allure reports help and why useful reporting should support investigation as well as presentation.
Flaky Tests
A systematic approach to flaky tests: causes, classification, and strategies to reduce noise without misleading yourself.
CI Integration for Automated Tests
How to integrate automated tests into CI so they accelerate releases and provide a useful, reliable signal.
Postman
How QA engineers use Postman to explore APIs, build collections, manage environment variables, and obtain fast integration feedback.
Insomnia
Where Insomnia helps QA and how its workflow differs from other API clients.
SoapUI
Why SoapUI remains useful for certain enterprise scenarios and where it is particularly well suited to QA.
Swagger / OpenAPI
How QA uses Swagger and OpenAPI to read documentation, verify contracts, and establish API expectations.
Newman
What Newman does and how it turns Postman collections into repeatable executable artifacts for CI and regression testing.
TestRail
Where TestRail helps QA teams and how to keep a test management tool from becoming a bureaucratic archive.
Zephyr
What QA needs to understand about Zephyr in the Jira ecosystem and where it helps manage testing.
Xray
How Xray connects testing to Jira workflows and where it is especially useful for teams that need strong traceability.
Qase
When Qase suits a QA team and how to keep it useful instead of accumulating obsolete test cases.
Allure TestOps
How Allure TestOps connects automated test results, manual scenarios, and quality analytics, and where it provides practical value.
Jira
How QA can use Jira to manage defects, work, and release decisions effectively.
YouTrack
How QA teams can use YouTrack effectively for search, tagging, and defect management.
Redmine
Why some teams still use Redmine and what QA needs to know when working with an older but practical bug tracking stack.
Linear
How QA can use Linear while preserving thorough defect analysis in a fast product and engineering workflow.
Trello
Where Trello helps QA and the limitations to understand when using it to track defects and testing tasks.
JMeter
Where JMeter remains useful for performance work and what QA needs to understand before building load tests with it.
k6
Why modern teams choose k6 and how its strengths support performance testing in engineering workflows.
Gatling
Gatling strengths and when teams choose it for more complex, larger-scale performance scenarios.
Locust
Where Locust helps QA and how its Python-first approach makes performance scenarios transparent and manageable.
LoadRunner
Why LoadRunner remains common in enterprise systems and which strengths and limitations QA should understand.
Charles Proxy
How QA engineers use Charles Proxy to analyze traffic, replace responses, and debug web and mobile scenarios.
Fiddler
When Fiddler is useful for QA and how it helps investigate network scenarios, particularly in desktop and web applications.
mitmproxy
When a scriptable proxy gives QA more value than simply inspecting network traffic.
Wireshark
When QA engineers need Wireshark and how its analysis differs from conventional proxy tools.
Release Testing
How to treat release testing as a controlled risk decision rather than a last-day rush through a checklist.
Regression Strategy
How to build a regression strategy that covers real risks without becoming an endless, expensive ritual.
Test Environments
Why a test environment is an essential layer of quality that determines how much confidence you can place in test results.
The 7 Principles of Testing Explained Simply
The seven testing principles without dry theory: what they mean, how they appear in everyday QA work, and why interviewers often ask about them.
Test Design Techniques
Equivalence partitioning, boundary value analysis, decision tables, and other essential test design techniques.
QA, QC, Testing, Verification, and Validation: What Is the Difference?
Understand essential QA terminology: how QA differs from QC, what testing, verification, and validation mean, and how to explain them in interviews and everyday work.
Functional, Nonfunctional, Smoke, Sanity, Regression, and Retesting
Common testing types in everyday QA: what smoke, sanity, regression, and retesting mean, and how functional and nonfunctional testing differ.
Error, Bug, Defect, and Failure: Understanding the Terms
How Error, Bug, Defect, and Failure differ, how they relate, and how to explain them clearly.
Equivalence Partitioning and Boundary Value Analysis
Two fundamental test design techniques: how to apply equivalence partitioning and boundary value analysis to forms and APIs and avoid arbitrary input testing.
Testing Requirements: Theory and Practice
How QA reviews requirements before execution: what to look for, which questions to ask, and how to identify risks before coding.
SDLC, STLC, and Development Models: Waterfall, V-Model, and Agile
Understanding SDLC and STLC alongside Waterfall, V-Model, and Agile: what QA needs to know and how the tester's role changes in each approach.
How to Write an Effective Bug Report
How to write clear titles, reproduction steps, expected and actual results, and attachments so bugs are easy to understand, reproduce, and fix.
The Defect Lifecycle: From Discovery to Closure
The defect lifecycle: common bug statuses, responsibilities, and why the logic behind status transitions matters.
Severity and Priority: How to Prioritize Bugs
The difference between severity and priority, common combinations, and frequent mistakes in defect assessment.
Black Box, White Box, and Gray Box: What QA Engineers Need to Know
The differences between black box, white box, and gray box testing, where each applies, and what practicing QA engineers need.
Test Documentation: Checklists, Test Cases, Test Suites, and Test Plans
The main test documentation types: how checklists, test cases, test suites, and test plans differ, when to use them, and how to avoid unnecessary process overhead.
Decision Tables, State Transitions, Pairwise, and Exploratory Testing
Practical test design techniques: when decision tables, state transitions, pairwise testing, and exploratory testing help and how to apply them without academic overload.
Learning paths
Start with the fundamentals and move on to practical checks. Each path lists articles in a suggested reading order.
Test design
Choose effective checks with equivalence classes, boundaries, and decision tables.
SQL and databases for QA
Learn SQL and database checks to test applications with more confidence.
Resources for practice
Download a checklist, template, or exercises to use in your work. All resources are free, with no sign-up required.
API testing checklist
31 API checks covering contracts, permissions, input, retries and state.
Download MarkdownTest case template
A blank template and two worked examples for boundaries and permissions.
Download MarkdownSQL for QA: 8 exercises
Reproducible data, queries, answers and common JOIN and NULL mistakes.
Download Markdown SQL practice dataset (.sql)