Meet 2016’s Mobile Testing Challenges

Over at Ministry of Testing, Rosie Sherry polled the community for their thoughts on the biggest challenges for mobile testers in 2016. Given the breakneck speed of change in technology, I’d expected to see at least one totally new mobile testing challenge to watch out for, or a big change coming down the pipeline that would force testers and QA teams all over to rethink everything.

Instead, you’ll recognize most of these problems, as they’ve come up before and some have even been discussed on our blog here at test IO. One of them, “in the wild testing,” or as we call it here – real world testing – is the cornerstone of test IO’s testing philosophy and the reason for our existence. Continue reading “Meet 2016’s Mobile Testing Challenges”

What we can learn from the iOS update that bricked iPhones

Lapses in quality assurance can turn ground-breaking innovation into deal-breaking embarrassments. Too many of these lapses will knock an innovator off its spot at the top. An example comes from Apple, a global technology leader known for attention to detail and quality for every aspect of its software and hardware development.

Apple product launches are often anticipated as “The Next Big Thing,” but high expectations have a downside: when the Cupertino giant doesn’t deliver something disruptive or unexpected, the technology press and stock market don’t hold back in their criticism. Continue reading “What we can learn from the iOS update that bricked iPhones”

Let Testers Do Terrible Things to Your Code

Jeff Atwood (you may know him as one of the founders of Stack Exchange) writes about how he learned to test his code:

“I believe a key turning point in every professional programmer’s working life is when you realize you are your own worst enemy, and the only way to mitigate that threat is to embrace it. Act like your own worst enemy. Break your UI. Break your code. Do terrible things to your software.

Continue reading “Let Testers Do Terrible Things to Your Code”

Software Testing Myth: Only Test Ready Products

It’s the habit of perfectionists everywhere: only reveal what you’re working on when it’s done or as close to done as possible. Whether it’s a term paper, a painting, a slide deck, or a software product, it’s tempting to keep it under wraps until the due date. But just as with paper- or painting-in-progress, getting feedback and regular checks along the way that what you’re creating meets the requirements means you won’t be stuck with software or slides that no longer match the customer’s needs. You also avoid painting yourself into a corner that will take a lot of work to fix.

Continue reading “Software Testing Myth: Only Test Ready Products”

Running afoul of Brooks’ Law in Quality Assurance

In 1975, Fred Brooks, a manager overseeing the team that was developing OS/360, an IBM operating system, wrote the book, “The Mythical Man-Month.” His observation was that if you add additional workers to a software project that is already behind schedule, you will inadvertently make it even later.

The reason is that the engineers currently working on the project have to divert attention from their work to train new employees. In addition, the communication needed to incorporate additional software developers creates significant overhead that slows the pace of work. Continue reading “Running afoul of Brooks’ Law in Quality Assurance”

Tips on Asking Really Good Questions

Over at StickyMinds, they’ve put together a set of tips on how to ask questions to get answers that improve your software testing. Your first question might be, what does that have to do with good QA and good software testing?

A big part of examining an app, a website, or another piece of software is learning to ask the right questions. By asking the right questions, you learn more about what is expected and unexpected behavior. This helps you figure out what the known (and unknown) boundaries of that product are.

Getting into this mindset is important, not just for software testers but for the people working with them as well. Sometimes you need to ask yourself, what isn’t being tested? What blind spots do we have? What biases do our testers have?

It’s worth it to read all six of the tips, but my favorite are tips 4 & 5: Continue reading “Tips on Asking Really Good Questions”

A new name and a new investor

As you may have noticed, we have a new name: testcloud is now test IO. We’re excited about our new name, we think it reflects who we are and what we do better. We are still the same company and we’re still passionate about testing and excited about helping teams to make software better.

We’re also excited to announce that we’ve raised a new round of funding – Series A – from Turn/River Capital. It’s great to have them on board. You might know them as the folks behind BookFresh (now part of Square), Sucuri, and other great web and SaaS companies.

We’ll use this funding will to expand our team and grow in the U.S. There are a lot of companies out there making software, and we know that test IO can help them do it better.

Michael Downing, the CEO of Tout (one of our first U.S. customers and an online video platform for publishers, content creators and advertisers) had something to say for this occasion:

“Bringing software to market before competitors is critical to our bottom line, but finding bugs before our customers do is critical to our reputation. test IO’s crowd of testers continuously uncovers bugs and usability issues that would normally take much longer to identify internally, allowing us to launch applications on time and worry-free.”

It’s our goal to make everyone’s development process that much faster, more efficient, and worry-free. Today’s economy is driven by mobile apps and software, and developers companies from startups all the way to multinationals are looking for faster ways to test software. test IO provides a platform that developers can manage themselves, yet tap into the speed, quality and efficiency of crowdtesting.

That’s idea the at the foundation of our company – that the smartest and most efficient way to do QA is with continuous testing by humans – and it’s on its way to taking over the world. We’re looking forward to making it the normal way that all software is developed.

If you’re excited about this, get in touch! (We’re hiring)

Continuous Testing Manifesto

Build – Test – Learn… and Repeat!

Continuous testing…

  • combines automated testing and testing with people to ensure full test coverage in real life situations for your products
  • makes the most of computers’ precision and humans’ creativity to find bugs before they can cause damage
  • turns testing with people from the major drag just before shipping into an essential part of development, just like automated testing
  • can be used to solicit tester feedback to improve and shape the product from the beginning of and throughout the development process

Continue reading “Continuous Testing Manifesto”