Demonstration: 4 Hours
Lab: 0 Hours
Total: 4 Hours

Manual Testing Modules:

• Software Development Life Cycle
• Testing Methodologies (Waterfall, RUP Iterative, Agile)
• Different Testing Types: System, Black Box, End-to-end, Integration, Beta, GUI, Load, Performance, Stress, Volume, Endurance, Regression, Smoke, Ad hoc, Functional, Positive, Negative, Usability, 508 Compliance, User Acceptance Testing
• Testing Methodology / QA Process
• Business Requirement Document (BRD)
• System Requirement Specification (SRS)
• Design Documents (DD)
• Design Mockup/ Wire frame/Prototype
• Requirement Assessment/Validation
• Documents: Test Strategy, Test Plan, PMP, CMP, SDP, RAR, TAR, LOE, Executive Summary, Test Cases, Test Scenarios etc.
• Manual Testing vs. Automation
• Risk Analysis
• IV & V
• Use Cases
• Requirement Traceability Matrix (RTM)
• Test Matrix
• Interview questions and answers discussion
• Written test
• Oral presentation test

System Development Life Cycle (SDLC):

• Understanding concept of Business Modeling Requirement Gathering Analysis
• Design
• Implementation
• Testing
• Deployment

Software Development Standards

• Waterfall Method
• Spiral Model
• Rational Unified Process (RUP)
• Concepts of the RUP
• What is Iterative Development?
• Why Develop Iteratively? B
• Benefits of an Iterative Approach
• Mitigating risks
• Accommodating changes
• Reaching higher quality
• Learning and improving
• Increasing reuse
• Develop iteratively
• Manage requirements
• Model visually
• Use component-based architectures
• Continuously verify quality
• Manage changes
• RAD methodology
• Object oriented analysis and design (OOAD)
• AGILE, XP Methodology
• Synchronize & Stabilize Methodology
• Prototype Model
• Comparison between Waterfall & RUP
• Artifacts Delivered at Each Phase of RU

SOX compliance:

Industry basics: health, mortgage, finance, insurance, pharmacy, and their compliance needs.

Six sigma

CMMI

Interview questions and answers discussion

Written test

Oral presentation test

• Project schedules
• Scope document
• Business Requirements
• Architecture diagrams
• Process maps
• Technical Requirements
• UML diagrams and Notation (Use case, State Transition, Collaboration, Deployment,Package, Class, Activity, Sequence diagrams)
• Use cases and Collaboration Case description
• Supplemental specifications (Screen, Report, Interface mockups and Screen flow diagrams)
• Report and interface requirements
• Application Contingency Plan
• Security management plan
• Business Recovery Plan
• Test plans and Test cases
• Traceability matrices
• Interview questions and answers discussion
• Written test
• Oral presentation test

• Meetings and Ceremonies: Regular gatherings foster collaboration and alignment within AGILE teams.
• Sprint Planning: A detailed session outlining goals and tasks for the upcoming sprint cycle.
• Framework: a structured approach providing guidelines for Agile project management.
• Kanban A visual management tool for tracking work progress and flow within AGILE teams.
• JIRA Review: Utilization of JIRA software for project tracking, task management, and review in AGILE workflows.
• Different Tools: Various software and platforms facilitate AGILE project management and communication.
• Product backlogs: a prioritized list of features and tasks representing requirements for product development.
• Review Ceremonies: Regular meetings to evaluate completed work and gather feedback from stakeholders.
• Backlog grooming is the ongoing process of refining and prioritizing items in the product backlog.
• PBI/PPBM: Product Backlog Item/Product Backlog Management: Essential Elements in AGILE Product Development.
• Cross-Functional & Self-Organizing Team: Team structure promotes diverse skill sets and autonomy in decision-making within AGILE projects.

JIRA /ALM Tools:

• The module “JIRA – Project and Test Management Tool” is a crucial part of the course “Testing Automation with Java and Selenium.” This module introduces students to JIRA, a widely used project and test management tool in the software industry. Students will learn how to create and manage projects, tasks, and issues within JIRA, enabling effective collaboration and tracking of testing activities. They will also explore the integration of JIRA with test automation frameworks, allowing them to streamline their testing processes and enhance efficiency. Through hands-on exercises and practical examples, students will gain practical experience in utilizing JIRA for managing test cases, tracking defects, and generating reports. By the end of this module, students will have acquired the skills and knowledge necessary to leverage JIRA as a powerful tool for project and test management in their automation testing projects.

When it comes to bug tracking and reporting, here are some essential steps to follow:

1. Reproduce the Bug:

   • First, ensure you can consistently reproduce the issue. Identify the exact steps or conditions that trigger the bug.

2. Isolate the Issue:

   • Determine whether the bug is specific to a particular module, feature, or environment.
   • Check if it occurs on different browsers, devices, or operating systems.

3. Collect Relevant Information:

   • Gather details about the bug:
     • Description: Clearly explain what’s wrong.
     • Expected Behavior: Describe what should happen.
     • Actual Behavior: Explain what actually occurs.
     • Screenshots or Videos: Visual evidence helps.
     • Environment Details: OS, browser, version, etc.

4. Log the Bug:

   • Use a bug tracking tool (e.g., Jira, Trello, GitHub Issues) to create a new issue.
   • Include all relevant information from step 3.

5. Assign Priority and Severity:

   • Prioritize the bug based on its impact:
     • Priority: How urgently it needs fixing (e.g., high, medium, low).
     • Severity: How severely it affects users (e.g., critical, major, minor).

6. Assign to the Right Team Member:

   • Assign the bug to the appropriate developer or QA engineer.
   • Provide clear context and steps to reproduce.

7. Monitor Progress:

   • Regularly check the bug’s status.
   • Communicate with the assigned team member.

8. Regression Testing:

   • After the bug fix, verify that it’s resolved.
   • Perform regression testing to ensure other areas weren’t affected.

9. Close the Bug:

   • Once confirmed fixed, close the bug.
   • Add any relevant notes or comments.

The “Manual Testing Bootcamp” module is an essential part of the course “Testing Automation with Java and Selenium.” This module focuses on providing students with a comprehensive understanding of manual testing principles, techniques, and best practices. Students will learn the fundamental concepts of manual testing, including test planning, test case design, test execution, and defect reporting. They will explore various types of testing, such as functional testing, usability testing, and regression testing, and understand how to effectively apply them in different testing scenarios. Additionally, students will gain practical experience in performing manual testing by engaging in hands-on exercises and real-world examples. By the end of this module, students will have acquired the necessary skills and knowledge to conduct manual testing efficiently and effectively, laying a solid foundation for their automation testing journey with Java and Selenium.

The module “Back End Testing Tool: SQL, PL/SQL, and TOAD” is a crucial component of the course “Testing Automation with Java and Selenium.” This module focuses on equipping students with the necessary skills to perform back-end testing using SQL, PL/SQL, and TOAD. Students will learn how to write SQL queries to retrieve and manipulate data from databases, enabling them to validate the integrity and consistency of the data in the back end. They will also explore the advanced features of PL/SQL, which allow them to create stored procedures, functions, and triggers for testing and automation purposes. Additionally, students will become familiar with TOAD, a powerful database management tool, and learn how to leverage its functionalities to execute SQL queries, analyze query performance, and generate reports. By the end of this module, students will have a strong foundation in back-end testing techniques, enabling them to effectively validate the data and ensure the integrity of the application’s back-end systems using SQL, PL/SQL, and TOAD.

The module “Java Programming Essentials for Testing Automation” is a critical component of the course “Testing Automation with Java and Selenium.” This module focuses on equipping students with the fundamental concepts of Java programming necessary for automation testing. Students will learn the basics of Java syntax, data types, variables, control structures, and object-oriented programming principles. They will also explore essential concepts such as classes, objects, methods, inheritance, and polymorphism, which are crucial for building robust and maintainable automation test scripts. Through practical examples and coding exercises, students will gain hands-on experience in writing Java code for test automation scenarios using Selenium WebDriver. By the end of this module, students will have a solid understanding of Java programming essentials, enabling them to confidently write automation scripts and leverage the power of Java in their Selenium-based testing projects.

The module “Selenium Framework for Testing Automation” is a vital part of the course “Testing Automation with Java and Selenium.” This module focuses on introducing students to the Selenium framework, which is widely used for automating web application testing. Students will learn the key components of the Selenium framework, including Selenium WebDriver, Selenium Grid, and Selenium IDE. They will gain practical experience in automating test scenarios using Selenium WebDriver, which allows them to interact with web elements, perform actions, and validate expected outcomes. Additionally, students will explore techniques for handling different types of web elements, implementing synchronization, and managing browser configurations. Through hands-on exercises and real-world examples, students will develop proficiency in creating robust and maintainable automation test scripts using the Selenium framework. By the end of this module, students will be equipped with the necessary skills to utilize the Selenium framework effectively and efficiently in their Java-based automation testing projects.

Demonstration: 10 Hours
Lab Work: 18 Hour
Total Hours: 28 hours of hands-on practice sessions and real-time project base Lab work to be able to work in a real job.

Demonstration: 2 Hours
Lab: 2 Hour
Total: 4 Hours