Can a requirement be verified just by white or gray box testing?



  • I've read that if a requirement can't be verified by black-box testing or inspection, then it's not a requirement, but a design specification.

    I'm building a software that makes processing with on images acquired by a camera, and the processing itself should be verified because it is essential for producing the right image presented to the end user.

    However it is very difficult to test this in black-box, even in gray-box, so I wonder if it should be listed as a software requirement? If yes, then is it OK for my software verification to have it verified in white or gray-box testing?


    PS: I'm building medical device software, thus following IEC 62304 standard, that specifies that my software requirements shall be verified through system testing.



  • I've read that if a requirement can't be verified by black-box testing or inspection, then it's not a requirement, but a design specification.

    I don't think that's true. There are plenty of requirements which are difficult-to-impossible to test with black-box techniques; for example, a client-server application might have a requirement that all communications between client and server is encrypted - but black-box testing can't see the communications at all. But that doesn't stop it being a valid requirement.



Suggested Topics

  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2