Proper Black Box Test Case Design-part 2-Boundary Value Analysis

Proper Black Box Test Case Design - Part 2 - Boundary Value Analysis Our second post in this series focuses on efficient test case design using black box testing. The goal of these posts is to make you better at designing test cases so that you can develop higher quality systems. In-depth explanations and practice exercises are at the core of these tutorials. In part one of this tutorial, we discussed: What a well-designed test case is Different types of software testing Black Box Testing Equivalence Partitioning Boundary Value Testing Today, we are going to continue working on learning Black Box Testing techniques. Specifically, we will learn Boundary Value Testing (BVT). BVT further expands upon the concepts that you mastered in the Equivalence Partitioning Tutorial. You will utilize the equivalence partitioning technique to help you with boundary value testing. In the previous post, I started with an example of a very simple test case. I will further expand upon it here. Test Scenario Consider the following situation where a text box allows the following integers to be entered: 1 – 5 Success 5 – 9 Monkeys 9 – 11 Bananas Use your newly found skills to create equivalence classes. (See the completed example below.) You might notice that you run into an issue at all of the boundaries, or edge cases. For example, if you enter a 5, does that return a “Success” or “Monkeys”? Same goes for the 9; will that return “Monkeys” or “Bananas”? Testing the edge conditions in software testing is known as boundary value testing. Isn’t it awesome how the name makes complete sense? Boundary...

Pin It on Pinterest

Clef two-factor authentication