Types of Testing

Write a short note on Boundary Value Analysis.

What is Boundary Value Analysis?

It is a software testing technique in which tests are designed to include representatives of boundary values in a range.
A boundary value is any input or output value on the edge of an Equivalence Partition.
It is a black box test design technique where test cases are designed by using boundary values.
This technique is used in range checking.
This is the technique of making sure that the behavior of the system is predictable for the input and output boundary conditions.

Example of Boundary Value Analysis

Suppose input should be greater than equal to 10 and less than 50.
So, according to this input values from 10 to 49 are valid, but if you make mistakes in specifying the conditions, the following things can happen:

Input <= 10 AND < 50 → Input value 9 is Valid.

Input >= 10 AND input <= 50 → Input value 50 is Valid.

Input > 10 AND input < 50 → Input value 10 is Invalid.

Input >= 10 AND input > 50 → Input value 49 is Invalid.

In the above example, at the minimum it should have following test cases for boundaries 9, 10, 11 and 48, 49, 50.
These values are respectively:

It is very easy to introduce defects at boundaries, boundary value are important.
Boundary Value Analysis technique is used to identify errors at boundaries rather than finding those exist in center of the input domain.
It is a next part of Equivalence Partitioning for designing the test cases where these cases are selected at the edges of the equivalence classes.
It is also called as part of stress and negative testing.

What is Tester's Workbench?

It is a virtual environment which is used to verify the correctness of a design or model.
It contains a generic set of tools which support automation of testing tasks.
It is the process to verify and validate the system structurally and functionally.
It is one part of the software development life cycle, which is comprised of many workbenches.

Features of Tester's Workbench

It simplifies test creation with Story Board testing and Code-free test authoring.
Quickly develop complex performance test scenarios with script-less, visual, performance test and workload models.
It provides earlier, end-to-end continuous integration testing throughout hardware, software and cloud-based dependencies.
It emulates workloads accurately that represents realistic user scenarios.
It is extensible and supports standards and protocols helps to meet the challenges of testing environment.

Sr. No.	Alpha Testing	Beta Testing
1.	Alpha testing is performed by the developers at the software development site.	Beta testing is performed by the customers on their own site.
2.	This testing is also performed by the Independent Testing Team.	This testing is not performed by the Independent Testing Team.
3.	Alpha testing is always performed within the organization.	Beta testing is always performed outside the organization.
4.	It performs in the Virtual Environment.	It performs in the Real Time Environment.
5.	This testing is not open to the market and the public.	This testing is always open to the market and the public.
6.	It is considered as the User Acceptance Testing (UAT) which is done in the developer's area.	It is considered as the User Acceptance Testing (UAT) which is done at customers or users area.
7.	It comes under White Box Testing and Black Box Testing.	It comes only in Black Box Testing.
8.	It is conducted for the software application and project.	It is conducted for software product.
9.	It is not known by any other different name.	It is also known as Field Testing.
10.	The long execution cycle may be required for Alpha testing.	Only a few weeks of execution are required for Beta testing.
11.	It ensures the quality of the product before moving to Beta testing.	It concentrates on the quality of the product, but it gathers user's input on the product and ensures that the product is ready for real time users.