3 ms·
I've said it before, but I'll say it again: If the system is used by humans, then it needs to be tested by humans. Ideally but not necessarily not the customer
by somewhereoutth 3y ago
I've said it before, but I'll say it again:
If the system is used by humans, then it needs to be tested by humans. Ideally but not necessarily not the customers.
If it is used by just machines then machine testing is fine.
(Per the article, unit tests are clown coding really - nobody cares)
- kvdveer 3y agoDoes this logic extend to /parts of software/? Most lines of code are not UIs, so they are not used by humans, meaning they should be tested by machines? Do we consider webbrowsers to be humans here?
- somewhereoutth 3y agoThe 'user' being the entity that is using the system at the 'commercial boundary' - where your customer interfaces with your system. So for a web site, it is the human, whereas for a banking API, it is the machine. It may be useful for development purposes to create artificial internal 'commercial boundaries', but unit tests are far too fine grained.