Quality Assurance
Learn to test software thoroughly, communicate defects clearly, and understand how quality fits into modern development teams. A practical track that opens a technical career path without requiring you to write application code.
About this track
QA is how teams prove software does what buyers expect, and how they catch it early when it does not. You learn to design tests, run manual and exploratory passes, write bug reports developers can act on, and handle regressions without panic. Tools include a Jira-style tracker, simple spreadsheets for cases, browser DevTools for evidence, and Postman when APIs are in scope. Habits matter more than vendor logos: clear steps, honest severity, and tight communication with engineering. You practise on real builds, not toy puzzles.
Who this track is for
QA is one of the clearest technical career paths that does not require writing application code from day one.
People who have tested software informally or in non-QA roles and want to apply structured, professional practices.
Developers who want to write better software by understanding how it will be tested, and how QA thinking improves engineering.
What you will learn
Organised into modules that build on each other. The content is structured, not arbitrary.
QA fundamentals and the testing mindset
- What QA is and where it fits in a product team
- The difference between testing and quality assurance
- Thinking like a tester: adversarial, systematic, curious
- Understanding software development workflows (Agile, sprints, releases)
Test case design and documentation
- Writing test cases that are clear, repeatable, and complete
- Test coverage: what to test and why
- Equivalence partitioning and boundary value analysis
- Documenting test plans and test suites
Manual and exploratory testing
- Executing test cases against a real application
- Exploratory testing: structured investigation without a script
- Regression testing: verifying fixes don't break existing behaviour
- Cross-browser and cross-device testing basics
Bug reporting, workflow tools, and API checks
- Writing bug reports that developers can act on
- Bug severity and priority, and why they are different
- Jira or equivalent: boards, issues, and how QA plugs into delivery
- Browser DevTools for reproduction evidence and quick network checks
- API testing with Postman: requests, assertions, and when APIs need QA attention
Tools & technologies we use
The same categories of tools QA teams use in the wild, without pretending every company picks the same vendor. Principles first; interfaces follow.
Jira or equivalent
Issues, workflows, and traceability from reproduction steps to release decisions.
Google Sheets or light test-management habits
Test cases, matrices, and coverage notes that stay honest and shareable, even without enterprise tooling.
Browser DevTools
Console, network, and layout clues that make bug reports credible.
Postman
Calling endpoints, inspecting payloads, and catching contract issues before they reach users.
Your mentor may standardise on one issue tracker for the cohort, but the habits transfer to Linear, Azure DevOps, and other systems.
How the learning works
Not self-paced video content. A structured programme with real outputs and structured feedback.
Real applications, real defects
You test actual software with real bugs to find, not artificial exercises designed to be easy.
Documentation focus
Writing good bug reports and test cases is a skill in itself. You practise this with structured feedback on your output.
Team workflow simulation
QA doesn't happen in isolation. Sessions include understanding how your work connects to development, product, and release decisions.
What this prepares you for
Realistic, honest expectations. The track gives you foundation and practice. What you do with it determines what comes next.
A portfolio of test cases, test plans, and documented bug reports
Confidence executing manual and exploratory testing with DevTools, trackers, and Postman where needed
Understanding of how QA fits in a professional development team
Foundation for junior QA analyst, test analyst, or software tester roles
Quality Assurance: common questions
Track-specific answers: prior knowledge needed, what you build, tools used, and how to get started.
Still have a question not covered here?
Start a conversationReady to start the Quality Assurance track?
Contact us to confirm the next intake date and ask any questions before you commit.
Contact Folowise if you have questions before applying.