Task 2

Boundary Value Analysis is a way to test systems that looks at the edges or limits of what values should be sent to them. We don't test every possible input, so we only test numbers close to the minimum and maximum. To show this, if a program can handle numbers from 0 to 100, we would try it with 0, 1, 2, 99, 100, and 101. Errors often happen near these lines, so this helps find bugs. We can find mistakes better if we check these important points. Boundary Value Analysis is useful because it only needs to test a few scenarios to find a lot of possible problems. Still, it's not 100% safe. Errors don't always happen at the edges, they can happen anywhere. So, BVA is helpful, but it needs to be used with other testing methods for full software quality assurance.

Decision testing makes sure that a piece of software always picks the right option, no matter what. Here's how it works: We build test cases based on the various possible decisions the program can make. For example, if a program decides to give a discount based on a customer's age, we'd test it with different ages to see if it gives the right discount. This method helps us find bugs related to decision-making logic. We want to make sure the program does what it's meant to do under different circumstances. Decision testing is important because programs often have to make choices, and we need to be sure they make the right ones. By testing these choices, we can catch errors early and make the program more reliable.

Use case testing is a method to examine if a software program performs as it should in real-life settings. In basic terms, it involves evaluating how the software acts when users interact with it based on different situations or "use cases." A use case is like a story showing how a human (the user) interacts with the software to accomplish a given goal. Testers construct test cases that mirror these real-world events to guarantee the software performs correctly. For instance, in an e-commerce platform, a use case could be placing an order. Testers would then write tests to make sure that the ordering process—from adding products to the cart to payment—is smooth and error-free. Use case testing helps discover difficulties that users can encounter in their everyday interactions with the program, making it a crucial aspect of maintaining a great user experience.

LCSAJ, or Linear Code Sequence and Jump testing, is a method used to check the integrity of software programs. In simple terms, it includes studying the flow of code execution by inspecting every potential sequence of statements and jumps within the program. Testers design test cases to verify that each line of code, together with any conditional jumps, is run at least once during testing. By doing this, they can uncover any potential mistakes or defects in the program's logic or flow. LCSAJ testing helps ensure thorough coverage of the codebase, increasing the possibility of identifying bugs or vulnerabilities. While it may involve more time compared to other testing methodologies, LCSAJ testing is essential for guaranteeing the resilience and reliability of software systems, particularly in critical or safety-sensitive applications where even little errors can have substantial repercussions.