Quick Reference Study Notes for Software Testing

Software Testing

 Software testing is the next step in SDLC after development where it is checked if the object which is developed is working as intended or not? It consists of executing different test cases If the entity under the scope is working correctly, the test case is marked as ‘pass’ else ‘fail’. It allows us to detect bugs which are left unnoticed by the developer.Due to this, it is also known as “Quality Assurance”. It is of two types : Manual and Automation. These days Automation is gaining a lot of popularity in the industry due to its nature which saves ample time that is wasted in retesting after updation of code.

 STLC(Software Testing Life Cycle)








Requirements/Design Review                    

You review the software requirements/design (Well, if they exist.)

  • ‘Review Defect’ Reports


Test Planning

Once you have gathered a general idea of what needs to be tested, you ‘plan’ for the tests.

  • Test Plan

  • Test Estimation

  • Test Schedule


Test Designing

You design/ detail your tests on the basis of detailed requirements/design of the software (sometimes, on the basis of your imagination).

  • Test Cases/Test Scripts/Test Data

  • Requirements Traceability Matrix


Test Environment Setup

You set up the test environment (server/ client/ network, etc) with the goal of replicating the end-users’ environment.

  • Test Environment

Rich company

Test Execution

You execute your Test Cases/ Scripts in the Test Environment to see whether they pass.

  • Test Results (Incremental)

  • Defect Reports


Test Reporting

You prepare various reports for various stakeholders.

  • Test Results (Final)

  • Test Metrics

  • Test Closure Report

  • Who Worked Late & on Weekends





Testing Types 

Testing Category

Types of Testing

Functional Testing

  • Unit Testing

  • Integration Testing

  • Smoke

  • Sanity

  • UAT ( User Acceptance Testing)

  • Localization

  • Globalization

  • Interoperability etc.

Non-Functional Testing

  • Performance

  • Endurance

  • Stress

  • Volume

  • Scalability

  • Usability etc.


  • Regression

  • Maintenance



  • Unit Testing

It is a level of software testing where individual units/ components of a software are tested. The purpose is to validate that each unit of the software performs as designed.

  •  Integration    Testing

It is a level of software testing where individual units are combined and tested as a group. The purpose of this level of testing is to expose faults in the interaction between integrated units. Test drivers and test stubs are used to assist in Integration Testing.

  • System Testing

The process of testing an integrated system to verify that it meets specified requirements.

  • Smoke Testing

It is a kind of Software Testing performed after software build to ascertain that the critical functionalities of the program is working fine.

  • Sanity Testing

It is done after receiving a software build, with minor changes in code, or functionality, to ascertain that the bugs have been fixed and no further issues are introduced due to these changes.

  • Regression Testing

It is a type of software testing that intends to ensure that changes (enhancements or defect fixes) to the software have not adversely affected it.

  • Performance Testing

It is done to check whether the system meets the performance requirements such as responsiveness etc.

  • Stress Testing

It is done when a system is stressed beyond its specifications in order to check how and when it fails. This is performed under heavy load like putting large number beyond storage capacity, complex database queries, continuous input to the system or database load.

  • Volume Testing

The software or application undergoes a huge amount of data and Volume Testing checks the system behavior and response time of the application when the system came across such a high volume of data. This high volume of data may impact the system’s performance and speed of the processing time.


Important Documents

 Test cases

If we focus on the word “Cases”, what it tells us is that there are certain scenarios which we are testing. Here’s where creativity kicks in and also the prior experience of the testing personnel helps in way that he/she can see it coming.  Test cases sheet development helps the tester to retest the cases after new builds, he doesn’t need to think of the scenarios again and again. It also helps team to see and understand the situation clearly and allows them to reproduce.


Bug Report

A bug report is a document in which all the bugs that have been found are placed and some details of them are mentioned which allows the development team to find out what is lacking in the system and what needs to be done.

Sample Bug report

Bug Name: Application crash on clicking the SAVE button while creating a new user.

Bug ID: The BUG Tracking tool will automatically create it once you save this.

Area Path: USERS menu > New Users

Build Number:/Version Number 5.0.1

Severity: HIGH (High/Medium/Low)

Priority: HIGH (High/Medium/Low)

Assigned to: Developer-X

Created By: Your Name

Created On: Date

Reason: Defect

Status: New/Open/Active – Depends on the Tool you are using

Environment: Windows 2003/SQL Server 2005


Application crash on clicking the SAVE button while creating a new user, hence unable to create a new user in the application.

Steps To Reproduce:

1) Logon into the application

2) Navigate to the Users Menu > New User

3) Filled all the fields

4) Clicked on ‘Save’ button

5) Seen an error page “ORA1090 Exception: Insert values Error…”

6) See the attached logs for more information

7) And also see the attached screenshot of the error page.

Expected: On clicking SAVE button should be prompted to a success message “New User has been created successfully”.

*NOTE : "This study material is collected from multiple sources to make a quick refresh course available to students."

This website uses cookies to improve user experience. By using our website you consent to all cookies in accordance with our Cookie Policy. More info. I Agree