Let’s start with something we can all agree on – a defect is something not working as it should. Now, we like to think of defect-based testing as having radar for a certain kind of bug (or a specific flaw). Instead of using the standard requirements docs or the use cases, we use the defects to base test cases. This whole process is based on taxonomies.
Let’s begin with an analogy about software testing. Suppose for a moment that bugs are like medical conditions (no pun intended). The process we use to identify them is like the medical one: through differential diagnosis. We detect the harmful situation and offer a course of treatment. Yet we are all familiar with situations where things can get complicated, just like in the medical field. In software testing, one of the most challenging situations we can encounter relates to a particular type of errors: the false positives and false negatives. What are they and how do we approach them?
Risk Based Testing is all about evaluating and pointing the likelihood of software failure. What’s the probability that the software will crash upon release? What would the expected impact look like? Think about “know-unknowns” in your software – this is what risk based testing is trying to unearth.
Since it’s Holiday Season we wanted to offer you our own little “gift”. It’s something we came across recently while trying to solve a pressing issue. It’s a Jira add-on by the name of Botron Software Configuration Manager (http://www.botronsoft.com/products/configuration-manager/) and it saved us a lot of headaches. Before we tell you more about it, let’s see how it got on our radar.
Software testing is an integral part of developing products and, as such, managers are always trying to find new ways to manage testing. But software testing is part of a bigger picture, which has to do with the development of new technologies, with trends in IT and business and with the global workforce, among others. In this article, we discuss some of these trends that influence your business and that, if you understand, you can use to your advantage.
Testing is integral to software development and its role is to provide quality assurance for the final product. Without quality assurance, you risk running with a faulty product, which leads to decreased sales, damaged reputation and increased costs with fixing bugs and customer care.
Software testing is crucial for delivering excellent software products, but it can eat away at your resources. Ideally, you need a solution that provides high-quality testing, while also allowing your team to focus on what matters most: software development. Automated testing tools can help you achieve this balance, though choosing the right solution is not easy.
Managers often see software testing as a cost source and go to lengths to cut these costs by compromising on the quality of the testing or by dropping it altogether. In the end, testing does little to actually contribute to accumulating revenue, right? Wrong.
When developing software applications one of the most critical aspects is testing. Neglect this and it may lead to lack of product quality, followed by customer dissatisfaction and ultimately increasing overall costs.