One of the maxims in software testing is that “testing early and testing often” helps avoid the high cost of deploying a software bug. But it’s hard to quantify what that exact cost is because of all of the factors that go into the software development life cycle, including (but not limited to) an organization’s size, the number of customers, and the employees and resources utilized to debug and fix. There are, however, some statistics that we can look at to determine how damaging bugs can be.
All content tagged with "qa"
It could be very debatable that in this day and age there are not that many companies, development shops, agencies or individual developers not using a strategy to keep different versions of the product (from now on I'm going to be referring to product rather than app, site, webpage to streamline the subject) isolated from each other depending on which point of the development process they are reflecting, but (and I'm quoting Mark Twain in this one) "truth is stranger than fiction...", and in this case truth refers to the reality of how the code for the product is managed.
