Improving the QA automation developer experience

[Spark450]

Background

The design system team has received feedback from a QA developer indicating that automating interactions with specific components—such as the goa-date-picker—can be cumbersome, mainly due to the use of multiple nested shadow DOMs. Additionally, the recent workshop focused on improving support for the QA practice and highlighted potential opportunities for improvement, including better documentation, component simplification, and additional tools and resources.

Acceptance criteria

Create research plan: A detailed research plan is created outlining objectives, research questions, target participants, and methods. Consider using this draft as a starting point

Participant recruitment: QA developers from product teams in a variety of ministries are identified and recruited for interviews.

Interviews conducted: Semi-structured interviews are completed with at least 4-5 QA developers.

Data collected and organized: Interview notes and recordings are collected and organized for analysis.

Insights synthesized: Findings from the interviews are synthesized into actionable insights, focusing on documentation gaps, automation challenges, and opportunities for improvement.

Next steps identified: A list of prioritized actions is created to address identified challenges and improve support for the QA practice.