📚 B is for […]

B is for bugs!

What else would you add?

[LinkedIn & X versions]

B is for boundary analysis

Beta testing
Black-box testing

B is for Banana Bread - Android 1.1

Behaviour Driven Development

Today I learned something new! :banana::bread:

Breakpoint, a nice feature of a debugger.

B is for Biological necessity, something that tends to get forgotten when there’s a really fascinating problem to dig into

B is also for Broken, which is a state too much software can too easily attain despite our best efforts

B is for Better, which is what we want the software we test to become

Browser Compatibility, to ensure software works across different browsers/devices

B for Better Behavioral Testing :100:

‘B’ is for buffer overflow.

B is for Binary chop.

Black-box testing :sweat_smile:
(Business) Benchmark testing
Bug Bounty

This tester loves bannana bread too

BUGS!

I’m surprised that hadn’t come up earlier hehe

We don’t call them Bugs, this word has a negative vibe, we call them Issues LOL :smiley:

B is for “Bugs? Nonsense! It works on my end!”

B is for Biases.

  • What biases might we become self-aware of?
  • How might our biases impact our testing efforts?
  • How does this work for me/you/them?
  • How does this work for someone I have never considered or met?

B is for Belief, a system for making decisions without evidence, that Testers help to dismantle and disprove.

Brave, we have to take the chance to believe in our work and be brave enough to not be ignored for saying no to releases to production on Friday, say no without proper information (acceptance criteria and impacted changes from the code).