Blog
Revenue vs. reputation – what’s the real cost of poor web quality?
It turns out, poor web quality can be pretty expensive. Even more so if you find those pesky bugs after launch. Because according to the Systems Sciences Institute at IBM, the cost to fix an error found after product release was four to five times as much as one uncovered during design and development. ...
A pragmatic approach to test automation
Test automation can be the solution to releasing new features and functionality with reduced time to market. Automation is one of the tools for QA resources to use but at Digivante we firmly believe full automation isn’t the ultimate end goal. You might be thinking, “but automating any test is going to save me ...
How does Digivante augment your QA team?
Many firms struggle to recruit experienced and qualified QA professionals and testers. The market is tough right now and the nature of QA makes it hard to predict resource requirements for projects with certainty. You might employ headcount that’s not fully utilised, or you actually refrain from hiring only to discover you don’t have ...
What is quality engineering and why is it important?
Quality engineering focuses on the introduction of new quality methodologies and the impact they have across the company including cultural and procedural changes. It’s about improving your processes around the way that you deliver quality and affects the whole company. Whilst quality engineering is relevant for any type of product development, in our world ...
What is quality assurance and why does it matter?
For any company with a digital product, quality assurance is the process of ensuring that a new digital product, and its consequent versions, is released without issues for customers and that the product works as intended. In short, it’s to ensure that standards of quality are met. Quality assurance isn’t a single thing. It’s ...
Six simple website testing strategies to beat the bottleneck
By its very definition, “agile” should make things easier, right? It means developers can stay reactive to a business or customer’s needs and update products in regular, incremental chunks. Much less of a headache than frantically scrambling towards one major release, surely. So, what’s the problem? Partly, that chipping away in fortnightly sprints also means ...
