CH05.L06 . BBT-5-Use case

Summary

The video script discusses the use case technique in software testing, focusing on its role in black box testing. It explains the components of a use case, including actors, preconditions, and post-conditions, using a banking ATM as an example. The script highlights the extraction of test cases from use case diagrams, emphasizing the initial number of cases and the potential for further case extraction through techniques like Equivalence Partitioning (EP) or Boundary Value Analysis (BVA). The summary underscores the importance of the use case approach for assessing the system's main functionality externally.

Takeaways

• 💼 The script discusses the role of a software designer in creating models of documentation and requirements, focusing on the 'Use case' method.
• 🔍 'Use case' is highlighted as a technique for Black box testing, from which test cases can be derived.
• 👥 The 'Use case' includes key components such as Actors, Preconditions, and Post-conditions.
• 🏦 An example of a Use case diagram is provided for a banking ATM system, illustrating how it can be used to identify actors and their interactions.
• 👨‍💼 The actors in the ATM Use case diagram are the customer, ATM technician, and bank.
• 💳 A precondition mentioned is that the customer must have an account to use the software.
• 💰 Post-conditions relate to the financial transactions affecting the credit status of the actors.
• 📈 Six test cases are planned to be extracted from the Use case diagram, with a focus on the customer and technician actors.
• 🔎 The script emphasizes the importance of further detail extraction for each test case, potentially using other techniques like EP or BVA.
• 🔑 The Use case technique is described as being applicable for the whole system, focusing on external interactions and main functionalities.

Q & A

What is a 'Use case' in software design?

A 'Use case' is a technique used in software design to describe a sequence of actions that a system performs to achieve a specific goal. It is often used for black box testing to extract test cases.

What are the key components of a use case?

The key components of a use case include actors, preconditions, and post-conditions. Actors are those who will use the software, preconditions are the requirements that must be met before using the software, and post-conditions describe the state of the system after the actor has used it.

How can use cases be used for testing software?

Use cases can be used for testing software by extracting test cases from them. These test cases can then be used to verify that the software behaves as expected under various scenarios.

What is a black box testing technique?

Black box testing is a testing technique where the tester focuses on the output of the software without considering the internal workings. It is used to test the functionality of the software from the user's perspective.

What are the three actors identified in the use case diagram of a banking ATM?

The three actors identified in the use case diagram of a banking ATM are the customer, the ATM technician, and the bank.

What is the precondition for a customer using the banking ATM software?

The precondition for a customer using the banking ATM software is that the customer must have an account.

What are post-conditions in the context of a use case?

Post-conditions in a use case describe the state of the system after the actor has used it to achieve the required scenario and reach the targeted results.

How many test cases can be extracted from the use case diagram of a banking ATM?

From the use case diagram of a banking ATM, six test cases can be extracted: four from the customer actor and two from the technician actor.

What is the importance of considering the main function when creating test cases?

Considering the main function when creating test cases is important because it helps ensure that all necessary test cases are identified. It also allows for the extraction of additional test cases using techniques like Equivalence Partitioning (EP) or Boundary Value Analysis (BVA).

How can further test cases be extracted from a main function?

Further test cases can be extracted from a main function by using detailed techniques such as Equivalence Partitioning (EP) or Boundary Value Analysis (BVA) to identify specific scenarios and edge cases that need to be tested.

What is the role of a use case diagram in software testing?

A use case diagram provides a visual representation of the interactions between actors and the system. It helps in identifying the initial number of test cases to be written and understanding the main functionality of the system from an external perspective.