Re^3: Needing help on testing

I even know of organizations where design and development of the testing environment begins at the same time as — or even well before — application development.

Those are the ones that never finished their original project, because they spent all the time debugging their tests that have been written by the same people as the actual project code.

perl -e 'use MIME::Base64; print decode_base64("4pmsIE5ldmVyIGdvbm5hIGdpdmUgeW91IHVwCiAgTmV2ZXIgZ29ubmEgbGV0IHlvdSBkb3duLi4uIOKZqwo=");'

Comment on Re^3: Needing help on testing Download Code

Replies are listed 'Best First'.
Re^4: Needing help on testing by choroba (Cardinal) on Oct 31, 2018 at 10:26 UTC
That's not true, actually. At work, we write lots of tests: unit tests, integration tests, and API tests, we have manual testers and QA engineers. Maybe it wasn't the case at the very beginning, but nowadays, any new feature or change must be properly tested. And our original project is kind of finished, or at least our customers pay for it and use it (we've just had the best quarter results in the whole history). ($q=q:Sq=~/;[c](.)(.)/;chr(-\|\|-\|5+lengthSq)`"S\|oS2"`map{chr \|+ord }map{substrSq`S_+\|`\|}3E\|-\|`7**2-3:)=~y+S\|`+$1,++print+eval$q,q,a, [download]	[reply] [d/l]
Re^4: Needing help on testing by Your Mother (Archbishop) on Oct 31, 2018 at 13:59 UTC
I also write a lot of tests. Sometimes before a new feature. It does take quite a bit of time; more time than the actual code in most cases. It also protects against shipping bugs, losing customers, late night emergency patches, the next dev’s insanity, regressions, bad upgrades, doc errors, impossible refactoring time…; and in my current $work industry in particular, it prevents lawsuits. After a year or so, it has amply repaid the initial time sink.	[reply]


P is for Practical
	PerlMonks