1. Why use the scenario method to design test cases?
Most business software is composed of background management (such as user management, role management, rights management, etc.) and workflow. End users, expect software to achieve business requirements, rather than a simple combination of functions. For single-point functions, most problems can be solved by using equivalence class, boundary value, and decision table use-case design methods. For software systems involving business processes, the scenario method is more appropriate.
2. What is the scene method?
Scenario business flow is usually divided into basic flow, alternative flow, abnormal flow
Basic flow: The basic flow represents the process that the input is correct and can achieve the goal through the business process. (Insert the card--"Enter the correct password--"Enter the amount--"Withdraw money--"Withdraw the card)
Alternative flow: The alternative flow means that the input error (or operation error) when passing through the business process causes the process to repeat, but after correction, the process can still achieve the goal. (Insert card --> Enter wrong password -- "Enter Correct password -- "Enter amount -- "Withdraw money -- "Withdraw card)
Exception flow: Exception flow indicates that an input error (or operation error) occurs when the business process is passed, resulting in an abnormal termination of the process (insert card --> enter wrong password 3 times --> swallow card).
A process user expectation: unique in-degree, unique out-degree. Every process contains a process node that has never been walked.
