[SystemSafety] Another question

[Olwen Morgan]

Another baffler:

Lots of developers have software processes that are not truly fit for 
purpose. (A good, simple diagnostic sign is to look at the technical 
effectiveness of error-prevention and -detection measures at each stage 
of the process.) Hardly surprising, then, that in such processes a lot 
of errors are left to be discovered in testing. Now the question:

If your testing keeps on taking longer than you planned, *why do people 
pay only lip-service to adopting coding styles that seek proactively to 
minimise the size of relevant test coverage domains?*

Obviously, the best course is to strength error detection everywhere in 
the process, but actively minimising the size of coverage domains makes 
economic sense if you rely mostly on testing to find bugs.


O

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.techfak.uni-bielefeld.de/mailman/private/systemsafety/attachments/20180920/f157ff31/attachment.html>