A couple of good posts…

A good post on uTest that gives 8 Tips for Becoming a Dedicated Tester.

Another good post on uTest that lists 5 Myths about Software Testing.

Advertisements

In Response to James Whittaker’s GTAC Post

I found James Whittaker’s latest post on Google’s Test Blog very interesting. To think that we could use a Chrome extension to automate tests that could identify bugs in the UI and take us directly to them is exciting to think about not only for testers but also for developers. Not only would this extension identify the bugs in the UI but it would also record and store all the tests that identified them. It doesn’t get much easier than that! However, like many other tools I’ve seen, this will still probably require the skills and trained eye of an experienced tester to determine what truely is a real bug and what is not. However, having a tool like this would certainly aid the tester in identifying places of concern to make those decisions.

To summarize…great advancements are happening in software testing and I believe the combination of a Chrome extension like this with well designed manual test scripts or exploratory charters would greatly enhance the quality of any web application. I will definitely be keeping my eye on this and see what demonstrations, presentations, or papers are released after GTAC.

Test Automation Resources for Beginners

If anyone has any test automation resources for beginners that they’d recommend or wouldn’t mind me borrowing (if you are local), please send me an e-mail (jward@fusionalliance.com).

Good Article

I just read a post on www.testingreflections.com called “Interviewing Insights and Test Frameworks” by James A. Whittaker. This was a really good article about what James has learned during his interviews for testers at Google. I would say that I use the Fishbowl Framework and Storybook Framework the most. However, I would say that at one time or another I have used each framework James mentions individually or in combination with one of the other frameworks. However, I don’t feel that these are new ideas, just new terms for exploratory and black box testing techniques.

Let me know what you think…