Let we discuss about some topics like 1) Boundary Value Analysis 2) Decision Table Testing 3) Use Case Testing 4) LCSAJ Testing

Boundary Value Analysis
It is one of the functional testing. It is based on testing the boundary values of valid and invalid partitions. Boundaries are values where testing is likely to yield defects.
For each variable we check-
1) Minimum value.
2) Just above the minimum.
3) Nominal Value.
4) Just below Max value.
5) Max value.
For example:
If the valid input is between 1 to 10. Then the boundary values are 0,1,2 and 9,10,11.
Limitations:
• It is useful when the product is under test.
• BVA is quite rudimentary.
Decision Table Testing
This technique is used if we have more conditions and we have to perform action based on the conditions at that moment.

The decision table have four parts they are.
Stubs   Entries

Condition C1
C2
C3

Rule
Action A1
A2
A3

Outputs

1. Condition stubs.
2. Action stubs
3. Condition Entries.
4. Action Entries.

For example:
Condition:
1. Account has to be approved.
2. OTP to be matched
3. Sufficient amount to be present in the account
Action:
1. Transfer money.
2. Show alert message “insufficient account balance”
3. Block if any suspicious activity.
TC1 TC2 TC3 TC4 TC5
Condition 1 Account already approved T T T T F
Condition 2 OTP Matched T T F F x
Condition 3 Sufficient money T F T F x
Action 1 Transfer money Execute

Action 2 Show insufficient money alert message Execute

Action 3 Block the transaction Execute Execute x

Use Case Testing
It is a Black box testing.Use Case is a tool for defining the required user interaction. It depends on the user interaction and the response of the system to the user’s action. It is mainly user- oriented. It tests the functional requirement of the system. It usually helps to uncover the integration defects, due to the incorrect interaction between different components.
Use case testing is generally produced from the SRS document. If specific User interaction scenario missed in the SRS document, probably the same be missed in the test case also.
For example:

1. User - Enters the mail Id.
2. System – Validates the mail id.
3. User – Enters the password.
4. System – Validates the Password.
5. System – Enter in to respective user mail.

Linear code sequence and jump (LCSAJ) Testing:
It is a white box testing used to test code coverage. Means what percentage of code is executed with the existing test cases.
It has three components they are
1) Start of the segment.
2) End of the segment.
3) Target line
The code usually executes from the start of the segment to the end of the segment and then the control flow breaks the sequential execution and jumps to the target line to transfer the control flow.
For example:
LCSAJ Number Starting of the segment Ending of the segment Target line to transfer control flow
1 4 9 11
2 4 13 7
3 7 10 15
4 7 13 7
5 11 13 7

100% LCSAJ coverage means the test data covers all the above LCSAJs in the table.
And line density means number of times the a line number appears in LCSAJs.