I've developed a new diagram that I think it much better at communicating how the messages in a system flow between components. I've used sequence diagrams for this in the past, but I've always found a number of problems with them.
This very simple flow produces a large diagram:
What's wrong with this?
I've set out to create a new type of diagram to replace sequence diagrams:
I decided to focus on the process rather than the participant, use a small number of familiar symbols (anything else, such as conditional or loops are done using notes), and keep the syntax terse.
The rules are basic:
I'd love to get your feedback - please add your comments below.
| || |
Free, Selenium 3.0 compatible, and at over 420 pages this book is a hands-on guide to dozens of specific ways you can use to get the most of WebDriver in your test automation development.
This book will help you learn the fundamentals of the WebDriver API such as locating and interacting with web pages, through advanced topics such as Page Objects and mobile testing, and finally teach you how to build up your own web application testing framework.
Java technical lead and solutions architect in London for the UK IT industry for over ten years. more...