SOFTWARE TESTING MASTERCLASS-2025-JIRA | AGILE | API Testing

Define a bug as the actual result not matching the expected result per the SRS. Detect defects through requirements, noting login gating, wrong behavior, or features not in the SRS.

Explore the end-to-end bug life cycle, from reporting in tools to open, assigned, fixed, verified, reopened, and closed, including roles tester, lead, developer, and the use of comments.

The lecture explains the four levels of testing—unit, integration, system, and acceptance—covering who performs each level from developers' unit tests to client acceptance.

Perform functional testing, GUI testing, and usability testing to ensure an application functions correctly, displays accurate look and feel, and remains easy to use.

Explore how compatibility testing verifies the app's behavior with other software, browsers, and operating systems, and how configuration testing checks the app's behavior with diverse hardware.

Learn how testers handle a bug by replicating the issue with the same steps, then report it in a bug tracking tool like Jira, after checking for existing reports.

Set up a Jira account for practice, sign up with a unique email and verify it, then create a scrum project for bug reporting during a seven-day trial.

Learn how to report a defect in Jira by creating a new defect, filling the summary and description, adding steps to reproduce, attaching evidence, and assigning to the dev lead.

Set bug priority and severity by assessing impact on business and application. Recognize login blocking as high priority and high severity, while spelling errors are high priority but low severity.

Learn how to perform smoke testing to verify a build’s major functionalities and readiness for testing, and use sanity testing (not scripted) to verify a focused functionality after changes.

Learn how to define and format test cases by outlining login scenarios, including correct and incorrect credentials and blank fields, and follow the requirements-to-execution workflow from SRS to test execution.

Master the standard test case format, description, preconditions, steps, test data, expected and actual results, and status, and learn to write in Excel or via Jira and other tools.

Learn how to assign unique ids to test cases, populate each column with data, and include module names to ensure clear traceability and consistent id formats across the project.

Define what exactly to test in each test case with a concise best guess description. Use ATM withdrawal and admin login examples to illustrate clear, test-focused descriptions.

Identify and document preconditions or prerequisites for each test case, including data, dependencies, and setup such as clearing cookies, login requirements, or database connections, to ensure accurate results.

Define each test case with clearly defined serial steps from home page navigation to checkout, using exact button and element names and including steps to reproduce.

Define test data for each test case, recognizing that data can change expected behavior in searches, logins, and registrations, and optionally use data references or Excel sheets for sensitive data.

Explain how to define the expected result in each test case, emphasize its role as a mandatory column, and illustrate per-step expectations with a login example.

Learn how to track test cases from execution to status by comparing actual results with expected results, marking pass, fail, blocked, or not executed, and documenting reasons.

Explain how to use the test case comments column to document execution results, reasons for failures or blocks, and to inform defect reporting.

This lecture demonstrates using a non-mandatory priority column to tag test cases as high, medium, or low, enabling focused testing under tight deadlines and protecting major functionalities.

Add an optional type column to test cases to classify them as functional, usability, or other testing. This supports filtering, prioritizing, and assigning tests by type.

learn to report defects with a bug id, link test cases to bugs in Jira or other tracking tools, and note the id in a dedicated column for traceability.

Use the experience based technique, or little guessing, to extend test cases with prior testing experience. Increase tests only if effectiveness rises; reduce them if effectiveness remains unchanged, saving resources.

Learn boundary value analysis for testing a functionality with a range of values by identifying positive and negative boundaries using four key values to reduce test cases while maintaining effectiveness.

Explore equivalence class partitioning (ECP) to group inputs that produce the same output, reducing test cases without compromising testing effectiveness. Apply ECP to input ranges and data types with examples.

Understand how performance testing differs from functional testing by evaluating an app under varying user loads to measure response time, memory usage, network status, and non functional results.

Master load, stress, endurance, spike, and volume performance testing to understand how user load and database interactions affect response times and stability.

Understand the difference between use cases and test scenarios, and how client requirements shape testing.

Explore how agile scrum converts client requirements into user stories, builds product and sprint backlogs, and guides work through sprint planning, daily scrums, reviews, and retrospectives.

Identify the three types of mobile apps—native, web, and hybrid—and note that native apps install on devices, web apps run in mobile browsers, and hybrids blend native and web.

Learn how to install native or hybrid iOS apps for testing, from the App Store or via TestFlight invites, and understand the download, installation, and pre-release testing workflow.

Set up a free Jira trial for hands-on practice, create a Scrum project named File Management System, invite teammates, and learn end-to-end bug reporting and agile task management.

Learn to report a new defect in Jira by capturing a screenshot, writing a clear summary, detailing steps to reproduce, attaching evidence, and assigning the issue for resolution.

Learn how to report a defect in Jira, assign it to a developer, and link team members to track, ask questions, and escalate issues via email.

Learn how to define and assign components in Jira defects, using modules like registration, log-in, and e-mail, and filter defects by component to track issues efficiently.

Set a default Jira dashboard to show all defects and issues assigned to you, including sprint-ready views.

Configure a Jira bug workflow by editing the workflow and assigning open, in progress, closed, and reopen statuses to defects, then publish changes to enable end-to-end defect lifecycle.

Learn the end-to-end bug life cycle for a valid defect: report, assign to a developer, fix, verify, and close. See testers and developers collaborate across open, in-progress, and resolved states.

Understand the end-to-end bug life cycle for an invalid defect: a tester reports it, a developer rejects with a reason, then reassigns, attaches notes, and closes per requirements.

Learn the end-to-end life cycle of a valid defect rejected by a developer, including reopening, reassigning, and final verification before closure.

Learn to search defects in GTA using basic and advanced search, then apply gun (Jira query language) to locate issues by id, or by text in summary and description.

Explore Jira's issues and filters to locate defects by assigned and status, then use dashboards to apply open issues, reported by me, all issues, viewed recently, created recently, updated recently.

Explore advanced search in Jira to build multi-criteria queries across issues, filters, and columns by type, status, priority, component, label, and assignee for efficient defect tracking.