Skip to main content
Software Engineering

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*

6
  • If you know c#, couldn't you write tests for F# functions written by someone else assuming you know what they're suppose to do and not necessarily how it is done? Commented Feb 23, 2015 at 20:16
  • @JeffO How often does someone write unit tests for code they haven't written? Other than that, technically yes, but see the entire rest of my answer for why this is unlikely in practice. Commented Feb 23, 2015 at 20:17
  • Isn't it better to characterize unit tests as black box tests? While they test the innards of an application, they usually treat the part they test as a black box; unit tests written against implementation details are brittle. Commented Feb 23, 2015 at 20:18
  • 3
    @Doval You can use words in whatever way you wish, but merely being aware of (and primarily interacting with) a very specific class/method/function, the existence and behavior of with is only relevant to the people implementing the software as a whole, makes it a white box test in my book and in every classification I've seen. It doesn't need to poke private variables of the unit under test to be concerned with implementation details. Commented Feb 23, 2015 at 20:21
  • @delnan - If they are doing Test Driven Development (TDD), then all the time. Commented Feb 27, 2015 at 3:02