TASK-2

Q: Describe the following testing techniques with proper examples
a) Boundary value Analysis
A: Boundary value analysis is based on testing the boundary values valid and invalid partitions. The behavior at the edge of the equivalence partition is more likely to be incorrect than the behavior within the partition, so boundaries are an area where testing is likely to yield defects.
It checks for the input values near the boundary that have a higher chance of error. Every partition has its maximum and minimum values and these maximum and minimum values are the boundary values of a partition.
In BVA we test boundaries between equivalence partitions one test case for each boundary value.

Benefits of BVA :-

Efficient identification of potential errors at the edges of input domains.
It helps to ensure that the software handles boundary conditions correctly.
Provides focused testing on critical areas where errors are likely to occur.

Note:

A boundary value for a valid partition is a valid boundary value.
A boundary value for a invalid partition is a invalid boundary value.

Below are the principle of BVA :-

Input Boundaries: >>BVA is applied to both input and output boundaries. >>It considers the minimum ,maximum, and just beyond the min and max value for input.
Test cases: >>Test cases are designed to evaluate the behavior of the software at the boundary values. >>Typically three sets of test cases are created for each boundary: one with a value just below the boundary, one at the boundary, and one just beyond the boundary.
Error Detection: >>The goal is to identify errors related to boundary values, such as off-by-one errors or issues with boundary conditions.
Examples: >>If a system accepts values between 1 to 100, boundary values would include tests with 0,1,100 and 101. >>For a range of dates, boundary values might include testing the day before, the first day, the last day, and the day after the specified range.
Applicability: >>BVA is particularly effective for input conditions that have a range of valid values, such as numeric ranges, date ranges, or any other parameter with defined limits.

Example :-

Consider a system that accepts ages from 18 to 56

Valid test case : Valid test cases for the above example can be any value entered greater that 17 and less than 57

Enter the value : 18

Enter the value : 19

Enter the value : 37

Enter the value : 55

Enter the value : 56

Invalid test case : Where any value less than 18 and greater than 56 is entered

Enter the value : 17

Enter the value : 57

b) Decision Table testing
A : Decision table testing is very effective tool in testing the software and its requirements management. The output may be dependent on many input conditions and decision tables give a tabular view of various combinations of input conditions and these conditions are in the form of True(T) and False (F). Also, It provides a set of conditions and its corresponding action required in the testing.
This is systematic approach where the different input combinations and their corresponding system behavior(Output) are captured in a tabular form.

Components of decision table testing

Conditions: >> These are the factors or criteria that influence the decision making process. >> Conditions can be either True or False.
Actions: >> These represents the possible outcomes or actions based on the combinations of conditions.
Rules: >> Each row in the decision table represents a unique combination of conditions and the corresponding action or outcome.
Columns: >> Columns represent different conditions and actions

Example of a decision Table :

Consider a example where a system determine if a person is eligible for a discount based on age and membership status:

In this above example, the decision table outlines the different combinations of age and membership status conditions, along with corresponding discount actions. Testing would involve creating test cases based on these combinations to ensure the system behaves correctly.

c) Use Case testing
A : Use case testing is a Black box testing technique that focuses on validating the functionality of a software application by testing its use cases. A use case represents a specific way of user interacts with the system to achieve a particular goal. use case testing ensures that the system behaves as intended and meets user requirements in real world scenarios.
Tests can be derived from use cases, which are specific way designing with software items.
Use cases are associated with actors(Humans, External hardware, other components or system) and subjects (the component or system to which the use cases is applied).

Key steps in use case testing

Identify the use cases : Define and identify the various use cases that describes how different users interact with the system to accomplish specific tasks or goals.
Understand user scenarios : Gain a comprehensive understanding of the user scenario outlined in each use cases, This includes input, expected outputs and the sequence of interactions.
Create test cases : Develop test cases based on the identified use cases, covering various scenarios and conditions that users might encounter during real world usage
Test execution : Execute the test cases to verify that the system behaves correctly and provides the expected outputs in accordance with the defined use cases.
Evaluate Functionalities : Validate whether the functionalities described in the use cases are implemented correctly and meet user expectations.
Boundary conditions and Exception handling : Test boundary conditions and exceptional scenarios to ensure that the system handles edge cases and unexpected inputs as specified in the use cases.
User interface testing : If applicable, Perform user interface testing to ensure that the graphical elements and interactions align with the use cases

Example :- Consider and e-commerce application with a use cases for placing order. The use case may include below steps :

User login
User adds items to the shopping cart
User proceeds to checkout
User enters shipping and payments information
User confirms the order

d)LCSAJ Testing
A : Linear code sequence: A Linear code sequence refers to a series of instructions in a program executed in 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 altered based on conditions. This includes construct like if statements, loops and other branching mechanism.

Example:-