tag:blogger.com,1999:blog-9238405.post5312514638964760588..comments2024-03-18T02:04:50.380-07:00Comments on Agile Testing: The Second Law of Automated TestingGrig Gheorghiuhttp://www.blogger.com/profile/17863511617654196370noreply@blogger.comBlogger14125tag:blogger.com,1999:blog-9238405.post-60879894932083225522011-03-03T12:21:28.245-08:002011-03-03T12:21:28.245-08:00Dave -- I have a couple of slides at the end point...Dave -- I have a couple of slides at the end pointing to various tools. I've used all of them successfully in agile projects.Grig Gheorghiuhttps://www.blogger.com/profile/17863511617654196370noreply@blogger.comtag:blogger.com,1999:blog-9238405.post-5532453878624867452011-03-03T12:13:19.468-08:002011-03-03T12:13:19.468-08:00I would like to know what automated tools have wor...I would like to know what automated tools have worked well in an Agile environment, of course with a limited budget. Any ideas will be helpful.DaveTnoreply@blogger.comtag:blogger.com,1999:blog-9238405.post-45895464476667720172009-06-30T07:21:47.058-07:002009-06-30T07:21:47.058-07:00I really agree with your point in "versioned&...I really agree with your point in "versioned" and the way you explained is really good and its so clear and easy to understood the key point in Automating. I got the Automation software to do this process from www.macrotesting.com And it really sounds better to do automation to find that. I really have to cheer you as your post made really sense and its a good advice too.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-9238405.post-14030994159159908142009-06-04T03:36:44.275-07:002009-06-04T03:36:44.275-07:00i'm new to the whole idea of automated testing...i'm new to the whole idea of automated testing but my experience with versioned software and the constraints of manual tests (no time, no tester, no money, error-prone) taught me a lesson: i need, want and demand automated tests. first researches had my boss aboard and now i am in the lucky position to get to write my dissertation on automated testing.<br /><br />my google-voodoo led me to your blog where i found some interesting information and links - thanks for that! :)falcyhttps://www.blogger.com/profile/01544217462014752360noreply@blogger.comtag:blogger.com,1999:blog-9238405.post-36520588726352247182009-05-25T04:26:16.080-07:002009-05-25T04:26:16.080-07:00By the way, one related best practice that I use:
...By the way, one related best practice that I use:<br />If you have a version control system for your software, use it for your automated test suite as well.Arjan Kranenburghttp://www.arjankranenburg.com/noreply@blogger.comtag:blogger.com,1999:blog-9238405.post-70745969586552710702009-05-25T00:31:57.816-07:002009-05-25T00:31:57.816-07:00Ha, that's probably true. That's how I did it in a...Ha, that's probably true. That's how I did it in at least 2 jobs, but just because I didn't want to go into the hassle of convincing managers that wanted a Business Plan first.<br />I just started with some scripts to reduce repetitiveness and make my life easier. Then glued individual scripts together and trying to convince others to use the same tools. By that time, my efforts were highly appreciated, and the tools are still used.<br />It is a pitty though that lot's of people start like that. So recently I have tried to re-design my tools such that they can be more universally applied. A first step is described at:<br />http://www.testtoolinterfaces.com<br /><br />You'll get that beer if I run into you ;-)Arjan Kranenburghttp://www.arjankranenburg.comnoreply@blogger.comtag:blogger.com,1999:blog-9238405.post-46116990063805874892009-05-24T15:57:31.946-07:002009-05-24T15:57:31.946-07:00Arjan -- OK, I'll spill the beans, but you'll have...Arjan -- OK, I'll spill the beans, but you'll have to buy me a beer at some point ;-) <br /><br />I think the First Law of Automated Testing is: JUST DO IT! Start small, and add more and more tests. Pretty soon you'll become test-infected and hopefully your enthusiasm will be shared by other people in your organization.<br /><br />GrigGrig Gheorghiuhttps://www.blogger.com/profile/17863511617654196370noreply@blogger.comtag:blogger.com,1999:blog-9238405.post-88601558331830760652009-05-24T12:09:59.288-07:002009-05-24T12:09:59.288-07:00Nice slides, but I'm still wondering what the firs...Nice slides, but I'm still wondering what the first law is. Or is it that you have to get a beer in the bar before starting to automate?Arjan Kranenburghttp://www.arjankranenburg.comnoreply@blogger.comtag:blogger.com,1999:blog-9238405.post-3474219327916007002009-05-24T09:19:33.487-07:002009-05-24T09:19:33.487-07:00Bignose -- you're right, "revealing bottlenecks" i...Bignose -- you're right, "revealing bottlenecks" is a better description of performance testing.<br /><br />Ned -- I was referring to internal version numbers that I think any respectable Web application would have. As an end user, you don't see them, but internally I'm sure most Web apps deploy based on code from a certain branch, and even have internal code names for their release.<br /><br />GrigGrig Gheorghiuhttps://www.blogger.com/profile/17863511617654196370noreply@blogger.comtag:blogger.com,1999:blog-9238405.post-86590359868447808202009-05-23T16:12:47.541-07:002009-05-23T16:12:47.541-07:00This is a good point. I think by "versioned" you ...This is a good point. I think by "versioned" you mean, "changes over time", or "has more than one release". I make the point only because in web applications, often there are no explicit version numbers. New code gets pushed frequently, often more than once a day. What is flickr's version number, for example?<br /><br />Ironically, it is in these environments that automated regression testing is both more important (because of the frequency of releases) and more difficult (because of using cutting-edge browser techniques, browser incompatibilities, and so on).<br /><br />BTW: thanks for the mention in the slides! :)Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-9238405.post-86526788656777472052009-05-22T05:10:46.251-07:002009-05-22T05:10:46.251-07:00Nice slides, I'm glad you got a good reception fro...Nice slides, I'm glad you got a good reception from the talk.<br /><br />One nit to pick: Your slide on "Performance/load/stress testing" claims that performance tests are about "Eliminating bottlenecks".<br /><br />That's not quite true; testing isn't about *changing* anything, it's about *discovering* what's true. So that might be better expressed as "Revealing bottlenecks".Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-9238405.post-8131910527089880522009-05-21T23:03:49.233-07:002009-05-21T23:03:49.233-07:00Since "You should always develop using a software ...Since "You should always develop using a software versioning tool", your rule becomes "You should use automated testing".<br /><br />- Paddy.Paddy3118https://www.blogger.com/profile/06899509753521482267noreply@blogger.comtag:blogger.com,1999:blog-9238405.post-9080456446830859602009-05-21T21:41:03.479-07:002009-05-21T21:41:03.479-07:00Good Stuff Grig! (as usual)Good Stuff Grig! (as usual)Brandon Burtonhttp://www.inatree.orgnoreply@blogger.comtag:blogger.com,1999:blog-9238405.post-68426939309886033172009-05-21T17:03:18.083-07:002009-05-21T17:03:18.083-07:00Very cogent advice. As most budgets these days ar...Very cogent advice. As most budgets these days are getting thinner and thinner, spending money on repeatable automated testing makes a lot of sense.<br /><br />Thanks for the reinforcement!Mr. Hericushttp://www.hericus.com/noreply@blogger.com