Software Testing Syllabus 2026: Manual, Automation and API Testing

The software testing syllabus in 2026 is no longer just manual test cases and bug reports. The industry has moved toward SDET (Software Development Engineer in Test) roles where testers write code, automate regression suites, integrate testing into CI/CD pipelines, and validate APIs before a single UI screen exists.

But the foundation has not changed. You still need to understand the software development lifecycle, you still need to write test cases, and you still need to think critically about what could go wrong. Automation without that foundation is just faster bad testing.

This syllabus covers the complete path in five modules: testing foundations, manual testing in practice, automation with Selenium, API testing with Postman, and CI/CD plus performance testing in agile environments.

Each module includes specific topics, learning outcomes, and a practice idea. Follow it in order. The automation modules will not make sense without the manual testing foundation that comes first.

For the full cost breakdown of testing programmes, see the software testing course fees guide. 

For structured learning options, explore Scaler Academy and Scaler’s free courses.

Who Should Learn Software Testing (and the Outcomes)

This syllabus is built for three groups:

• First-year CS students who want to understand how quality assurance works before specialising
• Career switchers entering QA or SDET roles from non-tech backgrounds
• Developers who want to write testable code and understand the testing side of the pipeline

By the end of this syllabus, you will be able to write test cases and test plans, perform manual functional and regression testing, automate web application tests using Selenium and TestNG, test REST APIs using Postman with assertions and automation, and understand how testing fits into CI/CD pipelines and agile workflows.

The ISTQB Foundation Level syllabus is the globally recognised baseline for software testing knowledge. 

This syllabus covers the ISTQB foundation topics in Modules 1 and 2 and goes beyond them into automation, API testing, and CI/CD in Modules 3 through 5. The World Quality Report by Capgemini tracks industry trends and consistently shows that QA budgets are shifting toward automation and AI-augmented testing, which is why this syllabus dedicates three of five modules to automation-related skills.

Module 1: Testing Foundations (SDLC, STLC, Test Design)

Every tester, manual or automated, needs to understand how software is built and how testing fits into that process. This module covers the concepts that never change regardless of what tools you use.

Topic	What You Learn	Outcome
Software Development Life Cycle (SDLC)	Waterfall, V-model, iterative, agile models	You understand where testing fits in each development model
Software Testing Life Cycle (STLC)	Requirement analysis, test planning, test design, execution, closure	You can describe the testing process from start to finish
Testing principles	Seven ISTQB principles (e.g., exhaustive testing is impossible, pesticide paradox)	You understand why testing cannot prove absence of defects
Test levels	Unit, integration, system, acceptance testing	You know which testing happens at which stage
Test types	Functional, non-functional, structural, change-related (regression, re-testing)	You can classify any test by type and purpose
Test design techniques	Equivalence partitioning, boundary value analysis, decision tables, state transition	You can design effective test cases that cover maximum scenarios with minimum cases
Test plan and test case writing	Structure of a test plan; test case format (ID, steps, expected, actual, status)	You can write a professional test plan and structured test cases
Defect lifecycle	New, assigned, open, fixed, re-tested, closed, deferred, rejected	You understand the journey of a bug from discovery to resolution
Bug reporting	Key fields: severity, priority, reproducibility, environment	You can write bug reports that developers can act on

Practice idea: Take a simple web application (a login page or a calculator) and write a complete test plan: identify test scenarios, design test cases using equivalence partitioning and boundary value analysis, and write at least three bug reports for intentional defects. This single exercise covers most of Module 1.

For a detailed explanation of the development lifecycle, see the Software Development Life Cycle tutorial on Scaler Topics.

Module 2: Manual Testing in Practice

Manual testing is not obsolete. Automation handles repetitive regression checks. Manual testing handles exploratory testing, usability evaluation, and edge-case discovery that scripts cannot anticipate. Every good automation engineer started as a manual tester, because you cannot automate what you do not understand.

Topic	What You Learn	Outcome
Functional testing	Verifying each feature against requirements	You can systematically test a feature and document results
Regression testing	Re-testing after changes to ensure nothing broke	You can identify which test cases to re-run after a code change
Smoke and sanity testing	Quick checks before deep testing; focused checks after fixes	You know when to run a broad quick check vs a targeted deep check
Exploratory testing	Unscripted testing driven by curiosity and experience	You can find bugs that scripted test cases miss
Usability testing	Evaluating user experience, navigation, accessibility	You can assess whether a product is usable, not just functional
Cross-browser and cross-device testing	Testing on different browsers, screen sizes, operating systems	You can identify environment-specific defects
Bug tracking with JIRA	Creating tickets, linking to test cases, tracking resolution	You can manage defects professionally in an industry-standard tool
Test execution and reporting	Running tests, logging results, generating test summary reports	You can produce clear reports on testing progress and quality status

Practice idea: Pick a publicly available website (an e-commerce site or a travel booking portal) and perform a full manual testing cycle: write test cases for the search and checkout features, execute them, log at least five bugs in a spreadsheet (simulating JIRA format), and write a test summary report. This is closer to real QA work than any tutorial exercise.

For broader reference on testing topics, explore Scaler Topics.

Module 3: Automation Testing with Selenium

This is where testing starts to require coding skills. Selenium is the most widely used web automation framework in the industry, and it is the tool that most automation testing interviews focus on. You need a working knowledge of Java or Python before starting this module. If you do not have that, learn one of them first.

Topic	What You Learn	Outcome
Selenium WebDriver architecture	How WebDriver communicates with browsers; driver types	You understand what happens when you write driver.get()
Locators	ID, name, class name, CSS selector, XPath	You can identify and target any element on a web page
WebDriver commands	Navigation, element interaction (click, type, select), waits (implicit, explicit, fluent)	You can write scripts that interact with web applications
Synchronization	Implicit waits, explicit waits, fluent waits	You can handle timing issues that cause flaky tests
TestNG framework	Annotations (@Test, @BeforeTest, @AfterTest), assertions, test grouping, data-driven testing	You can organise test scripts into suites with setup, teardown, and assertions
Page Object Model (POM)	Separating page structure from test logic; page classes	You can write maintainable test automation code that does not break on minor UI changes
Data-driven testing	Reading test data from Excel, CSV, or properties files	You can run the same test with multiple data sets
Handling dynamic elements	AJAX, iframes, alerts, multiple windows	You can automate pages that do not load all at once
Selenium Grid	Running tests in parallel across browsers and machines	You can reduce test execution time for large suites

Practice idea: Automate the test cases you wrote in Module 2 for the e-commerce search and checkout features. Build a Selenium project with TestNG, implement the Page Object Model, use explicit waits for dynamic content, and run at least five test cases with assertions. Then parameterise one test with data from a CSV file to test multiple search terms. This project connects manual testing thinking to automation implementation.

For detailed Selenium tutorials and examples, see the Selenium topics on Scaler Topics. For the official framework reference, the Selenium documentation is authoritative.

Module 4: API Testing (Postman and REST)

API testing is increasingly where QA teams spend their time, because modern applications are built on APIs first and UIs second. If the API is broken, the UI will be broken regardless of how it looks. Testing at the API layer catches defects earlier, runs faster, and is cheaper to automate than UI testing.

Topic	What You Learn	Outcome
REST API fundamentals	HTTP methods (GET, POST, PUT, DELETE), status codes, headers, request/response structure	You understand how APIs communicate
JSON and XML	Reading and validating response bodies in JSON and XML	You can extract and verify data from API responses
Postman basics	Creating collections, sending requests, setting headers and body	You can manually test any REST API
Assertions in Postman	Writing test scripts using pm.expect; validating status codes, response body, headers	You can automate API validation in Postman
Environment variables	Setting up dev/staging/production environments; dynamic data passing between requests	You can run the same tests across multiple environments
Data-driven API testing	Running collections with CSV or JSON data files	You can test APIs with many input combinations efficiently
Authentication testing	Bearer tokens, API keys, OAuth basics	You can test authenticated API endpoints
API automation with Newman	Running Postman collections from the command line; integrating with CI	You can automate API test execution in pipelines

Practice idea: Use a free public API (such as Reqres.in or JsonPlaceholder) and build a Postman collection that tests a full CRUD workflow: create a resource (POST), read it (GET), update it (PUT), and delete it (DELETE). Add assertions for status codes, response body fields, and response time. Then run the collection with Newman from the command line. This exercise covers every major API testing concept in one flow.

For SQL skills that complement API testing (validating database state after API calls), see the SQL tutorials on Scaler Topics. 

For the official API testing reference, the Postman API testing documentation covers the platform in depth.

Module 5: CI/CD, Performance and Agile Testing

The final module covers how testing fits into the development pipeline and how to test for performance. These topics separate testers who can find bugs from testers who can prevent bugs from reaching production.

Topic	What You Learn	Outcome
CI/CD fundamentals	Continuous integration, continuous delivery, deployment pipelines	You understand how code moves from commit to production
Testing in CI/CD pipelines	Triggering automation suites on every commit; test stage gates	You can integrate Selenium and API tests into a pipeline
Jenkins basics	Creating jobs, configuring builds, scheduling test runs	You can set up a basic CI server that runs tests automatically
Performance testing concepts	Load testing, stress testing, endurance testing, spike testing	You understand the types of performance testing and when each applies
Introduction to JMeter	Creating test plans, configuring thread groups, adding listeners	You can run a basic load test on a web application
Agile testing	Testing in sprints, shift-left testing, tester role in scrum	You can work effectively in an agile team where testing is continuous
Test strategy in agile	Risk-based testing, test automation pyramid, defining done criteria	You can plan testing that keeps pace with rapid development cycles

Practice idea: Set up a simple Jenkins pipeline (or use GitHub Actions if Jenkins is unavailable) that pulls a Selenium test project from a repository and runs the test suite on every commit. Add a JMeter test plan that sends 100 concurrent requests to a test API and measures response time. This exercise connects automation testing to the pipeline, which is how testing works in real organisations.

For structured learning that covers CI/CD and DevOps practices alongside testing, explore Scaler’s free courses.

Tools, Certifications and Your Learning Path

Core Tool Stack by Module

Module	Key Tools	What They Do
Testing Foundations	Test management tools (JIRA, TestRail)	Track test cases, defects, and testing progress
Manual Testing	Browser DevTools, JIRA, spreadsheets	Inspect elements, report bugs, track test execution
Automation Testing	Selenium WebDriver, TestNG, Maven/Gradle, Eclipse/IntelliJ	Write and run automated web tests
API Testing	Postman, Newman, REST Assured	Test and automate API validation
CI/CD and Performance	Jenkins/GitHub Actions, JMeter, Git	Automate test execution and measure performance

ISTQB Certification

The ISTQB Certified Tester Foundation Level (CTFL) is the most widely recognised testing certification globally. It validates the concepts covered in Modules 1 and 2 of this syllabus. The exam costs approximately 4,000-5,000 INR in India and covers testing fundamentals, test design techniques, test management, and tool support.

Is it necessary? Not strictly. Most employers care more about practical testing skills than a certificate. But for freshers and career switchers with no QA experience, ISTQB Foundation provides a structured study path and a credential that gets your resume past initial filters. If you are going to invest in a certification, this is the one to start with.

How to Sequence Your Learning

The correct order is the order of this syllabus: foundations first, then manual testing, then automation, then API testing, then CI/CD. There are no shortcuts. Attempting Selenium without understanding test design produces scripts that run but do not test anything meaningful. Attempting API testing without understanding HTTP and JSON produces requests that return responses you cannot interpret.

A realistic timeline:

Pace	Time to Complete All 5 Modules
Full-time (30-40 hours/week)	8-12 weeks
Part-time (10-15 hours/week)	16-24 weeks
Weekend-only (6-8 hours/week)	24-36 weeks

• Modules 1 and 2 together take roughly 2-4 weeks for most learners.
• Module 3 (Selenium) is the longest module and takes 4-8 weeks depending on your coding comfort. 
• Module 4 (API testing) takes 2-3 weeks. 
• Module 5 takes 2-4 weeks.

For a structured programme that takes you from testing fundamentals through automation and into career-ready SDET skills, explore Scaler Academy.

For the cost of various testing programmes, see the software testing course fees guide and the automation testing course fees guide.

FAQs

1. What is the syllabus for software testing?

The software testing syllabus is structured in five modules: testing foundations (SDLC, STLC, test design techniques, defect lifecycle), manual testing (functional, regression, exploratory, bug tracking with JIRA), automation testing with Selenium (WebDriver, locators, TestNG, Page Object Model), API testing with Postman (REST fundamentals, assertions, data-driven testing, Newman), and CI/CD plus performance testing (Jenkins, JMeter, agile testing). Each module builds on the previous one, so follow them in order.

2. Should I learn manual or automation testing first?

Manual testing first, always. Automation without testing fundamentals produces scripts that run but do not test anything meaningful. You need to understand test design, defect identification, and critical thinking about quality before you can automate effectively. Manual testing teaches you what to test. Automation teaches you how to test it faster. The first skill is the foundation for the second. Spend 3-4 weeks on Modules 1 and 2 before touching Selenium.

3. Do I need coding for software testing?

Manual testing does not require coding. You can write test cases, report bugs, and perform exploratory testing without writing a single line of code. But automation testing absolutely requires coding. Selenium tests are written in Java, Python, or C#. API automation uses JavaScript or Java with Postman scripts. If you want to move beyond manual QA into SDET or automation engineer roles, learning to code is non-negotiable. Java or Python are the best starting languages for test automation.

4. How long does it take to complete a software testing course?

For a complete beginner studying part-time (10-15 hours per week), the full syllabus (manual plus automation plus API testing plus CI/CD) takes approximately 16-24 weeks. If you only want manual testing (Modules 1 and 2), 3-6 weeks is realistic. If you already know Java or Python and want to focus on Selenium and API automation, 8-12 weeks is reasonable. Full-time learners can complete the entire syllabus in 8-12 weeks.

5. Is ISTQB certification necessary?

Not strictly, but it helps freshers and career switchers. The ISTQB Foundation Level validates the concepts in Modules 1 and 2 and is recognised by most employers globally. It costs approximately 4,000-5,000 INR in India. For experienced testers with a portfolio of automation projects, ISTQB adds less marginal value. If you have no QA experience and need a credential to get your resume noticed, ISTQB Foundation is worth the investment. If you already have practical testing experience, your time is better spent building automation projects.