|
The Bugs That Deceived Me Every time we look at the data, we perform an analysis that helps us make decisions—hopefully the right ones. In this article, Gil Zilberfeld describes a few traps where bug data misled him to make bad decisions. These traps are in the data itself, not the tools, and can lead us in the wrong direction.
|
|
|
2013: A Year of Software Development and Testing in Quotes In this roundup of noteworthy quotes from industry experts interviewed in 2013, read about what constitutes effective agile methods, the year in testing techniques, and why you shouldn't put too much trust in the latest and greatest tools.
|
|
|
How to Test Your Website on Multiple Browsers: Four Solutions Compared Robbie Bridgewater writes on the difficulty in finding bugs during testing since no single computer can run all of the major browsers—not to mention the added challenge of testing various mobile operating systems. In this article, Robbie compares four possible solutions to this dilemma.
|
|
|
Wherever You Go: Testing Mobile Applications, Part 2 In part 2 of this interview, Jonathan Kohl discusses testing location-based services, the value of a good social network for crowdsourcing, and how poor optimization practices might literally burn a hole in your pocket.
|
|
|
A Conversation with Rajini Padmanaban Rajini Padmanaban is the director of engagement at QA InfoTech. She will be speaking about crowdsourced software testing at the STAREAST conference in April, so I took this opportunity to learn a bit more about crowdsourced testing and find out why it is better than traditional testing in some projects.
|
|
|
On Beauty, Quality, and Relativity The saying “beauty is in the eye of the beholder” rings true whether you’re staring at a centuries-old painting, listening to a busker’s music reflect off the tiles in a subway station, or testing software. It’s one thing to evaluate quality, but how do we evaluate how we evaluate quality?
|
|
|
Specification by Example: Collaborating on a Scope without High-Level Control Understanding what the business users are trying to achieve can significantly help you focus the project on things that really matter. In this excerpt from Gojko Adzic's book Specification by Example, the author offers some tips for effectively collaborating on the project scope when you don’t have high-level control of the project.
|
|
|
Tester, Know Your Product Should you diligently produce multiple big documents before testing begins? Consultant Fiona Charles argues that you should do that only if you believe that documentation is your product as a tester. If your product is information, you should instead minimize test documentation and engage with the software to build the product your stakeholders are paying for.
|
|
|
Load Test Your Website Before Your Customers Do When you release a website or web application, it’s going to face a lot of very public load testing. If it performs poorly, there’s a good chance that you’re going to lose a lot of customers. Colin Mason offers some tips for load testing in order to ensure a better customer experience.
|
|
|
Pair Programming in the Clink In this personal experience story, Daryl Kulak relates the day he spent behind bars. He was there to participate in a program that pairs prisoners with software developers “from the outside” to explore the art and science of agile software development. “It’s like a code retreat,” Kulak notes, “except it’s inside a prison.”
|
|