We talk a lot about software testing methodologies around here. And for good reason—they’re a primary component of a consistent and efficient testing and QA organization. But what is a methodology built upon? At Lighthouse, it comes down to 3 things: People, Process, and Tools.
Everyone wants lower costs, shorter schedules, and higher quality in software testing and QA—but you can’t have it all. Upper management wants cost and schedule savings, but you can’t just sacrifice quality, either. Could Risk-Based Testing be the ideal compromise?
Do you want better visibility into the effectiveness of your testing and QA team? Sign up for our upcoming webinar on October 19th to learn what metrics you need to be tracking and how they can improve your testing and QA!
In the grand scheme of things, you’d never think software (and software testing/QA) shares any similarity with an appliance like a washing machine. Well, according to our President and CEO, Jeff Van Fleet, perhaps they’re more alike than you think.
Let’s face it: to the unfamiliar eye, software testing can seem to be a bit abstract. And while a testing company may convincingly “talk the talk”; it can be tough to tell if they’re really “walking the walk”. That’s why transparency matters so much for software testing companies. If you’ve got nothing to hide, why hide it?
Without process, you can’t measure your software testing team. And, without measurement, how can you know their true efficacy?
Let’s face it: everyone tends to look at their work with rose-colored glasses. Unfortunately for IT personnel, this bias is especially dangerous to software testing/QA and development projects at large. When it comes to objectively measuring software quality, success, and more, metrics are king.