CF
Testing & QA thumbnail

Testing & QA

39 courses 6 categories

Testing and QA is the discipline of building confidence that software does what it is supposed to and keeps doing it as the codebase changes. The topic covers the full pyramid: unit tests against pure functions, integration tests against database and queue boundaries, end-to-end tests that drive a real browser, contract tests between services, performance tests under load, and the accessibility and visual-regression layers that catch the things the other tests miss.

The browser-automation stack has consolidated sharply since 2023. Playwright is now the default for new projects — Microsoft maintains it, every major browser is supported, the auto-wait and trace viewer are far ahead of competitors, and the test-runner ergonomics are excellent. Cypress still has a large installed base and remains strong for component testing. Selenium and WebdriverIO hold the long-tail of legacy enterprise suites and cross-browser grids; courses still teach them because real jobs still use them. Protractor is deprecated but appears in older Angular codebases. On the unit-test side: Vitest, Jest, pytest, JUnit, RSpec — the boring choices that work.

What you'll find under this topic

  • End-to-end testing: Playwright, Cypress, WebdriverIO, Selenium
  • Component testing: Cypress Component, Playwright Component, Storybook
  • Unit and integration testing: Vitest, Jest, pytest, JUnit, mocking strategies
  • Test design: TDD, BDD, page-object pattern, fixtures, data factories
  • CI integration: GitHub Actions, GitLab CI, parallelization, sharding, flake control
  • Performance and load testing: k6, JMeter, Gatling, Locust
  • Accessibility, visual regression, and contract testing

QA roles range from pure manual testers at regulated-industry shops to SDETs (software-development engineers in test) at FAANG-scale companies who write more code than most developers. The skill set transfers across employers because the test pyramid does not change — only the framework names do.

Top 10 picks for 2026

Categories (6)

Cypress thumbnail
Cypress
Cypress is a browser-based end-to-end testing framework designed to run tests in the same event loop as the application…
Playwright thumbnail
Playwright
Playwright Test — End-to-End Testing Framework for Modern Web Apps Playwright Test is a powerful end-to-end (E2E)…
Protractor thumbnail
Protractor
Protractor was an end-to-end testing framework specifically designed for Angular applications. Developed and maintained…
QA & Testing thumbnail
QA & Testing
QA and testing is no longer the separate-team activity it was a decade ago. In modern software organizations…
Selenium thumbnail
Selenium
Selenium is a browser automation framework that has been a cornerstone of end-to-end web testing for almost two…
WebdriverIO thumbnail
WebdriverIO
WebdriverIO is a browser automation framework based on Node.js, offering an alternative to tools like Cypress and…

Courses (39)

Showing 1 – 30 of 39 courses

Related topics

Frequently asked questions

Is testing a real career path or just a skill?
Both. Quality engineering, SDET, and test-automation roles are well-paid and in steady demand, especially at companies where regressions are expensive (fintech, healthtech, infrastructure). Many engineers also use testing fluency as a force multiplier inside a regular dev role. The pure manual-QA market has shrunk; the automation-focused QA market is strong.
Unit vs integration vs end-to-end — what's the right mix?
The classic pyramid still mostly holds: lots of fast unit tests, a meaningful integration layer, a smaller set of end-to-end tests covering critical user journeys. Modern variations (testing trophy, honeycomb) push integration tests higher. Whatever shape you pick, prioritise reliability — flaky tests are worse than missing tests because they erode trust.
Playwright vs Cypress vs Selenium?
Playwright has won most new projects in 2024–2026 — fast, multi-browser, great debugging, sensible API, strong network stubbing. Cypress remains popular and has a passionate community. Selenium persists in enterprise and where multi-language support matters. For a new test suite Playwright is the default pick; Cypress is a credible alternative.
How much testing should I actually write?
Enough that you trust your CI and refactor without fear; not so much that the test suite becomes a maintenance liability. Test what matters most — pure logic, edge cases, contract boundaries with external systems, and the critical user paths end to end. Skip trivial getter/setter tests and over-coupled UI snapshot tests.
Is AI changing test automation?
Yes, gradually. LLM-powered test generation, self-healing locators, and natural-language test authoring are real products. They're useful as accelerators but not yet replacements — the hard part of testing is deciding what's worth testing, not typing the test. Treat AI tools as productivity multipliers for engineers who already understand quality engineering.