home Forums Boundary Value Testing Are you a BVA practitioner? How do you do it?

This topic contains 1 reply, has 2 voices, and was last updated by Profile gravatar of Jari Mikael Laakso Jari Mikael Laakso 3 years, 9 months ago.

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
  • #327

    Boundary value analysis or Boundary value testing is the most important aspect in Black Box Testing approaches. But not every tester does that as a dedicated practice.

    If you love to find bugs and surprise your developers with your discovery, then this is where to start.

    Tell us how you do it here.

    Profile gravatar of Jari Mikael Laakso
    Jari Mikael Laakso

    There are quite a lot of things into this. You might have boundaries, such as:
    1) declared boundaries
    2) misdeclared boundaries
    3) boundaries that affect performance/UI/security
    4) language/framework/OS/hardware set boundaries
    5) input/output boundaries
    6) unknown boundaries (e.g. part of code we didn’t know that exists)

    Finding these kind of boundaries is often done either by exploring input and outputs, or revving up tools that are meant to do this. The oversimplified focus to test declared boundaries is limiting the imagination of the tester. Similar with the claim “most bugs happen at boundaries”, which is partially because we focus so much effort on testing those (declared) boundaries. I’m not saying we should not test declared boundaries, but that we should open our minds for other kind of boundaries – and testing.

    EDIT: I almost forgot to add this BVA mindmap from TestInsane, the most insane testing company in the world!

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.