23 Oct 2010 @ 3:48 PM 

As testers we must determine impossible assignments. Not just complaining and creating  discomfort. Most task can be partially impossible and this also has to be dissected.

You may have:

  • A task that is reasonable regarding the project, but not regarding the imposed approach to do the testing.
  • Lack of an oracle, where you don’t have the expected behavior defined properly to know what is a bug.
  • You don’t have a proper environment or tools to perform the testing in a reliable way
  • Misleading or improper documentation
  • Lack of  a proper cycle in the project. Ex: whatever a developer has done is the correct behavior; the rest is misconfiguration or 3rd party issue
  • Difficult environment of some sort in a team

There are a lot of other possible issues that make a project impossible to test or partially impossible. Some situations are resolved with common sense, some need experienced approach.

So before testing is good to determine situations like this and present it.

Posted By: Eusebiu Blindu
Last Edit: 23 Oct 2010 @ 03:48 PM

Categories: General


Responses to this post » (One Total)

  1. Is it possible to encounter the “lack of an oracle”? In the most extreme case, you’d always have your gut feeling.

Post a Comment

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

 Last 50 Posts
  • Users » 2
  • Posts/Pages » 141
  • Comments » 148
Change Theme...
  • VoidVoid
  • LifeLife
  • EarthEarth
  • WindWind
  • WaterWater
  • FireFire
  • LightLight « Default

bug bounties

  • No categories

bug bounty

  • No categories


  • No categories


  • No categories


  • No categories

Classic Tests

  • No categories


  • No categories