How do Junior Testers Advocate Quality?

We are continuing to develop a curriculum for Junior testers based on valuable input from the testing community. Through various activities, we have gathered feedback and identified a comprehensive list of key tasks, which has enabled us to develop this Job Profile.

Currently, we are thoroughly examining each task to identify the essential steps necessary to accomplish them. In this particular post, we are focusing on the task of:

Advocating Quality

We have actively engaged the community through social questions and a task analysis session. As a result, we have compiled the following steps required to fulfil this task effectively.

Understand Quality

  • Research what testing means
    • Look past the ‘assumption that technology works’ as a user/consumer
  • Research what quality means
    • ‘Positive user outcomes’
    • ‘Value to someone that matters’
  • Identify what life as a tester really means in software development
    • May be asked to do the same task repeatedly
      • Intro concept of ‘can something be automated?’
  • Decide what quality and testing means, avoiding misconceptions1
    • Possibly: QA vs QC vs Testing
    • An awareness of how issues can take different paths/root causes
      • Test data
      • Coding error
      • Environment
  • Communicate the importance of understanding business impact from the work that we are doing in testing

Advocate for Quality

  • Establish what quality means to a team
    • Cost of Quality Concept
  • Communicate with teams the theme of quality
    • Everyone has the opportunity to influence quality
      • Positively or negatively
    • Talk not only about one’s ‘attitude’, but also their ‘behavior’
      • It doesn’t matter if everyone in a team say testing is important if nobody actually do proper testing
  • Demonstrate examples of risks to quality
    • Assumptions/short-cuts in process steps and decision points
  • Learn about the users, what is important for them
    • Quantify user/support impact for issue if left unresolved
  • Write a proper bug report
    • What is the impact, why is it important to be fixed

What are your thoughts on this list of steps?

We value the insights and expertise of our testing community, and we want to hear what you think – did we miss anything? Is there anything in the list that doesn’t quite make sense?

Your experiences and perspectives are incredibly valuable. They’ll help us fine-tune our curriculum and make sure it’s useful for real-world scenarios. So, please, share your thoughts and let’s make this curriculum the best it can be!"


During the community session, we put together a list of potentially helpful resources for new testers regarding this topic on a Miro board. Where can I find that information?

@tlacenka you can find the Miro board here: