Embrace the chaos as testers share real-world struggles, celebrate Worldwide Tester Day, and tap into the MoTaverse for positive vibes, support, and fresh ideas.

Scott Kenyon and I are bringing colour to TestBash in our brand new, TestBash jackets. But you will have to wait to see the front.

Explore different mindsets to improve testing, overcome bias, and add more value.

I've been involved in software testing for a while now. I have both ISTQB and Certified Agile Tester training certificates. I've also had the honour of creating the course concept and a significant...

I'm happy to share that I have successfully completed the course and passed the test for Software Testing Essentials (STEC). I wanted to be the first to be STEC Certified but someone else beat me t...

Great episode where we had insights all about STEC - the lessons and topics as part of STEC. More interestingly, I can't miss to mention the coincidence of matching our hosts name and the topic t...

Explore the making of STEC, hear behind-the-scenes stories from its creators, and celebrate how this new certificate challenges the old ISTQB path.

I’m coming from: near Skipton in West Yorkshire, UK My role is: Programme Lead for Software Testing Apprenticeships for BPP University - School of Technology I’d love to meet others who are i...

Level up your accessibility testing by finding out what these three tools do well and what they miss!

Eighteen months, 19 modules, and 59 amazing contributors later, the MoT Software Testing Essentials Certification is complete! Looking back, my favourite part has been seeing so many community m...

Discover how testers are using MCP servers, debate the reality of mandatory AI tracking at work, and celebrate community milestones from STEC to new job wins

Technical documentation in software development refers to any documents, knowledge repositories (such as internal wikis), or architecture and system designs. Even user guides can be technical documentation. They are anything that explains how software works, how to use the software and what technologies the software is made of.As well as explaining the software and possibly hardware involved, it can also guide users, help teams work better together, and improve development, maintenance and further development. All documentation has the risk of becoming out of date, so it is as important to maintain them as it is the software itself.Types of technical documents can include requirements in many forms, architecture schematics and designs. API documentation, troubleshooting guides, code comments, reference documents and user manuals.Testers can gain all sorts of knowledge, insights, and test ideas from them, as well as assessing risks.