Task 2

1. BOUNDARY VALUE ANALYSIS
   It is the software testing technique in which tests are designed to include representatives of boundary values in a range. The idea comes from the boundary. Given that we have a set of test vectors to test the system, a topology can be defined on the set. It checks for the input values near the boundary that have a higher chance of error. Every partition has its maximum and minimum values are the boundary values of the partition
   Example:
   Need to set a minimum age requirement of 18 and maximum of 65. Need to provide the input values at the upper and lower limits along with the values which are inside or outside of the limit

2. DECISION TABLE TESTING
   It is the software testing technique used to test the system behaviour for the different input combinations. This is a systematic approach where the different input combinations and their corresponding system behaviour are captured in a tabular form. It is a very effective tool used for both complex software testing and requirements management. A decision table testing helps to check the all possible combinations of conditions for testing and testers can easily identify missed conditions
   Example:
   Username and password both were wrong. The user is shown an error message

3.USE CASE TESTING
It is generally a part of block box testing and helps developers and testers to identify test scenarios that exercise the whole system on each transition basis from start to finish. Business experts and developers must have a mutual understanding of the requirement. It is a functional testing technique that helps in identifying and testing scenarios on the whole system. It is used to develop the test cases at the system level or acceptance level
Example:
Online E-commerce purchase might include separate reports for adding item to the cart, selecting the payment type and choosing a shipping and delivery option
4.LCSAJ TESTING
It stands for Linear Code Sequence and Jump. It is a white box testing methodology used to determine the code coverage, what percentage of the code is executed with the existing test cases. It helps in designing new test cases which can increase the coverage of the code under test. Once the code coverage reaches the certain level we can stop the testing