Testing technique: 1)Boundary value analysis 2)Decision Table Testing 3)use case Testing

Testing technique:
1)Boundary value analysis
2)Decision Table Testing
3)use case Testing

Boundary Value Analysis:
• Boundary value analysis is based on testing the boundary values of valid and invalid partitions.
• Every partition has its maximum and minimum values and these maximum and minimum values
are the boundary values of a partition.
Example: If we want to enter an amount between 100 to 1000.
Here we check based on boundaries for 100, we take 98, 99, 101, 102, and for 1000, we take 998, 999,
1001, 1002

Decision Table Technique:
• In the Decision table technique, we deal with combinations of inputs.
• To identify the test cases with a decision table, we consider conditions and actions.
• We take conditions as inputs and actions as outputs.
Example: Login validation - Allow user to log in only when both the username and password is correct.
• Conditions 1: Enter a valid username and valid password and Click Login.
o Actions 1: Display the home page and Execute.
• Conditions 2: Enter an invalid username and valid password and Click Login.
o Actions 2: Display Error message as invalid username

use case testing
Use case testing involves examining how software behaves in response to specific user interactions or scenarios. It's like putting the system through its paces to ensure it does what it's supposed to do in real-life situations.
• Take, for instance, an online shopping site. We could have a use case where a user searches for a product, adds it to their cart, goes through the checkout process, and completes the purchase.
• During use case testing, we'd meticulously go through each step of this scenario. We'd check if the search results are accurate if the items get added to the cart properly, if the checkout process is seamless, and if the payment goes through without a hitch.
• In essence, use case testing helps us catch any glitches or hiccups in the system, making sure it meets user expectations. It's all about ensuring the software performs as intended from the user's standpoint, boosting its overall quality and reliability.