Explore how testers cut through AI hype with visualization, community stories, and quality coaching.

Collect and share your impact stories to show your value and support your career growth

It was so great to listen to Twit Episode 103 where we had a talk around being a solo tester in the organisation. Watch out the full episode to understand the challenges, struggle, mindset, conve...

Swap stories of solo testing, discover creative ways to spark quality conversations, and hear how AI and community “QA parties” are shaping modern testing.

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...

A way to record, plan and communicate a piece of work. A ticket can also be called an issue, and can be of different types such as Task, Bug, Story and Epic.Many teams also create custom types of tickets that are relevant for their domain or project. For example, when integrating Test Case Management tools into other work planning tools, you might have types such as Test Case, Test Set and Test Execution.Tickets are often linked either with flat or hierarchical relationships. For example many Stories may belong to an Epic, or a Test Case may Test one or more Stories. Some more generic relationships simply use "related", without specifying the type of relationship. Other relationships might indicate project planning, such as Blocks, or Do After.Tickets typically have at least: A title or summary Description Status There are many other fields a ticket might have, depending on the tool, configuration, domain or project.As a ticket is worked on, it can move though various states, depending on the tools used and their configurations, these state transitions may be gated. For example, you may set it up so tickets in the "To do" status can only transition into "Cancelled" or "In progress". You might also have rules, so certain fields are required to allow a state transition.Some tools allow automations, for example connecting CI systems to ticket management systems, so when a branch is made that refers to the ID of a ticket, the two are linked, so you can see code changes made as part of that ticket. Many other integrations and automations exist.

Celebrate 99 episodes of community connection, hear co-hosts reflect on what they've learned, and get inspired to take the stage yourself.

It's always been amazing to listen to people who come on stage and share their ideas and thoughts in each twit episode. But today's episode was special as it was 99th episode. It was great to see s...

11/09/24 Brighton The evening before Day 1 of TestBash 2024. I love this photo cos it captures the mild chaos of a busy social event. Often my favourite type of event photo. 😃

Discover what’s possible when you shift your testing left and do it well

Ben Dowen aka Full Snack Tester attempting to get some MoT Swag!