“The number one reason QA Managers lose their jobs is from failed automation initiatives. Is automation important? Absolutely! Don’t make a rookie mistake and waste your budget only to get negative ROI.” I've seen it first hand. I'd say there are 7 big mistakes that can undermine any automation effort...
Quality assurance is something that is ever present in every industry, ensuring that products are up to snuff and working perfectly. Shouldn’t it be the same for digital products as well? Just as the market for custom software has grown rapidly, so has the need to verify the function and quality of those solutions. We are proud to be providers of a crucial service, one that is only growing in importance in today’s digital economy.As we have been working to ensure the quality of our clients’ products, we have had our own quality verified as well. We are pleased to share that we are now featured as one of the top software application testing firms on Clutch. Clutch is a leading industry resource that uses verified ratings and reviews to help firms find the best vendors for their projects. We were included in their research on the application testing industry, alongside nearly 1,000 other top firms, and are proud to announce that we were listed as sixth overall.
Mark Bentsen, a friend and fellow software QA enthusiast, recently posted on LinkedIn, “The number one reason QA Managers lose their jobs is from failed automation initiatives. Is automation important? Absolutely! Don’t make a rookie mistake and waste your budget only to get negative ROI.” I've seen it first hand. I'd say there are 7 big mistakes that can undermine any automation effort:
Improve Mobile Web Performance - Webinar with Mark Tomlinson and Philip Lew Figuring out how to diag [...]
Practical Test Automation and Performance Testing Webinar Webinar Recording Speakers: Donna McCollum [...]
In Agile, developers, testers and business analysts build a working product through a series of short iterations. At the end of each iteration, the product owner accepts the software as working or not, and the team moves forward to the next iteration. This kind of acceptance is not the same as the User Acceptance Testing (UAT) traditionally done at the end of the development effort (Waterfall) by business users or end users who have the knowledge of the product to check it’s functionality and ensure that it can support them in their daily tasks on the job.UAT is still seen by most as a critical step in assuring quality software and that it meets the needs of end users, however, UAT does not fit neatly into Agile. For those implementing Agile, this often represents a missing link that causes significant pain. In this blog, we discuss how to solve this problem.
A Test case is simply a list of actions that need to be executed to verify a particular functionalit [...]
Incorporating User Acceptance Testing into AgileListen in to this webinar with Philip Lew and Cheney Ma as they discuss the problems with User Acceptance Testing and how to implement in Agile when it appears there is no time as the sprints roll on. The trick is in your process and development of user stories combined with detailed yes/no acceptance criteria and tests. Also see how it's implemented in Jira with SynapseRT as Cheney gives a demonstration of complete traceability by associated epics with user stories, user stories with acceptance criteria and tests with defects. View this XBOSoft webinar to learn more >
Why Do Defects Occur and What Can We Do About Them? We all say that we must ‘learn from our mistakes [...]
What Are The Top 5 Sources of Software Performance Issues Software performance problems are difficul [...]