Exploratory testing empowers testers to engage with the software. They can examine areas, paths, and options based on their experience and learning. By removing strictures of scripted testing, exploratory testing allows for holistic approach to test design, execution, and analysis. Testers are empowered in the moment of testing, on the device and platform they're using. This […]
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 […]
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.
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 […]
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.
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 […]
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 […]
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.
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?
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.
