Two MoTacon attendees are on the left. The MoTaacon logo is in the center, and to the right a prompt to Get Your Ticket.
Stale Documentation image
  • Nataliia Burmei's profile image
Documentation that was accurate at the time of writing but has since become outdated due to changes in the system, codebase, or process it describes. In testing, stale documentation is a significant risk because teams may test against expectations that no longer reflect actual system behaviour. Documentation stored in tools like Confluence is particularly vulnerable to going stale when it is disconnected from the development workflow and not actively maintained alongside code changes. The problem is often not that documentation was never written, but that there is no mechanism to keep it current.
Self-Serve Testing image
  • Nataliia Burmei's profile image
An approach to quality in which teams without dedicated quality engineers are equipped with the knowledge, templates, and tooling to make sound testing decisions independently. Rather than requiring a specialist to be present for every significant project or incident, self-serve testing relies on well-designed prompts, charter libraries, and structured guidance that carry quality thinking into conversations and contexts where a quality engineer is not physically present. It is particularly relevant in organisations where quality engineers are significantly outnumbered by delivery teams.
Quality Assistance Model image
  • Nataliia Burmei's profile image
As originally defined by Atlassian, the Quality Assistance Model promotes the ownership of quality and testing by every engineer on the team, regardless of their role. This allows each engineer to develop code, test it, and release it to production without gatekeeping by a quality team or quality engineer.  Then what do testers do? Under the Quality Assistance Model, you use your testing expertise to guide and educate the team, empowering and influencing them to produce high quality software.  Sharing quality and testing responsibilities across the team spreads the testing workload more evenly and gives testers time to: Build testing infrastructure Fill gaps in test automation Explore new tools and techniques  Monitor production performance Conduct exploratory testing, ensuring sapient investigation of your product that automated tests cannot provide Support developers on their team, or even on other teams
Subscribe to our newsletter