Software Testing Training: End To End Training On A Live Project – Free Online QA Training Part 1

Free Software Testing Training On A Real-Time Live Project:

Exciting news! We are thrilled to announce the next installment of our comprehensive Quality Assurance training series. In this training, we will simulate an entire software project, covering each phase in detail. Our focus will be on the QA training processes, phases, roles & responsibilities, and deliverables.

In short, get ready for a condensed online course in Software Testing.

---

Important note: The following free tutorials serve as a solid starting point, but for the best online LIVE Software Testing training course, conducted by industry experts, please visit this page.

---

=> Below is the list of all tutorials in this free Live Project QA training series:

• Day 1: Introduction to the Live Project
• Day 2: Reviewing the SRS Document and Creating Test Scenarios
• Day 3: Writing a Test Plan Document from Scratch
• Day 4: Creating Test Cases from the SRS Document
• Day 5: Test Execution
• Day 6: Bug Tracking, Test Metrics, and Test Sign-off

---

Why This Free QA Training?

We receive numerous inquiries from our readers requesting insight into the actual Software Testing process followed by QA teams. To address this demand, we have decided to document a complete Software Testing Life Cycle (STLC) using a real-life application that is available for testing on the Internet.

This live project will serve as the foundation for our Software Testing Training series. We strongly encourage you to closely follow this series as it provides a crash course in implementing testing practices on a live application.

Software Testing Training On a Live Project – What Is It?

Before we dive into further details, let’s take a moment to explain what this Software Testing course series entails and how it will progress.

We have selected a live application:

• We begin with a review of the SRS document
• Then, we move on to writing test scenarios based on the SRS document
• We proceed with creating a test plan from scratch
• Next, we cover the process of designing test cases
• Identifying test data
• Executing tests
• Managing defects
• Reporting test statuses
• Collecting metrics

• Essentially, we cover every aspect of a real-time Software Testing project, providing examples, artifacts, and deliverables along the way.

How to Follow This Software Testing Course Series?

Step #1) Introduction and SRS Walkthrough – We start this mini software testing course with a walkthrough of the SRS document. We have created and shared a sample SRS document. Take the time to go through it, as your understanding of this application will be crucial for the subsequent steps.

Step #2) SRS Review and Test Scenario Preparation

Step #3) Test Plan – Complete the process of creating a test plan from scratch. We will share the final version of the test plan for your reference.

Step #4) Test Cases – Complete the process of writing test cases, with sample test cases provided. You can use a test management tool or a spreadsheet for this task.

Step #5) Application Walkthrough and Test Execution – Learn how to execute test cases and record test results.

Step #6) Defect Reporting

Step #7) Defect Verification and Regression Testing

Step #8) QA Sign-off

The aim is to provide you with a real-time project experience and expertise. We hope you find this series valuable.

Application That We Are Going to Use

Introduction

Client: Orange
Application: OrangeHRM demo
Service Provider: SoftwareTestingHelp.com

Project Description

Orange intends to develop a commercial human resources management product that can be customized and utilized by medium-sized businesses, both nationally and globally.

The product has two versions: Professional and Enterprise.

Included Features

• Personal Information Management
• Advanced Leave Management
• Time & Attendance Tracking
• Employee Performance Management
• Recruitment
• Advanced Reporting
• Country/Location-Based Employee Management
• Localized Leave Rules
• Configurable Workflows
• Platinum Support
• Country/Location-Based Reporting
• Custom Reporting

Note: For simplicity and to focus on a specific area, we will consider the employee module of this HRM portal, where users can enter their personal information.

When a customer or business owner needs to enter the online world or make updates to an existing site or application, they encounter a business problem. Software is then developed to solve this problem.

Customers approach software service providers to bring their software ideas to life. This is where the software project begins.

A traditional Waterfall Project (SDLC) follows the following phases:

• As testers, we know that testing is not limited to just phase 5, “Testing”. We play a significant role throughout the entire process.
• Testing is a reactive job. We cannot test anything without code or an application to test. To be prepared and react efficiently, we strive to plan and prepare ahead of time. Therefore, our activities begin well before phase 5.

In summary, here’s what happens in each phase:

Initiate:

Once the producer and the customer agree to terms, software production begins.

• In this phase, business requirements are gathered and analyzed. This analysis involves decisions on technological considerations, hardware and software specifications, resources, effort, time, relevance, and improvements, among others.
• Business analysts, project managers, and client representatives are involved.
• At the end of this phase, the project plan is prepared.
• Project-specific documents, such as a scope document or business requirements document, are created.
• QA involvement is typically not expected at this stage, although involving QA from the beginning is ideal for identifying early issues in development phases.

Define:

The finalized business requirements serve as inputs for this step.

• This phase involves translating business requirements into functional requirements for the software. For example, if the business requirement is to allow users to make purchases on a website, the functional requirement will include details such as the site’s layout, menu options, product search, shopping cart, checkout process, payment options, and confirmation of sale.
• Developers, business analysts, and project managers are involved.
• The output of this phase is a detailed document containing the software’s functional requirements. This document goes by various names, such as Software Requirement Specification (SRS), Functional Requirements Document (FRD), or Functional Requirements Specification (FRS).
• This is when the QA team gets involved, after the completion of the SRS documentation.
• While finalizing the functional requirements and documenting the SRS, the QA manager/lead prepares an initial version of the Test Plan and assembles a QA team.
• The QA team becomes actively involved once the SRS document is complete.
• At this stage, either the development team, business analyst, or QA team lead will conduct a SRS walkthrough with the QA team.
• For new projects, a comprehensive walkthrough in the form of a conference or meeting yields the best results.
• For subsequent releases of an existing project, the SRS document is sent to the QA team via email or placed in a shared repository. The QA team reviews the document offline and gains a thorough understanding of the system.
• Since the primary audience for the SRS document isn’t exclusively testers, not all of its content is relevant to us. As testers, we must carefully review the document to determine which parts are useful.

SRS Document for This Live Project

We have attached a sample SRS document to give you an idea of its content, format, and structure. In the next article, we will explore how the QA team utilizes this document to proceed with our testing projects.

==> Download the Sample SRS Document for the Live Project.

Conclusion

In this article, we have introduced the Software Development and Testing process and shared a sample SRS document for the project we will be testing.

=> The next article in this software testing training series will focus on Reviewing the SRS Document and Creating Test Scenarios.

Note: While we prepare the next article in this QA training series, we encourage you to work alongside us here for the most immersive experience. Familiarize yourself with the SRS document, and when we reconvene, we will continue with the next steps.

Happy Testing until then!

About the Author: This live project QA training series is being presented by Swati Seela, a member of the STH team.