Isn't this just a case of 'how do we name things'?
Assuming that we adopt your definition of a Unit Test ...
Given a specific test, do we spend time to catagorize it as a 'Unit Test' or some other type of test? What is the point of making such a distinction?
If a unit of code, for example a function, is given one or more tests that attempt to prove that its logic is working, why is it important that we define these tests as 'Unit' or not? For example, a function that reads an entire text file into a RAM buffer may have one or more tests written to show that that is exactly what is achieves when run. Why split hairs about calling them Unit Tests or not? They are useful and important tests, whether or not they fit your Unit test definition.
How would my coding or testing behaviour change by calling some tests "Unit Tests" and other tests something else?
These are not rhetorical questions as I honestly don't know the answers and would like to improve my knowlege and practice of programming.
Flat View: This topic has 50 replies
on 51 pages
[
«
|
121314151617181920
|
»
]
Previous Topic
