QA Insight: Brent Strange's Software QA blog

Do Loop Until 0: Accidental Burn Down

Brent Strange — Wed, 18 Aug 2010 00:59:00 GMT

Screencast: Automate with VS 2010 Express, WebAii, MbUnit, & C#

Brent Strange — Sun, 01 Aug 2010 08:41:00 GMT

Overview
In this screencast I walk you through doing basic browser setup and automation using a free technology stack: Visual Studio 2010 Express, the WebAii Testing Framework from Telerik, C#, and MbUnit/Gallio. Why this stack you ask? Well, what I'm showing you is a FREE, non-trial, stepping stone to help you do a proof a concept with some leading edge tools in .NET without forking out the money.

One thing that we struggle with in our department is helping those who are interested in doing automation explore the possibility while aligning with technologies the development team is using. The problem is the initial cost of Microsoft's Visual Studio and Telerik's WebUi Test Studio (which uses the WebAii API) is far to much for somebody that is just tinkering (greater than $5000). This technology stack enables you to tinker, but keep in mind you will be missing out on a LOT of features and productivity enablers that come with the product that you pay for. For example with WebUi Test Studio Developer Edition you can get Visual Studio integration which gives recording functionality (a huge productivity enabler) and with Visual Studio Pro the ability to use WebUI project templates, advanced debugging, etc. Ideally, once you've proven out your POC for management you would be able to solicit for the funds for the full product, which in turn would open up another world of collaboration and productivity.

Download

	WMV			iPod/iTunes
	Zune			MP3

The Testing Planet Newspaper is Here!

Brent Strange — Thu, 29 Jul 2010 15:30:00 GMT

The Software Testing Club has done it again! Their quarterly "print", has been redone and now we have "The Testing Planet" as a newspaper! I just got mine in the mail the other day, and I have to say it's pretty dang unique, informative and fun. You too can buy your own Printed Copy, but if you can't find it within yourself to go old school and read the printed paper, you can download it for free here. You should probably buy a copy for safe keeping though, because it contains two of the worlds best QA comics: Cartoon Tester and Do Loop Until 0. Which makes the paper INVALUABLE!

I’m Looking for an Automation Engineer (SDET)

Brent Strange — Mon, 05 Jul 2010 20:56:00 GMT

Go Daddy's Hosting R&D department is looking to hire a Software Automation Engineer/SDET. Check out the job posting here. This is an awesome opportunity my QA friend. Let me tell you why:

You'll be working with me! Uhmm, why so quiet?. not impressed? Never mind I said that then. How about you'll be working at the same company as Danica Patrick then?
You'll be working with cutting edge technology.
Our process is agile (we practice Kanban).
We work on "cloud computing" products.
The opportunity to expand your test and development skills is huge.
The team is tight knit, super smart, we work hard, and yet have fun.
The team is passionate about our products.
As an Automation Engineer you aren't trapped into using one set of test tools or a language. We use what works best and makes sense for the situation.
You'll be in the position to mentor other engineers in the art of automation.
You'll be surrounded by other Automation Engineers which gives you the opportunity to collaborate with equally minded people.
Oh yeah, and Go Daddy in general is awesome place to work, check out the Go Daddy careers page for more info.

You know you want to! Apply here.

Lame Developer Stamp of Approval

Brent Strange — Thu, 01 Apr 2010 11:31:00 GMT

A Great Software Testing Comic: Cartoon Tester

Brent Strange — Wed, 24 Mar 2010 12:53:00 GMT

Fellow tester and cartoonist Andy Glover showed up on the SQA testing cartoon scene earlier this year with his comic strip Cartoon Tester. Andy does a great job in recognizing, mocking, and illustrating the classic tester and developer relationship as well as the general testers' life. When I discovered and read his comic for the first time in the first Software Testing Club magazine I found myself laughing out loud.

The sad, sad truth about software development. It's hilarious! Make sure and subscribe to Andy's comic here.

Do Loop Until 0: Death by 1000 Cuts

Brent Strange — Thu, 11 Mar 2010 20:45:00 GMT

Watir Podcast #32 with guest Brent Strange!

Brent Strange — Tue, 02 Mar 2010 20:33:00 GMT

Watir Podcast #32 is out and in this episode Zeljko and Gregg have me as a guest! In #32, we spend some time talking about how our Hosting Team at GoDaddy uses Watir for website automation, the supporting framework and patterns, and much more. When your ears have a few spare minutes you can get the podcast at WatirPodcast.com and TestingPodcast.com.

Do Loop Until 0: Under the Rug

Brent Strange — Fri, 12 Feb 2010 10:38:00 GMT

Tips for Automation Success: Making Tests Repeatable and Consecutive

Brent Strange — Wed, 10 Feb 2010 04:45:00 GMT

Being able to to run individual tests repeatedly and also being able to run them consecutively is a serious challenge when it comes to automation. I think all automation engineers want it, but some fall prey to not having it due to time constraints, setup and teardown complexity, or system access limitations.

What good is automation when it can't be ran repeatedly, further more running them all at once? Seems like a dumb question, but I've seen plenty of non-repeatable tests or suites written by others, and occasionally have fallen prey myself.

How do I ensure repeatability?

When planning the automation time budget, I allocate at least 15% for building infrastructure. Can't get the time? Fight for it, as an automation engineer it's your job. You have to sell the fact that if you don't have the time to build in the infrastructure for repeatability your tests will be less useful, take longer to setup due to manual intervention, and will eventually crumble into uselessness over time because manual intervention is not something you can easily hand off to another automation engineer or developer.
I start building in repeatability with test #1. This test can often take the longest to write because I'm often times building in the infrastructure needed to run all my tests repeatedly (reusable functions, system access functions (db connections, etc), setup and teardown functions).
When the test is done being developed, I run the test, I run it again, I run it again. repeat and rinse until it passes every time.

How do I ensure I can run all my tests consecutively?

I build each test so that it can be ran independently, which means that when I run them all from a list, no matter which order they are in, they will not interfere with each other. This is why extracting common code into methods, setup and teardown is instrumental; I will reuse it in almost every test.
I try to run all tests after each new test is developed and completed to make sure the new test plays nice with the others. This isn't always possible if you have long running tests, but if they aren't, I definitely do this.
I run them all at least once a day.