Last year, a team of QA community members; @christine, myself, @ivanc, @jennifer, @janflowers invested in directing our Quality assurance community efforts, the team created a testing prioritisation criteria, a POC etc.
There wasn’t lots of community activity on this project as we had initially thought but there is a rising need of supporting the release process with more automation coverage.
The developed POC added cucumber onto our radar; this was to introduce behavior driven development (BDD) in our QA picture, there was need to work with business people and users in end to end testing and the team advised that adopting a BDD framework was a way forward considering it’s adoptability by others like OpenHIE.
This year our community is preparing a fellowship program to boost our QA for the reference application and we would still want to rightly support everyone’s needs while not using our efforts for what won’t be well adopted. Considering our community comprising of more technical persons who have been picking interest in QA, do you still see the need to proceed with cucumber which adds another layer of complexity to our automation framework in order to involve business people, properly document test cases and provider better reporting? Do you feel like writing both the BDD phrasings (feature descriptions) and automated selenium test cases is a lot more work we are taking up for less benefits or you would find use of this work?