Manual S/W Testing+JIRA+ Test Rail + Azure DevOps+Playwright

Understand how organizations, whether service or product based, define software testing to verify client requirements under controlled conditions and uncover defects through test cases, positive and negative scenarios, and scripts.

Discover the standard software testing hierarchy—from trainees to senior engineers—where a test manager and a test lead guide planning, standards, test cases, and bug tracking.

Identify the goals and responsibilities of software testers, including early bug detection, requirement understanding, query logging, test case creation, and bug reporting and tracking.

Differentiate need from requirement by clarifying a customer's high-level necessity and the detailed conditions that fulfill the business need, documented in the requirements document.

Define system software and application software, then explain generalized versus customized applications. Compare standalone, client-server, and web applications across two-tier and three-tier architectures.

Explore seven principles of software testing, including presence of defects, exhaustive testing is not possible, early testing, context-dependent testing, defect clustering, pesticide paradox, and absence of errors.

Learn about software testing techniques, including equivalence partitioning, boundary value analysis, error guessing, and decision tables, with practical examples and validation methods for black box testing.

Explore black box testing, white box testing, and grey box testing, focusing on external behavior, internal code structure, and partial knowledge to design test cases and validate functionality.

Explore the software development life cycle (SDLC) from requirement analysis to post-implementation, covering system and software requirements, design, coding, testing, implementation, and maintenance.

Explore the waterfall model, the simplest software life cycle, where requirements are gathered and frozen at the start and stages progress sequentially, though the process limits client interaction.

Explore the prototyping model with two methods: develop multiple prototypes for different requirements and integrate for testing, or develop and test prototypes before merging, then test and deploy to production.

Explore the spiral model, a risk-driven software development approach that repeats four phases—planning, risk analysis, engineering, and evaluation—combining prototype concepts with ongoing risk assessment.

Explore how the agile model combines iterative development and testing to deliver working software in short sprints, with backlog grooming, scrum roles, and continuous improvement.

Explore the software testing life cycle (STLC) from requirement analysis to test closure, detailing planning, designing, environment setup, execution, bug reporting, risk analysis, traceability, and sign-off.

Identify the two main levels of software testing - low level with unit and integration testing, and high level with functional, system, and acceptance testing, including alpha and beta acceptance testing.

Explore the full spectrum of system testing, from usability and security to regression, automated testing, and risk-based approaches, all performed by the testing team across environments.

Smoke testing runs end-to-end tests before detailed functional or regression testing to decide build acceptance; sanity testing after bug fixes or new features validates critical features with no test cases.

Explore alpha, beta, and gamma acceptance testing within the software testing process. Learn how user acceptance testing, defined acceptance criteria, and final-stage testing validate readiness for release and guide updates.

Compare regression testing and retesting: regression testing checks for unintended side effects on existing functionality, while retesting verifies fixes on failed test cases and confirms defect verification.

Explore integration testing approaches, including big bang and incremental methods. Learn top-down, bottom-up, and sandwich strategies, plus the use of drivers and stubs to simulate unavailable modules.

Compare two versions of a web page or app using A/B testing, bucket testing, or split testing to identify the best performing version and reduce bounce rate.

Understand performance testing as a non-functional assessment of system resilience to heavy load, fast responses, and crashes, and identify five types—load, stress, volume, longevity (endurance/soak), and spike testing.

Explore the scope of non-functional testing by examining reliability, security, usability, stability, performance, recovery, scalability, flexibility, reusability, portability, localization, internationalization, and compliance.

Discover web accessibility testing to ensure WCAG-compliant and usable experiences for users with disabilities. Explore keyboard navigation and screen reader checks, and examine tools like VoiceOver, NVDA, Jaws, and Wave.

Explore web testing fundamentals to verify bug-free, reliable web applications. Learn usability, user interface, security, compatibility, performance, and database testing.

Learn how verification uses static testing to confirm specifications and how validation uses dynamic testing to meet end-user requirements, via the V-model aligned with SDLC phases.

Understand the difference between quality assurance and quality control, distinguishing process-oriented QA from product-oriented QC, and clarify roles of testers, QA, and quality analysts.

Learn verification testing as static testing conducted before validation, and explore walkthrough, inspection, and review as verification methods for documents across the SDLC.

Explore authentication and authorization concepts and distinguish their roles in web security testing, showing how a verified identity may still lack permission to access specific resources.

Master backend testing concepts, ensuring data integrity from front end to back end and ACID compliance, with SQL basics like select, insert, update, delete, join, and group by.

Learn how to craft a test plan that defines scope, objectives, and scheduling, and guides risk analysis, testing strategy, and resources for manual and automated testing.

Define high level test scenarios that verify complete software functionality, using one-line descriptions to maintain coverage, align with the requirement ID, and track scenario and test case counts.

Explore positive and negative testing scenarios by analyzing happy path and valid input ranges, and identify invalid data cases that should be rejected, using date format validation as an example.

Learn to write test cases and document actions, inputs, expected and actual results, prerequisites, test data, and status; organize them with unique IDs and reference requirements, forming a test suite.

Understand the requirement traceability matrix, which maps requirements to test cases, ensuring complete coverage and tracking status with agile metrics like lead time, kanban, and burndown.

Produce a software testing status report that summarizes test activities and execution results, communicates health and progress to management, and informs release decisions when bugs or blocked tests arise.

Explain requirement documents and use case documents, detailing client high-level requirements and terms like FSD, SRT, SRS, FIS, and how use cases derive from requirements in BDD.

Clarify how error, defect, bug, and failure differ across development, testing, and post-release, and explain how syntax or coding errors become these issues.

Learn bug reporting using a bug management tool, capturing project, reporter, severity, priority, root cause, state, and assignee. Include steps to reproduce, expected vs actual, test data, and attachment.

Track the bug life cycle from creation to closure, covering reporting, open status, review, deferred, rejection, reopening, development, verification, and final resolution with subtypes like fixed or invalid.

Explore bug leakage, defect age, error seeding, showstopper bugs, bug release, and hot fixes, and learn prevention, measurement, and remediation in software testing.

Explore latent defect, mask defect, and defect cascading, and learn how hidden issues may go undetected until later operations trigger additional defects.

Differentiate bug severity and priority by impact on functionality and fix urgency; main page spelling is high priority, low severity, while crashes on critical features are high in both.

Apply the 80-20 rule in software testing by prioritizing core functionalities first, then secondary areas if time permits, noting that 80% of problems arise in 20% of modules.

Test closure marks the end of the testing phase, saving test cases, execution results, requirement traceability metrics, and testing reports; managers ensure bugs are fixed or acknowledged and records archived.

Identify and compile test deliverables, detailing suggested documents such as test strategy, test plan, test cases, test scripts, test data, reports, and release notes for client delivery.

Assess test coverage against requirements using traceability metrics, identify missing or extra test cases, and apply code coverage techniques like statement, decision, and branch coverage.

Understand build, patch, and update concepts in software delivery; a build is a testing package, a patch fixes bugs, and an update delivers a new version to remove drawbacks.

A proof of concept demonstrates that the idea is possible, supported by research and reviews, submitted as a package to stakeholders, fiscally sound, with applicability to automation testing if needed.

Navigate major challenges in software testing, including clear communication across onshore-offshore teams. Emphasize requirement understanding, proactive query logs, early testing, and regression-focused techniques to improve test coverage.

learn how to log effective bugs with complete reproduction steps, environment prerequisites, screenshots or videos, and clear details to help developers reproduce, prioritize, and fix issues quickly.

Demonstrates how to report a bug in Jira and Azure DevOps using a login form scenario, detailing steps to reproduce, expected vs actual results, and bug creation workflow.

Learn to craft high-level test scenarios and detailed test cases for the Gmail signup page, linking requirements to TS01 and TS02 with the standard test-case template.

Illustrates an end-to-end agile process from project initiation to go-live, highlighting product owner, testing teams, and daily scrums, planning poker, and UAT. Understand how builds, testing, and retrospectives deliver value.

Apply database testing with MySQL using SQL Workbench to verify UI data against database tables, practice schema-aware queries, updates, and counts, and confirm changes reflect on the web page.