Testing Techniques

Boundary Value Analysis:
Boundary Value Analysis is a software testing technique used based on boundary value set with valid and invalid partitions with maximum and minimum values. And it checks for the input values near the boundary that partitions set and gives an output whether it comes under valid or invalid and gives a user with more defects than false defects. Mainly, Boundary value analysis is used to find defects near the edges.
For instance, the job applications need to be received over 18 and under 35.
Age (1 = <17) Age (=18<35) Age (>35<60)
Invalid Valid Invalid

Decision table testing:
Decision table testing is a software testing technique is also called as Pairwise testing where we can use a combination of multiple inputs to test and find defects. Comparatively, Decision table testing covers most of the test scenarios as we combine multiple test cases and it improves the quality of the product. It’s also known as Requirement Traceability Matrix where it maps all the requirement with the test cases. It provides the document where it covers all the test cases with the combination to find errors.
For instance, Let’s take a Login account for PVR Cinemas.

Testcase 1: The registered mobile number should be correct. Hence, the user should be getting OTP to his registered mobile number.
Testcase 2: The registered mobile number was correct but the OTP was wrong. Hence, an error message should be displayed as “Please enter the correct OTP”.
Testcase 3: The registered mobile number was wrong. Hence, an error message should be displayed as “Incorrect Mobile number, please enter the registered mobile number to proceed”.
Testcase 4: The registered mobile number and OTP entered should be correct. Hence, the user should be redirected to PVR homepage.
Use-case Testing:
Use-case testing is a testing technique written by user as it’s a user-oriented and not a system oriented. The client will provide the Customer Requirement Specification and the developers will write a testcase and the clients will review it to make sure and once it’s get approved by client, the developers will start the coding. Once the application is developed, Testers will test the application. So, the Use-case testing is mainly focused by User-approach and Scenario-based testing.
LCSAJ Testing:
LCSAJ stands for Linear Code Sequence and Jump comes under a White box testing technique to identify the code coverage, from end to end which can begin at anywhere from the start or branch or end of the program. It also helps in designing new test cases, which can also increase the code coverage under the test.