Slashdot Mirror
Automated Software QA/Testing?
nailbite writes "Designing and developing software has been my calling ever since I first used a computer. The countless hours/days/months spent on imagining to actualizing is, to me, enjoyable and almost a form of art or meditation. However, one of the aspects of development that sometimes "kills" the fun is testing or QA.
I don't mind standalone testing of components since usually you create a separate program for this purpose, which is also fun. What is really annoying is testing an enterprise-size system from its UIs down to its data tier. Manually performing a complete test on a project of this size sucks the fun out of development. That's assuming all your developers consider development as fun (most apparently don't).
My question is how do you or your company perform testing on large-scale projects? Do you extensively use automated testing tools, and if so, can you recommend any? Or do you still do it the old-fashioned way? (manually operating the UI, going through the data to check every transaction, etc.)"
I keep getting errors following links on slashdot today.
Everyone that disagrees with me is a paid shill
The article is about software testing, and the parent post complained that slashcode isn't tested enough. I second that. Why do we keep getting those 503 errors? Why does the lameness filter forbid posting a short snippet of Perl code to illustrate a point? If slashdot did a halfway decent testing of their code we wouldn't have to live with petty annoyances like those.