Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • 5
    how did professor clarify this when you asked them about this? (see also Why do interview questions make poor Software Engineering.SE questions?) Commented Dec 20, 2017 at 13:56
  • "whoever is writing the test generally has a pretty good idea about how the test are going to be implemented" - it's not about whether you know how the test is implemented, but whether you know (white) or not (black) how the thing you are testing is implemented. Commented Dec 20, 2017 at 14:03
  • @Jesper sorry. I meant to say "how the source code is going to be implemented". I have fixed it in the question. Commented Dec 20, 2017 at 14:08
  • 5
    While the implementation does not yet exist, whoever is writing the test generally has a pretty good idea about how the source code is going to be implemented. -- Yes, but the test itself does not. White-box testing means testing something internal to the method or class, like the value of a variable. It doesn't mean that the test writer knows what the code under test looks like. Commented Dec 20, 2017 at 14:24
  • 1
    Related, could be seen as a duplicate: Does TDD formally use black box testing to supplement unit tests Commented Dec 20, 2017 at 18:22