3 ms·

This seems really really expensive. Say it takes me 10 actions to fully test one feature and all its cases. Spread that across FireFox 3 + 3.5, Safari, and IE

This seems really really expensive. Say it takes me 10 actions to fully test one feature and all its cases. Spread that across FireFox 3 + 3.5, Safari, and IE 6 + 7 + 8, that would take a total of 60 actions for one feature. With a web app that has 20 features testing it once a week I would have to pay $326. What if a test fails, do I have to pay again? I don't see how anybody can use this with such a hefty price tag.

martinkl 17y ago
Just think of the amount of time you'd spend testing all of those manually, and what your time is worth. Go Test It costs hardly anything in comparison.
apinstein 17y ago
I have seen a bunch of these and many are priced at this level, which is around US $0.15 per test. It astounds me as it seems ridiculously high. Most of my automated tests run in about 5 seconds or less. With EC2 prices at about $0.10 per hour, I can't imagine ever using a service with such a high premium. Not only because the price is nominally expensive, but also because it's a commodity service that's being priced at a HUGE premium. For me, I'd consider the service if I could offload my grid testing to the cloud for around $20 / month. That way I could run a bunch of smoke tests after every push to make sure nothing broke and a larger set before commits. But that can get to be a lot of tests especially when you re-run for failures.
modoc 17y ago
Cross-browser testing can be one of the biggest time/money sinks during the QA phase of a web-app release. $326 may not make sense for a small company, but medium to large companies will spend much more than that on manual cross browser testing. A 4 person QA team, assuming average costs (salary, benefits, taxes, office space, hardware, etc...) of $100/hour (which I think is low) burns through $3,200/day. $326 is a drop in the bucket.

3 ms·

This seems really really expensive. Say it takes me 10 actions to fully test one feature and all its cases. Spread that across FireFox 3 + 3.5, Safari, and IE

by oneplusone 17y ago

martinkl 17y ago
Just think of the amount of time you'd spend testing all of those manually, and what your time is worth. Go Test It costs hardly anything in comparison.
apinstein 17y ago
I have seen a bunch of these and many are priced at this level, which is around US $0.15 per test. It astounds me as it seems ridiculously high. Most of my automated tests run in about 5 seconds or less. With EC2 prices at about $0.10 per hour, I can't imagine ever using a service with such a high premium. Not only because the price is nominally expensive, but also because it's a commodity service that's being priced at a HUGE premium. For me, I'd consider the service if I could offload my grid testing to the cloud for around $20 / month. That way I could run a bunch of smoke tests after every push to make sure nothing broke and a larger set before commits. But that can get to be a lot of tests especially when you re-run for failures.
modoc 17y ago
Cross-browser testing can be one of the biggest time/money sinks during the QA phase of a web-app release. $326 may not make sense for a small company, but medium to large companies will spend much more than that on manual cross browser testing. A 4 person QA team, assuming average costs (salary, benefits, taxes, office space, hardware, etc...) of $100/hour (which I think is low) burns through $3,200/day. $326 is a drop in the bucket.