Testing Techniques
1)Boundary Value Analysis: - It is a Black Box testing technique in which tester test at boundary values. It is observed that there are high chances of finding defect is at the boundary’s values. Boundary value analysis can perform at all test levels.
Example: consider we have requirement where customer will get discount in gym for those who have age in between 20-28years old.
So, by using boundary value analysis here tester test at these boundary values.
• 19 below boundary value (20) customer is not eligible for discount.
• 20 at lower boundary value customer is eligible for discount.
• 28 at upper boundary value customer is eligible for discount.
• 29 is above boundary value is not eligible for discount.

1. Testcase01 Tester test in TC1 with value 19.
2. Testcase02 tester test with value 20.
3. Testcase03 Tester test with value 28
4. Testcase04 Tester test with value 29 With these 4 testcases tester test mentioned requirement.

2)Decision Table: It is a Black Box testing techniques where tester test with multiple input conditions.
In Boundary value analysis, tester test with only one input so when tester must test with multiple input conditions then decision table testing techniques is used.
In this technique tester creates decision table which is tabular representation of input versus rules\test conditions.
This type of techniques is helpful in covering more complex requirements.
Let’s investigate one scenario of Banking application where tester needs to check for credit card eligibility. So as per requirement customer who is salaried or monthly salary income is greater than 30000 and fill ITR then he is eligible for credit card.

So, Tester needs to test these 4 testcases as per defined rules to verify mentioned requirement.

•TC01 Verify condition where customer is salaried or monthly income is more than 30000 and he fills ITR then expected result is customer is eligible for credit card.
•TC02 Verify condition customer is salaried and monthly income is not greater than 30000, he fills ITR then expected result is customer is eligible for credit card.
•TC03 Verify condition customer is not salaried and monthly income is greater than 30000, he fills ITR then expected result is customer is eligible for credit card.
•TC04 Verify condition customer is salaried and monthly income is not greater than 30000, he does not fill ITR then expected result is customer is not eligible for credit card.

Decision table technique it is simple to interpret different business requirements.

3)Use case testing: In Use case testing testcases are derived from Use cases.
Use cases are associated with actors (users, human, external components) and subjects (system to which use case is applied).
In Use case actors are represented by “A”, and system is represented by “S”.
Let’s investigate one scenario: We have one web application and tester needs to verify login functionality.
If user enters invalid password 3 times, his account will get locked.

•Testcase 01 will be when actor enters username and correct password in web application. And system validate the password. Users enter in web application.
•Testcase 02 will be when actor enter in correct password and system validate it and shows message “Password is in valid and please Try”.
•Testcase 03 when user enter incorrect password till 3 times and system validate it and shows message” User account is locked”.

4)LCSAJ Testing: - Stands for Linear code sequence and Jump. It is a white box technique.
Linear code sequence: A Linear code series refers to a series of instructions in a program executed in a straight, sequential order without any branches or jumps. The goal is to test each linear Sequence of code to ensure that it behaves as expected.

Jump: A jump refers to control flow operations in programming where the normal sequential execution of code is alerted based on conditions. This includes constructs like loops, branches, if statements.
A single LCSAJ has the following three components:
•Start of the segment, which can be a branch or the start of the program.
•End of the segment, which can be the end of a branch or the end of the program.
•A specific target line.