Software Testing Course Syllabus

This module explores the diverse approaches used in professional software development. You will analyse the Software Development Life Cycle (SDLC) and break down specific methodologies, including the Iterative, Waterfall, V-Model and Agile models. The module also examines the role of DevOps and CI/CD practices in improving software quality and reducing cycle time. Finally, you will explore the Shift-Left concept, focusing on the strategic move of testing activities to earlier stages of the SDLC.

Key Learning Outcomes

By the end of this module, you will be able to:

• Map the core stages of the Software Development Life Cycle (SDLC).

• Differentiate between key development methodologies, such as Waterfall, V-Model and Agile.

• Evaluate the role of DevOps and CI/CD in modern software quality and delivery speed.

• Examine the concept of “Shift-Left” to move testing activities to earlier development phases.

• Assess the benefits and drawbacks of various methodologies to make informed decisions based on project constraints.

This module focuses on the key concepts and principles of Agile methodology, specifically exploring the Scrum and Kanban frameworks. You will analyse the core components of Scrum, including sprints, ceremonies, roles and artefacts, while comparing it to Kanban’s emphasis on continuous delivery and flow. The curriculum also examines the use of User Stories for capturing requirements and the critical roles of Test-Driven Development (TDD) and Behaviour-Driven Development (BDD) in delivering high-quality, user-focused software.

Key Learning Outcomes

By the end of this module, you will be able to:

• Navigate the Scrum framework, identifying the purpose of specific sprints, roles and ceremonies.

• Differentiate between Scrum and Kanban methodologies based on delivery flow and structure.

• Construct User Stories as a primary method for capturing requirements and communicating with stakeholders.

• Evaluate the impact of TDD and BDD on software quality and alignment with user expectations.

• Apply Agile principles to software development projects to ensure high-quality, iterative delivery.

This module covers the widely used testing standards that define best practices in global software development. You will investigate the core Test Standards that serve as essential guidelines for quality assurance, with a walkthrough of internationally recognised ISO Testing Standards.

Key Learning Outcomes

By the end of this module, you will be able to:

• Identify and interpret the professional guidelines that outline best practices for software testing.

• Navigate internationally recognised ISO standards.

• Evaluate the significance of standardised testing in ensuring software reliability and quality.

• Apply these global testing standards to your own QA activities to maintain industry compliance.

• Contribute to the development of high-quality software by adhering to recognised international frameworks.

This module transitions into the core execution of software testing by mastering the Software Testing Life Cycle (STLC). You will analyse each stage of the process, from initial test planning and design to execution and closure. The curriculum also examines the critical differences between Verification and Validation and how Software Requirements serve as the mandatory foundation for all testing activities. Finally, you will explore the practical application of Black Box, White Box and Grey Box testing techniques.

Key Learning Outcomes

By the end of this module, you will be able to:

• Map each stage of the Software Testing Life Cycle (STLC) from planning to closure.

• Differentiate between Verification and Validation and their respective roles in quality assurance.

• Analyse how Software Requirements dictate the foundation for test planning and execution.

• Apply specific testing techniques, including Black Box, White Box and Grey Box testing, to various software scenarios.

• Establish a technical foundation in testing fundamentals to prepare for advanced practical application as a software tester.

This module examines the various types of Requirements Specifications that serve as the blueprint for software development and testing. You will analyse the role of System, Functional, Non-Functional and Technical Requirements Specifications in defining project scope and guiding quality assurance activities. The curriculum also introduces Request for Change (RFC) documents, exploring how they are used to systematically track and manage software modifications throughout the development lifecycle.

Key Learning Outcomes

By the end of this module, you will be able to:

• Differentiate between System, Functional, Non-Functional and Technical Requirements Specifications.

• Analyse how specification documents serve as the primary guide for development and testing activities.

• Identify the purpose and structure of Request for Change (RFC) documents in tracking software modifications.

• Evaluate the importance of clear requirements in shaping the success of software projects.

• Implement change-management principles to ensure consistency during the development lifecycle.

This module examines the critical technical documents that define a software system’s architecture and implementation. You will analyse High-Level Design (HLD) and Low-Level Design (LLD) documents to understand how they provide both a structural overview and a detailed blueprint for a system. The curriculum also covers the full suite of Requirements Specifications, including System, Functional, Non-Functional and Technical documents, alongside the use of Request for Change (RFC) protocols to track modifications during development.

Key Learning Outcomes

By the end of this module, you will be able to:

• Differentiate between High-Level Design (HLD) and Low-Level Design (LLD) in software architecture.

• Analyse how design documents provide the transition from system overview to granular implementation.

• Categorise various Requirements Specifications (System, Functional, Non-Functional and Technical) and their role in guiding development.

• Identify the purpose of Request for Change (RFC) documents in maintaining version control and system integrity.

• Evaluate the contribution of professional technical documentation to the overall success of the software development lifecycle.

This module explores the end-to-end management of software testing activities, from strategic planning to final closure. You will learn to develop a comprehensive Test Plan and to translate complex requirements into actionable Test Scenarios and Test Cases. The curriculum covers the use of the Requirements Traceability Matrix (RTM) to verify coverage, alongside the management of Test Data and Test Environments. You will also master Test Estimation Techniques to project resource requirements before moving into the practical phases of Test Execution, Evidence Collection and Reporting.

Key Learning Outcomes

By the end of this module, you will be able to:

• Construct a comprehensive Test Plan that outlines a strategic approach to software quality.

• Translate technical requirements into detailed Test Scenarios and Test Cases for system validation.

• Utilise a Requirements Traceability Matrix (RTM) to track and verify full requirement coverage.

• Implement Test Estimation Techniques to accurately calculate required effort and resources.

• Execute software tests while systematically documenting Test Evidence and generating professional Test Reports.

• Manage the Test Closure process, ensuring all activities are concluded and documented to industry standards.

This module masters the professional discipline of identifying, documenting and managing software defects. You will define what constitutes a “defect” within a development context and learn the industry standards for accurate identification. A significant portion of this module is dedicated to the Defect Report, where you will learn to author formal documents that communicate technical issues to stakeholders. You will also categorise defects using Severity and Priority classifications and track their progression through the complete Defect Life Cycle, from initial discovery to final verification and closure.

Key Learning Outcomes

By the end of this module, you will be able to:

• Define and identify defects within the specific context of a software development project.

• Author professional Defect Reports that capture all essential elements required for clear developer communication.

• Categorise defects using industry-standard classifications for impact, severity, and priority.

• Map a defect’s progress through the Defect Life Cycle, managing its status from “New” to “Closed.”

This module provides a deep dive into the diverse range of testing types used to validate modern software. You will examine the purpose, implementation and unique challenges of several critical testing disciplines, including Unit, Integration and API Testing. The curriculum also covers high-level validation through System Testing, User Acceptance Testing (UAT) and End-to-End Testing, alongside the continuous verification provided by Regression and Exploratory Testing. By analysing the benefits and difficulties associated with each, you will learn to strategically select the most effective testing type for any project scenario.

Key Learning Outcomes

By the end of this module, you will be able to:

• Differentiate between the various levels of the testing pyramid, from granular Unit Testing to high-level System Testing.

• Execute specialised testing types, including integration testing, to verify communication between software components.

• Implement Regression Testing protocols to ensure new code changes do not negatively impact existing functionality.

• Navigate the User Acceptance Testing (UAT) process to ensure software meets the final needs of the end-user.

• Evaluate the advantages and constraints of Exploratory Testing versus scripted End-to-End Testing.

• Select and conduct the appropriate testing types based on specific software project requirements and technical constraints.

This module explores Non-Functional Testing, focusing on the operational attributes that determine a system’s performance, security and user experience. You will examine the significance of testing for “how” a system works rather than just “what” it does. The curriculum covers a comprehensive range of specialised disciplines, including Performance, Security and Usability Testing, alongside high-pressure evaluations like Stress and Scalability Testing. You will also analyse the requirements for Localisation, Compatibility and Reliability, as well as the fundamentals of Penetration (Pen) Testing.

Key Learning Outcomes

By the end of this module, you will be able to:

• Differentiate between Functional and Non-Functional testing requirements.

• Analyse the impact of Performance and Stress Testing on system stability under high-traffic conditions.

• Evaluate the importance of Security and Pen Testing in protecting software against external vulnerabilities.

• Navigate the complexities of Localisation and Compatibility Testing to ensure software functions across different regions and devices.

• Select the appropriate non-functional testing types based on project goals, identifying the specific benefits and challenges of each.

This final module transitions from theory to Hands-On Execution, where you will apply critical thinking and technical skills to real-world scenarios.  Using the professional standards established in previous modules, you will construct Test Cases and generate Detailed Bug Reports based on your direct observations. This module serves as the final validation of your ability to contribute to the software testing process and improve the overall quality of digital products.

Key Learning Outcomes

By the end of this module, you will be able to:

• Audit live test sites to identify technical vulnerabilities, functional bugs and usability issues.

• Construct professional, execution-ready Test Cases that validate specific user requirements.

• Generate high-quality Bug Reports that include reproduction steps, severity levels and expected results.

• Apply critical thinking to prioritise testing activities based on site observations and findings.

• Validate the overall quality of a software product through a systematic, evidence-based testing approach.