The Complete QA Bootcamp: From Beginner to Job Ready

Explore software delivery as an end-to-end process from design and coding to testing and delivering a functional product, and compare Waterfall with Agile to highlight flexible, value-driven approaches.

Describe the waterfall model as a linear, phase-driven approach to software development, detailing requirements gathering, system design, implementation, testing, deployment, and maintenance.

Explain why teams still use waterfall or mix agile and waterfall in practice. Learn how this approach helps keep software flowing in many companies.

Explore agile principles and values that prioritize customer satisfaction through early and continuous delivery of valuable software, adaptability, collaboration, and self-organizing teams.

Discover how the software development lifecycle guides planning, design, development, testing, deployment, and maintenance, with qa involvement at every stage to reduce risk and align engineering, product qa, and stakeholders.

Scrum, the common form of agile, uses empirical process control with transparency, inspection, and adaptation, and defines roles like product owner, Scrum master, designers, developers, testers.

This daily scrum shows a 15-minute stand-up where backend, frontend, QA, product owner, and scrum master share yesterday’s work, today’s tasks, blockers, and alignment on profile updates and acceptance criteria.

Refine the sprint backlog to keep items well-defined and prioritized, then conduct sprint planning to define the sprint goal, select items, and create a task-ready sprint backlog.

Explore how Scrum documents work through initiatives, epics, and user stories, detailing roles, actions, benefits, and subtasks for development and testing.

Define clear, testable acceptance criteria using given-when-then, refined in grooming, linked to test cases, and used by product, devs, qa, and stakeholders to guide testing and release.

Visualize the workflow with a kanban board to track tasks across to-do, in-progress, and done. Limit work-in-progress, optimize flow, and pursue continuous improvement through feedback and adaptable policies.

Issue tracking with Jira creates a single source of truth for bugs, tasks, and user stories, helping QA report defects, track fixes, and manage testing progress across environments.

Learn how Jira tracks work, turning tasks, stories, and bugs into issues, and how to sign up, create a project, start a sprint, and move issues through to done.

Practice creating issues and tasks on the board, link related work items using relates to, and add subtasks under stories to show parent relationships.

Configure the board by adding a new status and adjusting transitions, then rename columns to reflect stages: to do, in development, in testing, ready for release, and done.

Master the basic Jira workflow for sprint teams by moving a story from to do through in development and in testing to ready for release, with reviews and bug handling.

Manual testing forms the foundation of QA work, with testers interacting with the software like real users and verifying functionality without automation.

Prioritize testing by scoring risk and impact to allocate effort where failures block core features or harm customers, guiding manual and automated coverage as the product evolves.

Regression testing verifies existing functionality after changes, protecting the product from unintended side effects and ensuring releases perform as well or better. Combine automation with risk-based prioritization for reliable releases.

User-based testing evaluates a product from real users' perspectives, uncovering confusion, hesitations, and intuitive issues beyond function checks, guiding UX improvements and reducing rework.

Learn how integration testing validates data flow and interactions across components, from APIs and databases to authentication workflows, ensuring end-to-end paths like a login flow work reliably.

Prioritize testing on high-risk areas where failures threaten business goals, guided by a simple risk matrix that weighs likelihood and impact.

Understand how a test environment provides a controlled, production-like space where testers safely verify updates before they reach customers, and explore new code, configurations, and data.

Explore functional testing and its levels from unit to integration, system, and user acceptance testing. Discover how each level validates behavior and usability against user needs.

Define test scenarios as high-level ideas that capture main functionality and real user workflows, guiding test case creation for critical features like login, checkout, transfers, and statements.

Analyze requirements by reviewing documentation, user stories, and stakeholder expectations to translate them into testable elements and plan tests; identify ambiguities and define acceptance criteria to guide testing.

Master boundary value analysis to test edges of input ranges, catch off-by-one and validation errors, and verify date, length, and range rules with equivalence partitioning.

Master equivalence partitioning to divide inputs into valid and invalid partitions, test one representative value per partition, and enhance coverage with boundary value analysis across UI, API, and backend.

Identify and classify defects as gaps between expected and actual software behavior, spanning UI, logic, API calls, and data handling, to guide testing and improve quality.

Understand how severity measures technical damage and priority captures business urgency to prevent miscommunication among qa, developers, and product teams. Apply these concepts in release planning and triage.

learn how to write clear bug reports with structure, environment details, reproducible steps, evidence, and priority and severity to communicate facts and enable fast fixes.

Good bug reports communicate clearly with reproducible steps, include severity and priority, attach screenshots or logs, and specify environment and platform. Bad reports omit steps and context, causing delays.

Describe reproducible steps as a recipe to reliably recreate a bug, removing ambiguity, and include actions, data, and visual evidence so developers reproduce defects in their environment.

Use screenshots, videos, and logs to make bug reports verifiable; annotate with context, timestamps, and arrows to aid debugging across console, network, and server logs.

Understand the bug lifecycle from new report to resolution, covering triage, assignment, in progress, fixed, and quality assurance verification, with reopened, deferred, duplicate, won't fix, and cannot reproduce states.

Plan, execute, and track testing with a test case management system that centralizes cases and suites. Attach evidence, ensure traceability to requirements, and use reporting to guide release decisions.

Install X-Ray in Jira to manage test cases, executions, and plans from Jira dashboard. Create issue types: Test, Precondition, Test Set, Test Plan, Test Execution, and environments Dev, QA, Prod.

Create and organize Jira test cases by selecting test type (manual, generic, cucumber), add steps and preconditions, and group tests into sets, plans, and runs.

Create a test plan, add the login and logout tests, and manage test executions to track status.

Demonstrates building test cases with parameterized datasets for login, including username and password, and using combinatorial datasets to generate iterations, then linking them to test plans and executions.

Organize test cases in the test repository by creating feature folders such as auth and checkboxes. Drag tests into these folders to streamline organization and prepare for future test plans.

Learn how to link a test case to its story and associate login tests to the story, then run tests and track statuses from to do to green.

Create and link test cases for superhero app stories, test login and roster flows, track defects, and manage blockers through a Jira-based sprint and test plan cycle.

Map desktop and mobile architecture to reveal how UI, business logic, and data layers interact, guiding QA strategies across OS APIs, device constraints, and network conditions.

Learn installation testing to verify initial install, updates, reinstallation, and clean uninstallation across systems, prevent errors and leftover files, and ensure smooth onboarding.

Ensure apps work across desktops, tablets, and mobiles through OS, browser, hardware, and network compatibility testing. Leverage emulators, real devices, analytics, and automation for reliable device coverage.

Perform UI and interaction testing to ensure visual correctness, accessibility, and responsive behavior across web, desktop, mobile, and hybrid apps.

Practice system resource and file interaction testing across platforms to verify safe OS resource use, proper read-write flows, sandboxed permissions, path handling, encoding, and atomic write techniques.

Explore common desktop and mobile bugs, including layout, viewport, and dpi issues, input and permission bugs, navigation and state management, and performance and accessibility considerations.

Master command line basics as a text-based interface used for Git, npm, test automation, and servers and APIs, using Windows cmd, Git Bash, Mac terminal, and VS Code terminal.

Learn how to manage files and folders in a qa-practice directory, creating, renaming, moving, copying, and deleting files with Windows and Mac commands.

Demonstrate practical terminal commands for software testing, including clearing the screen with CLS on Windows or CLEAR on Mac, accessing help, using the up-arrow history, and stopping servers with Ctrl+C.

Engage in hands-on exploratory testing that designs and runs tests in real time, uncovering risks and defects quickly through evidence, logs, and evolving heuristics.

Contrast exploratory testing with scripted testing, showing how charter-driven exploration and checklists paired with automation enable rapid risk discovery, actionable evidence, and regression-safe coverage for compliance.

Charters structure exploratory testing by defining intent, scope, and constraints, and timeboxed sessions, guiding focused, evidence-driven exploration that links risks to defects and regression protection.

Learn how heuristics guide testers to generate test ideas, broaden coverage, and uncover risks using SFDPoT six dimensions, CRUD operations, and platform-aware prompts.

Explore exploratory testing with five TORs—data, interruption, error, scenario, and configuration—that guide risk-focused testing, reveal defects through boundary values and malformed records, and document outcomes.

Learn to take disciplined, lightweight notes during exploratory testing, capturing steps, evidence, timestamps, and comparisons of expected versus actual behavior to drive defects and actions.