Week 1-2: (CORE)

Clock Hours: 24 hours theory, 0 hours Lab

• • Fundamentals of Software Quality
  • Definition and importance of software quality
  • Quality assurance vs. quality control
  • Software development life cycle (SDLC)
  • Software Testing Life Cycle (STLC)
    • Phases of STLC (requirement analysis, test planning, test case development, environment setup, test execution, test cycle closure)
    • Entry and exit criteria for each phase
    • Deliverables and documentation in STLC
    • Role of a software quality engineer

Week 3-4: (CORE)

Clock Hours: 24 hours theory, 0 hours lab

• •   Testing Fundamentals
  • Types of testing (unit, integration, system, acceptance)
  • Black-box vs. white-box testing
  • Static vs. dynamic testing
  • Test case design techniques
  •  hours lab

Week 5-8: (CORE)

Clock Hours: 20 hours theory, 10 hours lab

• • Agile and Scrum Fundamentals
  • Agie methodologies (Scrum, Kanban)
  • Role of QA in Agile teams
  • Scrum ceremonies (sprint planning, daily stand-ups, sprint reviews, retrospectives)
  • Writing user stories and managing product backlogs
  • Role and responsibilities of a Scrum Master
  • Facilitating Scrum ceremonies
  • Coaching Agile teams
  • Preparing for Scrum Master certification exams

Week 9-13: (CORE)

Clock Hours: 24 hours theory, 24 hours lab 

• • Business Analysis Fundamentals
  • Role of a business analyst in software projects
  • Requirements gathering and documentation
  • Use case and user story development
  • Stakeholder communication and management
  • Preparing for ISTQB Business Analyst certification exams

Week 14-17: (CORE)

Clock Hours: 16 hours theory, 24 hours lab

• • Azure DevOps Basics
  • Introduction to Azure DevOps
  • Setting up Azure Boards for Scrum
  • Managing sprints and backlogs
  • Continuous integration and delivery (CI/CD) with Azure Pipelines

Week 18-20: (CORE)

Clock Hours: 16 hours theory, 8 hours lab

• • Quality Management and Metrics
  • Key quality metrics (e.g., defect density, test coverage)
  • Reporting and documentation
  • Root cause analysis
  • Using metrics to drive improvements

Week 21-24: (CORE)

Clock Hours: 24 hours theory, 20 hours lab

• • Manual Testing Basics
  • Writing and executing test cases
  • Defect lifecycle and management
  • Tools for manual testing (e.g., JIRA, ALM)
  • Defect and Reporting
    • Defect identification and classification
    • Defect tracking and lifecycle
    • Reporting defects using JIRA and ALM
    • Generating and analyzing defect reports
  • Test Case Management Tools
    • Introduction to test case management tools (e.g., TestRail, Zephyr, Qmetry)
    • Creating and managing test cases
    • Linking test cases to requirements and defects
    • Test execution and reportin
    • Preparing for ISTQB Foundation Level Tester certification exams

Week 25-28: (CORE)

Clock Hours: 16 hours theory, 24 hours lab

• • JIRA and QMetry Integration 
  • Introduction to JIRA and ALM
  • Setting up and managing projects in JIRA
  • Integrating JIRA with ALM for defect tracking and test management
  • Integrating JIRA with Qmetry
    • Introduction to Qmetry
    • Configuring JIRA with QMetry using credentials or Open API key
    • Real-time synchronization of user stories between JIRA and QMetry
    • Managing test cases, executions, and defects with QMetry in JIRA
  • Best practices for using JIRA/ALM in software quality assurance

Week 29-32: (CORE)

Clock Hours: 24 hours theory, 16 hours lab

• • Java Basics
  • Introduction to Java
  • Object-oriented programming concepts
  • Writing and debugging Java code
  • Java for test automation

Week 33-36: (CORE)

Clock Hours: 16 hours theory, 30 hours lab

• • Selenium Basics
  • Introduction to Selenium WebDriver
  • Setting up Selenium with Java
  • Writing and executing Selenium test scripts
  • Advanced Selenium features (e.g., handling alerts, frames, and windows)
  • Maven, GIT, and Jenkins
    • Introduction to Maven for project management and build automation
    • Using GIT for version control
    • Setting up and configuring Jenkins for continuous integration and continuous delivery (CI/CD)
    • Integrating Selenium with Maven, GIT, and Jenkins for automated testing pipelines

Week 37-40: (CORE)

Clock Hours: 16 hours theory, 24 hours lab

• • SQL Server Basics
  • Introduction to SQL Server
  • Database design and normalization
  • SQL Server set up and configuration
  • Writing SQL queries
  • Database testing and validation

Week 41-44: (CORE)

Clock Hours: 16 hours theory, 24 hours lab

• • Performance Testing Concepts
  • Load testing, stress testing, and scalability testing
  • Tools for performance testing (e.g., JMeter, HP LoadRunner)
  • Analyzing performance test results
  • Performance tuning and optimization

Elective Modules (120 hours) – Select any 3 courses

Module 13: Mobile Testing (40 hours)

• Week 45-49: Mobile Testing Fundamentals
  • Clock Hours: 16 hours theory, 24 hours lab
  • Introduction to mobile testing
  • Tools for mobile testing (e.g., Android Studio, Katalon, Perfecto)
  • Writing and executing mobile test cases
  • Testing on real devices and emulators

Module 14: API Testing (40 hours)

• Week 50-54: API Testing Concepts
  • Clock Hours: 16 hours theory, 24 hours lab
  • Introduction to API testing
  • Tools for API testing (e.g., Postman, SoapUI, Karate)
  • Writing and executing API test cases
  • Validating API responses and performance

Module 15: Power BI (40 hours)

• Week 55-58: Power BI Fundamentals
  • Clock Hours: 16 hours theory, 24 hours lab
  • Introduction to Power BI
  • Data visualization principles
  • Creating and sharing reports
  • Integrating Power BI with other tools

Module 16: Agile Scrum Certification (40 hours)

• Week 59-63: Scrum Master Certification Preparation
  • Clock Hours: 16 hours theory, 24 hours lab
  • Role and responsibilities of a Scrum Master
  • Facilitating Scrum ceremonies
  • Coaching Agile teams
  • Preparing for Scrum Master certification exams

Module 16: Project Management (40 hours)

• Week 64-67: Project Management Fundamentals
  • Clock Hours: 24 hours theory, 16 hours lab
  • Introduction to project management
  • Project planning and scheduling
  • Risk management
  • Resource allocation
  • Monitoring and controlling projects
  • Project management tools (e.g., MS Project, Trello)

Module 17: AWS Cloud Solution Architect (40 hours)

• Week 68-72: AWS Cloud Solution Architect
  • Clock Hours: 20 hours theory, 20 hours lab

• • Understanding the fundamentals of cloud computing and the AWS ecosystem
  • Overview of AWS services and their applications.
  • Principles of designing resilient, high-performing, secure, and cost-optimized architectures.
  • In-depth exploration of key AWS services such as EC2, S3, RDS, Lambda, and VPC.
  • Strategies for cost optimization and management on AWS.
  • Learn to design secure, scalable, and cost-effective cloud architectures.
  • Develop the ability to design and implement AWS solutions.

Module 18: Capstone Project (40 hours)

• Week 73-76: Practical Application
  • Clock Hours: 10 hours theory, 30 hours lab
  • Real-world project simulation
  • Applying learned concepts to a project
  • Collaboration and teamwork
  • Final presentation and evaluation