I was reading "Growing Object-Oriented Software, Guided by Tests" lately. Authors of this book suggested to always start developing a test suite with an end-to-end acceptance test.
Also another article says writing effective test case design is a skill and that can be achieved by some experience and in-depth study of the application on which test cases are being written. They always believe that the first set of effective test cases are end to end scenarios which would give you a safety net to validate the testing coverage of the application
Each of us know that if we use Cyclomatic Complexity technique we will be able to derive the number of independent path executions (End to End Scenarios) in the workflow of the application. It is very time consuming process to apply various methods on the workflow to identify independent paths. Here is the macro helps to identify the end to end scenarios for your workflows.
Very Simple!. Follow simple steps to get independent paths
1. Draw a control flow graph 2. Open the attached excel workflow 3. Enter name of the nodes in horizontal and vertical position 4. Specify ‘F’ alphabet in the cell where node to node connects 5. Click Run button 6. Click ‘OK’ button to close the dialog box 7. End to end scenarios are ready now 8. You want to run again, you simply replace “D” with “F” alphabet then click run button.
Note: In the attached sheet contains Unitary Payment workflow and generated end to end scenarios.