Archives
Re: Performance testing and coverage
Submitted by Alexander Podelko on Tue, 11/03/2008 - 07:38. non-functional testing | performance testing | performance testing patternsCan't leave Ainars Galvans' posting unanswered. I think that it touches very important issues I am fighting for long time with, so this post is going beyond just a comment.
It is very interesting that I completely agree with Ainars on most items except final conclusions – which I completely disagree with. I suspect that it is rather terminology difference. So let's start with what I disagree.
It is very interesting that I completely agree with Ainars on most items except final conclusions – which I completely disagree with. I suspect that it is rather terminology difference. So let's start with what I disagree.
Unplanned server outage
Submitted by Opensourcetesting.org - latest news on Tue, 11/03/2008 - 15:42.Open Source Testing experienced some server outage today when the database server went down between 13:00 and 14:30 GMT. Apologies for any inconvenience this caused.
Test Code Is Production Code, And Test Coders Are Developers
Submitted by jason@parlezuml.com (Jason Gorman) on Tue, 11/03/2008 - 16:10.A common objection that I hear to automating UI tests is that user interfaces change.
Which means that they end up having to rewrite a lot of their test code. And we all know what a pain in the beehive that is.
But, as developers, we also know that change is inevitable, and we therefore know that we have to structure our code so that it's as easy to change as possible.
Which means that they end up having to rewrite a lot of their test code. And we all know what a pain in the beehive that is.
But, as developers, we also know that change is inevitable, and we therefore know that we have to structure our code so that it's as easy to change as possible.
"Breaking" code
Submitted by noreply@blogger.com (Michael) on Tue, 11/03/2008 - 20:12.Jason Gorman is an interesting guy, and has a lot to say. I agree with lots of it, especially his iconoclastic position on agilism. This time, I'd like to disagree with two paragraphs in a recent blog entry. The second one first.
But I suspect in 5-10 years' time, as test-driven development becomes more popular and teams become more ambitious in their testing efforts, test developers will be in great demand and will be able to command high salaries. I see them becoming as important as architects are viewed as today. Maybe more so, since they actually add value on a project ;-) (Only kidding)
But I suspect in 5-10 years' time, as test-driven development becomes more popular and teams become more ambitious in their testing efforts, test developers will be in great demand and will be able to command high salaries. I see them becoming as important as architects are viewed as today. Maybe more so, since they actually add value on a project ;-) (Only kidding)
