Catch up on stories from the past week (and beyond) at the Slashdot story archive


Forgot your password?

Comment Re:If you have a giant build, it's not modular eno (Score 1) 128

You can structure your modules and your tests such that you can test them independently, using unit tests and functional tests while mocking other services. This keeps each individual build, likely to be kicked off by a change in the revision control system, to a minimum. Integration tests using all the components together can be kicked off at larger intervals (twice daily, for example). These should always pass if all the individual module tests passed. If not, then your tests are incomplete.

The trouble with doing something right the first time is that nobody appreciates how difficult it was.