Sitemap
Every page, one list
All 203 pages on tesbo.io, grouped by section. Nothing here is behind a filter or a “load more”.
Product
What Tesbo is, what it costs, and the free tools around it.
Solutions by role
How Tesbo fits the job you already do.
Comparisons
Tesbo against the tool you are on today.
QA roadmap
The career path, and every guide written for it so far.
- Testing inside a sprint, day by day
- Risk analysis and quality strategy
- Anatomy of an LLM feature
- How LLMs work — enough to test with them
- Performance testing: k6, JMeter, Gatling
- CI/CD for test suites
- The pyramid, the trophy, and choosing per system
- One language, properly: TypeScript or Python
- What quality means when code is cheap
- Refinement, acceptance criteria and the three amigos
- Communicating risk to people who don’t test
- RAG systems explained for testers
- Prompting for test work: specs in, tests out
- Thinking in percentiles, not averages
- Sharding, parallelism and runtime budgets
- Test architecture: fixtures, builders, page objects
- Git, branching and pull-request review
- The QA mindset: risk, not coverage
- Writing test cases someone else can run
- Writing as the primary interface
- Agents: planning, tool calls, memory, loops
- Coding agents in the QA loop
- Load profiles: soak, spike, stress, breakpoint
- Test impact analysis and selection
- Playwright as the default web stack
- Reading a codebase; reading a diff
- Verification vs validation
- Writing a bug report that gets fixed
- Being the quality voice in spec and design review
- Why assertions break: non-determinism and drift
- Spec-first automation
- Frontend performance and Core Web Vitals
- Ephemeral preview environments
- Selenium and Cypress literacy
- HTTP, REST, status codes, headers
- Delivery models: agile, scrum, kanban, trunk-based
- Defect triage: severity, priority and who decides
- Coaching developers; embedded quality models
- Evals: the new test suite
- Reviewing AI-written tests
- Security: the OWASP Top 10
- Feature flags and progressive delivery
- API testing and schema validation
- GraphQL and gRPC for testers
- Test design: equivalence, boundary, decision tables
- Running a regression cycle
- Owning the test estate: platform thinking
- Building a golden dataset
- AI for exploratory testing and test ideas
- OWASP API Security Top 10
- Canary releases and automated rollback
- Contract testing with Pact
- Auth: sessions, JWT, OAuth2, OIDC
- State transition and pairwise testing
- Choosing what goes in the regression pack
- Career tracks: SDET, quality engineer, AI quality
- LLM-as-judge, and its failure modes
- Coverage gap analysis with AI
- SAST, DAST and SCA in the pipeline
- Observability: logs, metrics, traces
- Mocking and service virtualisation
- SQL and the data layer
- Black, white and grey box
- Smoke, sanity, UAT: who runs what, and when
- Proof of work: portfolio, public suites, writing
- Rubrics, scoring and inter-rater agreement
- Self-healing locators: what breaks and when
- Supply chain: SBOM and dependency risk
- SLOs and error budgets
- Mobile: Appium, Espresso, XCUITest, Maestro
- Queues, events and async systems
- Functional vs non-functional
- Writing a test strategy
- Offline evals vs online evals
- Failure triage: clustering and log summarisation
- Secrets management
- Synthetic monitoring and testing in production
- Component and unit testing
- The browser platform: DOM, events, rendering
- Test oracles: how you know it’s right
- Writing a test plan
- Groundedness, faithfulness, hallucination rate
- Large-scale migration with agents
- Accessibility: WCAG 2.2, axe, screen readers
- Incident response, RCA and postmortems
- Visual and snapshot regression
- DevTools and network debugging
- Exploratory and session-based testing
- Entry criteria, exit criteria and the definition of done
- Task success and tool-call accuracy
- Building QA tooling on LLM APIs
- Accessibility law: the European Accessibility Act
- Quality metrics: DORA, escape rate, MTTR
- Test data: factories, seeding, anonymisation
- Containers: Docker and Compose
- Estimating test effort
- RAG testing: retrieval precision and recall
- MCP: wiring agents to your test estate
- Privacy in test data: GDPR and DPDP
- Flakiness: causes, quarantine, retry policy
- Cloud basics: environments, config, secrets
- Traceability: requirement to test to result
- Chunking, ranking and citation checking
- Cost, latency and determinism in CI
- Resilience and chaos basics
- Determinism: clocks, seeds, network control
- The test summary report and release sign-off
- Agent trajectory testing
- What never goes in a prompt
- Test management: Jira, Xray, TestRail, Zephyr
- Tool misuse and loop detection
- Measuring whether AI actually helped
- Drafting QA documents with AI
- Prompt injection: direct
- Prompt injection: indirect
- Jailbreaks and data exfiltration
- Excessive agency and blast radius
- OWASP Top 10 for LLM Applications
- OWASP Top 10 for Agentic Applications
- Red-teaming an AI feature
- Guardrails, refusals and over-refusal
- The model-bump problem
- AI governance: the EU AI Act, ISO 42001, NIST AI RMF
Articles
Writing on testing, quality, and the teams that do it.
- Unit Testing vs Integration Testing: What Each One Actually Checks
- The API Test Case Template: 9 Fields, One Worked Example
- TestLink Alternatives: The Four Real Reasons Teams Actually Leave
- Test Case Management for Agile Teams: Surviving a Two Week Sprint
- Out of the Spreadsheet: When and How to Move Your Test Cases to a Real System of Record
- Linking Test Cases to Jira Issues So the Link Survives the Sprint
- Source Available vs Open Source: The Three Questions That Settle It
- An Open Source QA Stack for a Team of Six: The Joins Nobody Writes Down
- Test Case Versioning: What Changed, When, and Who Agreed to It
- Positive and Negative Testing: The Cases That Actually Find Bugs
- System Integration Testing: And Whose Bug It Is
- GxP Test Documentation, in Plain Terms
- Test Evidence for a 21 CFR Part 11 Audit
- End-to-End Testing: What It Proves That Nothing Else Does
- Test Management Tools: 15 Options, Grouped by Team Fit
- Gray Box Testing: Why Most Real Testing Is This
- Black Box vs White Box Testing: Two Different Case Sets
- Component Testing: The Layer Between Unit and Integration
- Traceability for Medical-Device Software (ISO 13485)
- Test Evidence for an Audit: Proving Testing Happened
- Sanity Testing: When It Is Genuinely Different From Smoke
- API Testing: A Complete Guide to Cases, Types and Tools
- What Is a Bug? The Real History of the Word
- Defect Leakage: The QA Metric Measured Against Reality
- Exploratory Testing That Leaves a Record
- Smoke Testing: The Check That Decides Whether Testing Starts
- Test Scenario vs Test Case: Which One a Risk Needs
- Mobile App Testing: Types, Checklist and Tools
- Software Testing in 2026: The Trends That Are Real
- The Best AI Testing Tools Depend on the Job You Have
- Self Hosted vs Cloud Test Management: How to Decide
- Smoke vs Sanity vs Regression Testing: Three Words, One Confusion
- Self-Hosted Test Case Management: What You Actually Take On
- Free Test Management Platform: Where Free Runs Out
- Flaky Tests Are a Design Problem, Not Bad Luck
- Test Automation Strategy: Three Questions, Not a Tool
- Audit Trail in Test Management: The Approval Log
- Negative Test Cases for APIs: The Ones That Find Bugs
- The Complete Guide to Software Testing Strategies, Types & Tools
- AI in Software Testing: What Actually Works
- When Not to Automate a Test (and What to Do Instead)
- API Test Cases: What a Real One Contains
- Test Management Tool Migration Plan: Keep the History
- Bring Your Own API Key: AI Tools and Your Data
- Will AI Replace QA Engineers? The Honest Answer
- How to Document Exploratory Testing (Without the Bloat)
- Session-Based Test Management, Explained
- QA Metrics: The Four Worth Reporting (and Why)
- Flaky Test Detection: Finding Them in Your Run History
- AI Test Case Generation: Generate Freely, Merge Carefully
- What to Automate First in Testing: A Scoring Method
- Open-Source Test Case Management: What Actually Matters
- Test Case Management: The Record a Release Rests On
Learning
Longer, structured pieces you work through.
Test case library
Ready-made test cases you can copy into your own suite.
Infographics
One idea, drawn.
Release notes
What shipped, and when.