2 ms·
He mentions the importance of automated tested once or twice I think, but it isn't hammered on as a modern Agilist would. But, remember, 1970 was a different wo
by jerf 13y ago
He mentions the importance of automated tested once or twice I think, but it isn't hammered on as a modern Agilist would. But, remember, 1970 was a different world. You may literally have not had room to include unit tests in your code, or literally be unable to afford the sort of abstractions that would enable unit testing, for instance.Other parts of that book talk about the difficulty of squeezing bytes out of pages. A lot of modern Agile practices are not possible back then, or are so different as to be entirely different things. TDD would probably get laughed at by all, for instance. "What, you want me to waste my precious timeshare time to run tests I know are going to fail?"
- pnathan 13y agoI don't have the reference, but I read somewhere several years ago when digging through old journals that regular testing was part of the Project Mercury? Gemini? software development process.
- Someone 13y agohttp://www.testingreferences.com/testinghistory.php http://www.testingreferences.com/testinghistory.php, via Google, leads me to Google: http://books.google.nl/books?id=76rnV5Exs50C&lpg=PA81&ots=o800RpISOY&dq=project%20mercury%20weinberg&pg=PA81#v=onepage&q=project%20mercury%20weinberg&f=false http://books.google.nl/books?id=76rnV5Exs50C&lpg=PA81&ots=o8... "Project Mercury was done with short half-day iterations. [...] Tests were planned and written in advance of each micro-increment"