Methods of Manual Testing
Tags: guvi, manual, methods
Published: 2023-09-04 00:23:44

**_Boundary Value Analysis_**
Boundary Value analysis is a software testing technique that evaluate the software performance at the boundaries or extreme input conditions. This technique is  effective at identifying issues related to boundary conditions, where software behavior may differ significantly from the behavior within the normal input range. The boundary limits include the max , min and above and below the limit
**_Password Length:_**
**_Requirement:_** Passwords must be between 8 and 16 characters.
**_BVA Test Cases:_** 
Test with passwords of lengths
7 (just below the lower boundary).
8 (on the lower boundary).
9 (just above the lower boundary).
15 (just below the upper boundary).
16 (on the upper boundary).
17 (just above the upper boundary).

**_Decision Table Testing_**
Decision table testing is a structured and systematic testing technique used to validate the correctness of a system's logic based on different combinations of inputs and it called as Cause-Effect table testing. It's particularly useful when dealing with complex business rules or scenarios this type of testing ensure that all possible combinations of conditions and their outcomes are tested, making it an effective technique for ensuring overall coverage. 
**_Input Conditions:_**
**_Customer Type:_** Regular, Premium
**_Purchase Amount:_** Low < Rs.100, High >= Rs100			
**_Condition 1_**	**_Condition 2_**	**_Output_**
Regular		             Low		No
Regular		             High		10%
Premium	                     Low		10%
Premium	                     High		20%
Customer Type: Regular, Purchase Amt: Low
output: No Discount
Customer Type: Regular, Purchase Amt: High
output: 10% Discount
Customer Type: Premium, Purchase Amt: Low
output: 10% Discount
Customer Type: Premium, Purchase Amt: High
output: 20% Discount

**_Use case Testing_**
Use case testing is a method used to validating the system's behavior by testing its functionality against real-world scenarios. Use cases represent interactions between users and the system to achieve specific results. Use case testing ensures that the software application meets user requirements, behaves as expected in various user case , and provides value to its intended users
**_Scenario:_**
A user registers for a website by giving  username, email address, and password.
**_User Test case:_**
User enters valid username, email, and password.
output: Registration is successful.
User enters an existing username with  valid email, and password.
output: Registration fails with a message of username is already taken.
User enters valid username, invalid email format, and valid password.
Expected Outcome: Registration fails with a message of invalid email format.

**_LCSAJ Test method:_**
**_Linear Code Sequence and Jump (LCSAJ) testing method_** which comes under  white-box testing technique that focuses on  testing the different paths within a program's  flow. It particularly follows  the sequences of instructions within a program, including linear sequences and jumps that change the flow of execution. LCSAJ testing aims to ensure that all possible paths, transitions, and jumps within the code are tested, which helps identify potential logic errors, missing code , and unexpected behavior. It  verifies the program's  logic by testing all possible test case scenarios.
**_scenario:_**
if x >0:
   y = x*2
else:
  y = x-1
Test Case 1: x > 0
result: y = 2 * x
Test Case 2: x <= 0
result: y = x - 1