Goal: Increase automated RefApp test coverage quickly to avoid further valuable dev time being used on repeated manual UI tests (like we did in this list last sprint - that was helpful but won’t last long before we have to test again), and to save ourselves time in the near future. There are a lot of tasks still to do for the RefApp release, and we definitely don’t want to have to repeat manual tests after each code commit.
Proposed steps to achieve this:
Automation Documentation (Urgent): A simple, step-by-step guide on how to write a selenium test, that shows and example and a pattern to follow. @k.joseph could we have this done this week so people could start using this guidance asap?
Design Session: Once the documentation/mini-guide is ready, we can use a weekly design session as a practice time for community devs to join and practice writing selenium tests.
With big frontend changes in our future, it will serve us very well to have lots of community knowledge about how to create and maintain automated UI tests.