Guest Post: How Acquia Tests Software (via uTest)
In case you missed today’s news, uTest announced an exciting new partnership with Acquia, the enterprise guide to Drupal. As part of the deal – which provides their customers with unique access to uTest’s full suite of testing services – Acquia was legally obligated to write a guest post for our blog. Actually, that wasn’t part of the deal, but we were able to get a great guest post from them anyway.
Meet Stellina McKinney – Acquia’s Director of Engineering Services – who is here to discuss how Acquia leverages the uTest community. That’s right, not only is Acquia a uTest partner, they’re also a very active uTest customer. Enjoy the post!
*******
I started at Acquia 6 months ago, having previously worked for larger, process-heavy corporations that sold packaged proprietary, software with long release cycles. Our QA teams consisted of over 50 people (sometimes a lot more), and were always the long pole in the process, whether it was Agile or Waterfall.
Not so at Acquia.
At Acquia, I manage a lean QA team of 4 people (we have another team that tests usability), and we support 5 products. We work in an Agile environment, release every 3 weeks, and meet our quality goals for each sprint.
Our QA testing strategy at Acquia is to perform tests on agile user stories (akin to use-case tests or acceptance tests in Behavior Driven Development). Our goals are to:
- Define the behavior of the system, and not have a previously-coded system define the behavior for us
- Test failure cases so that they won’t affect production
- Stress systems through performance and load automation
- Mix automated and manual testing methods, as they’re complementary (machines are fast and consistent, but people have brains and are unpredictable)
We do this by:
- Listing the scenarios that must succeed for a product to be complete
- Writing automated tests to perform basic success and failure operations
- Engaging a crowd-sourced manual testing platform to examine our product in more depth
How can we do this with only a team of 4? uTest’s crowdsourced testing platform lets us leverage over 45 testers a month, without exceeding my start-up budget.

In the second installment of our Usability Testing series, Inge De Bleecker offers some valuable advice for getting to know your users. Enjoy!
Yet another incredible contest with our favorite little green man – Hopper! This past week, uTesters had to think long and hard and try guess who was under Hopper’s magnifying glass. Once again our uTesters did not cease to amaze us with their originality and creativity. One uTester even guessed that it was uTest’s very own Erica Smith! Other guesses included Bill Gates and Mark Zuckerburg. Overall we had 450 entries to this contest, so I think it’s fair to say that we had people intrigued!
Another week, another great Hopper contest on Facebook! In our second installment, we asked people to tell us what they would like to see under Hopper’s famous magnifying glass. Did we expect a big response? Yes! Did we expect the variations of entries that we received? Definitely not!
We’re happy to announce another new series to the uTest blog (in case you missed it, we introduced the
Our featured uTest guest blogger this month is Elena Houser. Originally from Russia, Elena got her start in IT with UUNet Technologies. Eventually, she caught the testing bug and has been testing for the last 7 years.
When you’ve been testing for a while, you often latch on to a single client who is your main source of employment. They know that you do a good job, and you might have become somewhat of a ‘specialist’ in the areas that concern the client. In some months, 100% of your paycheck might be from hours spent working for this client.
Readers of the uTest Blog should know that ecommerce software (retail apps in particular) are a familiar topic of discussion. We also recently published a whitepaper on the subject, see
Today is Valentine’s Day. You haven’t forgotten, have you? Last minute plans for Valentine’s Day can be difficult to arrange, but don’t fret, uTest has you covered.
How much is that source code in the window? You can find out with





