Once upon a time, there was a company and I started working there, and what I found was a working system without any tests that we (I) needed to improve and change without breaking anything. And everybody was afraid of changing anything because it could break a completely different thing. And it was decided to leverage my BDD experience to start documenting the system inner works with user stories that could be validates with the users Then cucumber came for the rescue and the user stories became automated tests And to keep using the same tool, we have user stories of how small (unit test size) parts of the system works and how backend systems works also This way non technical users can validate what is being tested and what is being developed in the company But most important, non technical users had a key role in adding tests to the legacy system helping to understand when a new test was breaking if the test was the problem or if that was a bug in the legacy system because they could read the tests. From there we just needed to configure a continuous integration system and be confident that the new developments would not break anything important.

And this is the experience I want to present, with a step by step of what we did and how the non technical users are involved in the application testing.