test IO Blog

The latest on software testing, QA, and DevOps.

January 13, 2016
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.

Read More
January 7, 2016
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 […]

Read More
December 21, 2015
What is Exploratory Testing?

Exploratory testing is an approach to software testing that emphasizes the engagement of the tester, the unscriptedness of testing, and the tester’s control over what and how to evaluate the software.

Read More
December 15, 2015
Crowdtesting Tip: Close the Feedback Loop

Crowdtesting gives you the chance to get feedback on bugs, usability, and features before you release it to the world. This in-the-wild and real-world evaluation of your app, website, or software is invaluable. There is one thing you can to do to get even better reports from your crowd of testers: answer questions! When you first […]

Read More
December 11, 2015
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 […]

Read More
December 8, 2015
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.

Read More
November 24, 2015
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?

Read More
November 18, 2015
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.

Read More
November 17, 2015
Continuous Testing Manifesto

Build – Test – Learn… and Repeat!

Read More
November 11, 2015
Mobile Fragmentation Sucks: How to Cope

Device fragmentation is here to stay but automated and continuous testing significantly reduce performance concerns and the cost incurred to fix defects.Device fragmentation is a nightmare for developers of all stripes looking to grow their user base. In fact, it’s the kind of problem that only gets worse the more successful your app becomes. The […]

Read More

test IO Newsletter

Subscribe to get the latest updates.

Follow Us

Ship Faster, Sleep Better

Get a Demo
linkedin facebook pinterest youtube rss twitter instagram facebook-blank rss-blank linkedin-blank pinterest youtube twitter instagram