Unit Testing

 

What is Unit Testing?

UNIT TESTING is a type of software testing where individual components of a software are tested. The purpose is to validate that each unit of the software code performs as expected. Unit Testing is done during the development of an application by the developers or tester it is the first level of testing

A unit is a single testable part of a software system and tested during the development phase of the application software.

The purpose of unit testing is to test the correctness of isolated code. A unit component is an individual function or code of the application. White box testing approach used for unit testing and usually done by the developers.

How to create unit testing test case

How To Create Test Scenario In Live Project

 The test scenario is a detailed document of test cases that cover end to end functionality of a software application .  The test scenario is a high-level classification of testable requirements. These requirements are grouped on the basis of the functionality of a module and obtained from the use cases.

In the test scenario, there is a detailed testing process due to many associated test cases. Before performing the test scenario, the tester has to consider the test cases for each scenario.

How to create a Test Scenario

• Carefully study the Requirement Document – Business Requirement Specification (BRS), Software Requirement Specification (SRS), Functional Requirement Specification (FRS) pertaining to the System Under Test (SUT).
• Isolate every requirement, and identify what possible user actions need to be tested for it. Figure out the technical issues associated with the requirement. Also, remember to analyze and frame possible system abuse scenarios by evaluating the software with a hacker’s eyes.
• Enumerate test scenarios that cover every possible feature of the software. Ensure that these scenarios cover every user flow and business flow involved in the operation of the website or app.
• After listing the test scenarios, create a Traceability Matrix to ensure that every requirement is mapped to a test scenario.
  Get the scenarios reviewed by a supervisor, and then push them to be reviewed by other stakeholders involved in the project. Example
• 
  
  
  

HOW TO CREATE TEST CASE IN LIVE PROJECT WITH EXAMPLE

 

What is a Test Case?

TEST CASE is a set of actions executed to verify a particular  functionality of your software application. Test Case contains test steps, test data, precondition, postcondition developed for specific test scenario to verify any requirement. The test case includes specific conditions, using which a testing engineer can compare expected and actual results to determine whether a software product is functioning as per the requirements of the customer. EXAMPLE

Test Case Example

Sanity Testing VS Smoke Testing Diffrance with information

Introduction

 

The life of a QA Tester will be considered incomplete if the terms ‘Smoke Testing’, ‘Sanity Testing’ and ‘Regression Testing’ are not infused into it. Though these are some regularly used terms, there are some common misconceptions around them too.

 

Software Build

Before we delve deeper into how these three testing methods differ, we must explain what a software build is.

Can you think of the primary component of building software? Well, yes, we are talking about the code. But we know that it is not just one code that builds the entire software. There are thousands of source code files depending on the complexity of the software. Needless to mention, these source codes need to be compiled into a single executable file, which can be shared with the release team to be deployed. The process of compiling these source code files into a single file is called a software build. It is pretty literal here because it is the process where the software is built to implement it.

 

Smoke Testing	Sanity Testing
Smoke Testing is performed to ascertain that the critical functionalities of the program is working fine	Sanity test is done to check the new functionality /bugs have been fixed
This testing is performed by developer or tester	This testing is performed by tester
Sanity testing exercises only the particular component of the entire system	Smoke testing exercises the entire system from end to end
To test the stability of new build	To test the stability of new functionality or code changes in the existing build
It is a part of basic testing	It is a part of regression testing
Smoke testing , build may be either stable or unstable	Sanity testing , build is relatively stable