Activity

Quality Engineer
she / they
Quality Coach | Scrum Master | UX Enthusiast | Tech Blogger | International Speaker | Exploratory Tester | Test Strategist | MoT Content Creator
<a href="https://www.ministryoftesting.com/software-testing-glossary/continuous-quality" rel="noopener nofollow">Continuous Quality</a> image
Continuous Quality
<a href="https://www.ministryoftesting.com/software-testing-glossary/test-design" rel="noopener nofollow">Test design</a> image
Test design
<a href="https://www.ministryoftesting.com/memories/cosmo-the-space-duck-s-big-racing-adventure" rel="noopener nofollow">Cosmo the Space Duck's Big Racing Adventure</a> image
Cosmo the Space Duck's Big Racing Adventure
This badge is awarded to members who share a photo memory from the community. image
This badge is awarded to members who share a photo memory from the community.
Can you find Cosmo the Space Duck on their real-life adventure? image
Can you find Cosmo the Space Duck on their real-life adventure?
Can you find Cosmo the Space Duck on their real-life adventure? image
Can you find Cosmo the Space Duck on their real-life adventure?
<div>Cassandra H. Leung shares an idea about syncing Club badges with MoT profiles: Hey MoT.  Thanks for another Community Star and Above and Beyond badge on The Club!  I'm super proud of these, and think it would be great if some of the badges (maybe not all) from The Club also appeared on our MoT profiles.  Or maybe instead of different Club badges, there could be a counter on the profiles of how many Club badges we've earned.<br><br><br>
</div> image
Cassandra H. Leung shares an idea about syncing Club badges with MoT profiles: Hey MoT.&nbsp; Thanks for another Community Star and Above and Beyond badge on The Club!&nbsp; I'm super proud of these, and think it would be great if some of the badges (maybe not all) from The Club also appeared on our MoT profiles.&nbsp; Or maybe instead of different Club badges, there could be a counter on the profiles of how many Club badges we've earned.
This badge is awarded to members who contribute content towards a Ministry of Testing certification. image
This badge is awarded to members who contribute content towards a Ministry of Testing certification.
<div>For me, YAGNI is a great heuristic to help me stay focussed and optimise the work not done.<br><br>For example, it can be very easy to get sucked into a task, like automating a workflow, and start thinking of all the variations you could automate, functions you could make reusable, and fancy frameworks you could explore.  But what are you trying to achieve right now, and what do you need in order to do that?  What's your minimum viable / valuable product in this situation?  If you don't need it now, how likely are you to need it in future?  YAGNI says you ain't gonna need it.  So don't spend time on it right now.  It's great to future-proof a little, and build something that's good to work with, but don't go putting on all the bells and whistles right now.  If you need it in future, you can get / do / create it in future.  For now, take things one step at a time, and get some feedback on what you already have.</div> image
Definitions of You Aren't Gonna Need It (YAGNI)
<div>Glue work is often work which is unloved, yet essential successful teams / projects.  While it's usually not large or innovative, glue work is a collection of smaller contributions which keep things running smoothly.<br><br>Some examples include taking notes, noticing when someone has been missed from an important meeting invite and adding them, or making sure someone responds to an incoming enquiry in a timely manner.  Without this glue work, the team may waste time repeating discussions they've already had, have to postpone important decisions, or cause stakeholders or users to feel unheard or unhappy.<br><br>One great irony of glue work, in my opinion, is that it often goes unappreciated, yet is a sign of leadership, maturity, and being a team player.  For this reason, it's a good idea to keep an eye on how much glue work you're doing, and what you're getting back from it, so as not to end up sacrificing your personal success and happiness for the sake of the team / project.<br><br>For more information on glue work and how to deal with it, check out this talk from Tanya Reilly: https://www.noidea.dog/glue</div> image
Definitions of Glue Work
aving joined my first Salesforce project just over six months ago, we’re now ready to consider automating the UI image
aving joined my first Salesforce project just over six months ago, we’re now ready to consider automating the UI
This badge is awarded to members who confirm their tickets to TestBash Brighton 2025 image
This badge is awarded to members who confirm their tickets to TestBash Brighton 2025
This badge is awarded to members who contribute a new term or an alternative definition to the software testing glossary. image
This badge is awarded to members who contribute a new term or an alternative definition to the software testing glossary.
This badge is awarded to members who Log in to MoT five days in a row. image
This badge is awarded to members who Log in to MoT five days in a row.
<div>In the context of software testing, I think of a specialist as someone who is the go-to person for a particular area / topic / technique, etc. A person who is often associated with something specific, because of the level of skill / experience they have in it. A specialist will typically be able to consult on, educate, and train people on the given topic.</div> image
Definitions of Specialist
<div>In the context of software testing, I’d say a generalist is someone who can do a lit bit of everything, but not to a deep extent. They have basic to good skills in many areas, but no particular area in which they’re highly skilled / experienced.</div> image
Definitions of Generalist
<div>Another way to test in a larger group is to have a bug bash. During a bug bash, lots of people from different disciplines come together in the same space (or call) to test the same system. Bugs can be called out instantly, domain experts can clarify questions immediately, and lots of feedback can be gathered quickly. Usually with a moderator or facilitator collecting the points raised, so there are fewer duplicates and everyone else can focus on testing. It’s really interesting to see how priorities and testing techniques differ, and ideas bounce and grow.<br><br>
</div><div>Bug bashes can be a really fun format which helps to boost morale, and they’re great for getting a lot of testing done quickly, for example, before a significant planned release. If you’re holding a bug bash ahead of a big release or feature launch, you can also theme your bug bashes towards those goals and assign different personas, to give it more fun and focus.</div> image
Definitions of Bug Bash
<div>TestBash is an annual opportunity for testers across the globe - and MoTaverse - to get together in a single place.  More than just a conference, it's a friendly and welcoming place to meet other people who are passionate about testing, quality, and community.  From scheduled talks to planned workshops to spontaneous chats, there are plenty of opportunities to learn and get to know people from the community.  The MoT team take care of participants by organising a diverse range of contributions and contributors, offering accommodations, and providing quiet spaces.  TestBash is truly something special, which has helped to launch speaking careers, bud friendships, and grow testing and quality enthusiasts.</div> image
Definitions of TestBash
<div>Test design is both a creative and scientific process for determining what and how to test. <br><br>The <strong>what</strong> is about making it something that's going to be useful information that's going to actually help someone in at the end of the day. <br><br>For me, the <strong>how</strong> plays a big part in that as well because I've seen that happen where someone maybe thinks that they're testing a certain thing, but the how that they're doing it actually is testing something else.<br><br>The how is important as well.</div> image
Definitions of Test design
A mnemonic I came up with while trying to think of ways to help people test like a tester image
A mnemonic I came up with while trying to think of ways to help people test like a tester
<div>Mutation testing is a method used in the context of automated checks / tests.  Rather than testing the code, mutation testing tests the tests.<br><br>The purpose of automated checks is to detect change.  With mutation testing, one introduces small changes to the code to see whether they are successfully detected.  If they are, the mutation is said to be "killed", but if they are not, then one may have a gap in the coverage of automated checks*.<br><br>One can also use what I call "reverse mutation testing" - changing the test so that it should fail, even though the system under test has not.  This reveals whether the test can actually fail, and whether you are really testing what you think you're testing.<br><br><em>*Side note: A gap in test coverage may be intentional.  It's important to think carefully about one's test strategy, whether 100% code coverage is desired, and on which level(s).</em>
</div> image
Definitions of Mutation testing
<div>In the formal style of pair testing, there’s typically a “navigator”, who decides what to do or investigate, and a “driver”, who directly interacts with the system under test and follows the instructions of the navigator. The pair will typically swap roles at regular intervals, giving both parties a chance to try out their ideas and observe how the other person navigates through the system. In the informal style, who says what to do next and who interacts with the system is less rigid. This gives room for more discussion and ideation. It may also be a little faster, as you can execute and show your ideas directly, without having to find all the words to explain them.</div> image
Definitions of Pair testing
<div>In my experience, there are two main, but distinct, things people mean when they refer to "end to end" testing.<br><br>Some people are referring to the complete <strong>user journey</strong>, from the start of a flow to the finish.<br><br>Others are referring to the <strong>system architecture</strong>, meaning that testing cuts through all involved layers of the system under test.<br><br>Because these two definitions are very different, it's important to understand what is meant by "end-to-end" testing in your specific context, so as to avoid misunderstandings, and meet expectations.</div> image
Definitions of End-to-End Testing
<div>Put extremely simply, a test to me is an experiment; a way of conducting research. I see a lot of cross-over with, and ideas we can draw from, the area of science. I don’t think we need to get super specific about what a test is, because the possibilities are so broad. I think that’s a good thing, and one of the fun things about testing.</div> image
Definitions of Test
Earned through actions that have made the MoT Community a more pleasant and useful place to be. image
Earned through actions that have made the MoT Community a more pleasant and useful place to be.
This badge is awarded to a member who has spoken at a TestBash conference. image
This badge is awarded to a member who has spoken at a TestBash conference.
This badge is awarded to members who have subscribed as Unlimited Members. image
This badge is awarded to members who have subscribed as Unlimited Members.
This badge is awarded to members who represent and promote the MoT community as MoT Ambassadors. image
This badge is awarded to members who represent and promote the MoT community as MoT Ambassadors.
This badge is awarded to those who donate to the MoT Scholarship Fund image
This badge is awarded to those who donate to the MoT Scholarship Fund
This badge is awarded to those who contribute to any Testing Planet episodes. image
This badge is awarded to those who contribute to any Testing Planet episodes.
This badge is awarded to members who have attended a TestBash event. image
This badge is awarded to members who have attended a TestBash event.
<blockquote>
<em>To me, it’s more or less about baking in quality from the start, always having an eye on the state of an SUT and how to improve it as you go along. This would be in contrast to building a thing entirely before thinking about whether or not it actually solves a problem or adds any value or whether anyone would actually want to use it. - </em><strong><em>Cassandra H. Leung</em></strong>
</blockquote> image
Definitions of Continuous Quality
Cassandra H. Leung
Cassandra H. Leung
is Open to Write
<div>Acceptance criteria are a list of points on a work item (often a documented as a ticket in a work tracking tool) that must be completed in order for:</div><ol>
<li>The work item to be considered "done" in the workflow</li>
<li>Stakeholders (e.g., product owner, customer, end users) to accept the work as complete</li>
</ol><div>
<br>It can be helpful to write acceptance criteria in a "given, when, then" format.  For example:<br><strong>Given</strong> I'm not logged into the system,<br><strong>When</strong> I navigate to the My Profile page,<br><strong>Then</strong> I will be prompted to log in<br><br>Acceptance criteria can be used to generate testing ideas, and they can also be tested themselves.  Does the described behaviour make sense in context?  Is this really necessary in order to solve the problem?  Is the implementation method really crucial to the acceptance of this work item?<br><br>One of the best ways to write acceptance criteria is during a collaborative, story shaping meeting, such as Three Hats / Three Amigos or a refinement session, where people from different disciplines are present.  This will help the team to raise questions and concerns as early as possible.</div> image
Definitions of Acceptance criteria
<div>An oracle is a type of heuristic which guides one's reasoning as to what is correct.  They can be useful, but are also fallible.<br><br>For example, one might deem a certain behaviour correct because of a set of acceptance criteria on the ticket which implemented the behaviour.  However, upon speaking with the product owner, one might discover that the requirements have since changed, and the behaviour is now incorrect.  In this case, both the acceptance criteria on the ticket and the discussion with the product owner are reasonable oracles (things on which to base one's assessment), but one is no longer correct.</div> image
Definitions of Oracles
<div>Heuristics are resources or tools you can use most of the time to help you with stuff. It's not always going to be correct, but most of the time, it can help you in some way.</div> image
Definitions of Heuristics
<div>The culture of a company or team is like their collective personality.  Every member of a group contributes to its culture through the way they interact with people, how they work, and even what they don't do.<br><br>For example, if a company was to say, "we have a culture of learning," that might mean that they actively help and mentor one another, see failure as a learning opportunity, and / or take dedicated time each week for focussed learning.  You may notice these are acts, not quotes.  Much like with personality, when it comes to culture, it's not just what you say, it's what you do.<br><br>And much like good quality, good culture is subjective.  A good starting point for assessing a group's culture might be how it makes you feel, and how psychologically safe you feel.</div> image
Definitions of Culture
<div>Risk is about much more than just defects or products. Risk is about impact; consequences; human beings. A risk isn't just a bug that might happen. A risk is something which could have a significant negative impact on real people.</div> image
Definitions of Risks
<div>It's normal for us to have biases - a tendency to lean one way or another, which we may or (more commonly) may not be aware of.  This can affect the judgements and decisions we make in an unreasonable or unfair way.<br><br>Say, for example, you prefer the colour blue over red.  When given the choice to accept one of two people into your team, you may choose the person who is wearing blue over the person who is wearing red, because you like blue better and subconsciously take that to mean the person wearing blue is the better choice.  In reality, the two things have no relation, so it would be unreasonable to make your decision based on this.<br><br>The difficulty is that if you're not aware of this bias, it's very difficult to counteract.  That's why biases can be dangerous, and it's important that we make a conscious effort to try and identify them, and remain open to other, more logical factors to base our judgements and decisions on.<br><br>In software production, biases can cause us to miss potential issues or risks, or make decisions which do not support the quality of the product.  If you have a particular stance on something but you don't know why, or notice a pattern in your behaviour that can't be reasonably explained, there may be biases at play.  Take it as an opportunity to check in with yourself and review which facts are and are not relevant.</div> image
Definitions of Biases
Cassandra H. Leung
Cassandra H. Leung
is Open to Speak
Explore various strategies and mindsets that promote continuous learning image
Explore various strategies and mindsets that promote continuous learning
Boost your career in software testing with the MoT Software Testing Essentials Certificate. Learn essential skills, from basic testing techniques to advanced risk analysis, crafted by industry experts. image
Boost your career in software testing with the MoT Software Testing Essentials Certificate. Learn essential skills, from basic testing techniques to advanced risk analysis, crafted by industry experts.
PowerPoint Karaoke is an improvisation game where each person presents 5 slides to an audience without knowing the contents of the slides or the topic! image
PowerPoint Karaoke is an improvisation game where each person presents 5 slides to an audience without knowing the contents of the slides or the topic!
Cassandra H. Leung
Cassandra H. Leung
registered for:
Join us this year for our worldwide 24 hours online TestBash software testing conference image
Join us this year for our worldwide&nbsp;24 hours online TestBash software testing conference
Cassandra H. Leung
Cassandra H. Leung
registered for:
This badge is awarded to members who have read 10 articles while logged in. image
This badge is awarded to members who have read 10 articles while logged in.
This badge is awarded to members who have subscribed as Professional Members. image
This badge is awarded to members who have subscribed as Professional Members.
Subscribe to our newsletter
We'll keep you up to date on all the testing trends.