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

Free Real-Time Live Project Training in Software Testing:

Great news! We are excited to present the next part of our all-encompassing series of Quality Assurance training. This training will mirror an entire software project, delving into each stage comprehensively. We will concentrate on the processes, stages, roles & responsibilities, and deliverables of QA training.

In essence, prepare for an intensive online course in Software Testing.

---

Key note: The following free lessons are a robust starting point, but for the premier LIVE Software Testing online training course, conducted by industry specialists, please check this page.

---

=> Down below is the list of all lessons in this free Live Project QA training series:

• Day 1: Introduction to the Live Project
• Day 2: Scrutinizing the SRS Document and Formulating Test Scenarios
• Day 3: Crafting a Test Plan Document from the Ground Up
• Day 4: Formulating Test Cases from the SRS Document
• Day 5: Test Execution
• Day 6: Bug Tracking, Test Metrics, and Test Sign-off

---

Why Opt for This Free QA Training?

We continually receive requests from our readers for insights into the actual Software Testing process carried out by QA teams. To cater to this demand, we will document a complete Software Testing Life Cycle (STLC) using a real-life application available for testing online.

This live project will serve as the fundamental base for our Software Testing Training series. We strongly suggest that you follow this series closely, as it offers an intensified crash course in applying testing practices on a live application.

Software Testing Training on a Live Project – What Exactly Is It?

Before we delve further into the details, let’s briefly explain the context of this Software Testing course series and its progression.

We have chosen a live application:

• We start with scrutinizing the SRS document
• Next, we shift our focus to devising test scenarios based on the SRS document
• We then proceed to craft a test plan from scratch
• Following that, we delve into the process of formulating test cases
• Identifying the test data
• Executing tests
• Tackling defects
• Reporting the status of tests
• Gathering metrics

• Basically, we cover every aspect of a real-time Software Testing project, presenting examples, artefacts, and deliverables along the way.

How Can You Follow This Software Testing Course Series?

Step #1) Introduction and Overview of SRS – We kick off this condensed software testing course with a comprehensive walkthrough of the SRS document. We have created and shared a sample SRS document. Ensure that you go through it in detail, as your comprehension of this application will be key for the subsequent phases.

Step #2) SRS Examination and Preparation of Test Scenarios

Step #3) Test Plan – Finalize the process of creating a comprehensive test plan from scratch. The final version of the test plan will be shared for your reference.

Step #4) Test Cases – Conclude the process of penning down test cases with provided sample test cases. This task can be done using a test management tool or a spreadsheet.

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

Step #6) Reporting Defects

Step #7) Verification of Defects and Regression Testing

Step #8) QA Approval

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

The Application That We Will Be Using

Introduction

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

Project Description

Orange aims to build a marketable human resources management product that can be customized and utilized by medium-sized businesses, nationwide and globally.

Two versions of the product are available: Professional and Enterprise.

Features Included

• Management of Personal Information
• Advanced Management of Leave
• Time & Attendance Monitoring
• Employee Performance Management
• Recruitment
• Advanced Reporting
• Management of Employees Based on Country/Location
• Localized Rules for Leave
• Workflows That Can Be Configured
• Platinum Support
• Reporting Based on Country/Location
• Custom Reporting

Note: For the sake of simplicity and focus, we will only consider the employee module of this HRM portal, where users can enter their personal information.

Whenever a customer or a business owner wants to enter the online world or needs to update an existing site or application, they encounter a business problem. To address this problem, software is developed.

Customers approach software service providers to make their software ideas a reality. It is at this point that the software project is initiated.

A traditional Waterfall Project (SDLC) proceeds in the following stages:

• Being testers, we understand that testing is not confined to phase 5, “Testing” alone. Instead, we play a significant role throughout the entire process.
• Testing is a reactive task. We can’t test anything without code or an application to test on. To prepare and react effectively, we aim to plan and prepare ahead. Hence, our activities start well before phase 5.

Here’s a brief summary of what occurs in each stage:

Initiation:

The production of software commences once the producer and the customer agree to the terms.

• In this stage, business requirements are collected and analyzed. This analysis covers decisions on technological considerations, specifications for hardware and software, resources, effort, time, relevance, and improvements, among other aspects.
• Business analysts, project managers, and representatives of the client are involved.
• At the end of this stage, the project plan is prepared.
• Documents specific to the project, such as a scope document or business requirements document, are created.
• Usually, the involvement of QA is not expected at this stage, although it is always ideal to involve QA from the beginning for the early identification of development-phase issues.

Defining:

The finalized business requirements serve as the foundation for this step.

• This stage includes translating the business requirements into functional requirements for the software. For instance, if the business requirement is to enable users to make purchases on a website, the functional requirement will delineate details such as the site’s design, menu options, product search, shopping cart, checkout process, payment options, and sale confirmation.
• Developers, business analysts, and project managers are involved.
• The output of this stage is a comprehensive document containing the software’s functional requirements. This document has several names, such as Software Requirement Specification (SRS), Functional Requirements Document (FRD), or Functional Requirements Specification (FRS).
• After the completion of the SRS documentation, the QA team is involved.
• While the functional requirements are being finalized and the SRS is being documented, the QA manager/lead prepares a preliminary version of the Test Plan and assembles the QA team.
• Once the SRS document is complete, the QA team becomes actively involved.
• At this stage, the development team, business analyst, or QA team lead will conduct a walkthrough of the SRS document with the QA team.
• For a new project, a comprehensive walkthrough in the form of a conference or a 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 location. The QA team reviews the document offline, gaining a thorough understanding of the system.
• Since testers aren’t the only audience for the SRS document, not all of its contents will be applicable to us. As testers, we must scrupulously review the document to ascertain which parts are useful to us.

SRS Document for this Live Project

We have attached a sample SRS document to provide you with an insight into its content, format, and structure. In the following article, we will demonstrate 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 introduced the Software Development and Testing process and shared a sample SRS document for the project we will be testing.

=> The upcoming article in this software testing training series will concentrate on the Examination of the SRS Document and Formulation of Test Scenarios.

Note: While we’re preparing the next article in this QA training series, we encourage you to work alongside us for the most hands-on experience. Get acquainted with the SRS document, and when we meet again, we’ll proceed with the next steps.

Happy Testing until next time!

About the Author: This live project QA training series is being spearheaded by Swati Seela, one of the STH team members.