Look at what our customers have to say about our services. On the reviews and ratings platform Clutch, our reviews highlight our knack for identifying issues quickly as well as our clear communication with clients and our ability to manage deadlines.
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.
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 >
As software testers we may think that GDPR (General Data Protection Regulation) has nothing to do wi [...]
A recent XBOSoft blog reader wrote in and asked about Healthcare User Acceptance Testing for a healt [...]
Why outsource anything be it a service or production? Why not keep every aspect of the business in house? Two hundred years ago, that approach probably made sense. Today, in the modern economy, globalization and technological advancements have made outsourcing a strategic imperative for all businesses. One question on every CEO’s, VP’s, or even a Managers plate with skin in the game “What need or challenge to our business can be better handled through outsourcing?”This blog addresses seven important reasons why outsourcing software QA & testing makes sense....
Adaptability to a changing environment is the key to survival, so said my father. More recently, brick and mortar has come under siege from the online retailers, What is dramatically different about today, is these online retailers are not really retailers, they are software companies, focused on retail. The backbone of today’s retail business model is ...
Nowadays, API testing forms an important part of testing a web application. This blog post explains what is API testing, how it supplements other software testing approaches, the challenges it brings and how to overcome them.
Mobile User Experience (Mobile UX) is a common subject these days when it comes to discussing how to keep users coming back and how to keep them engaged. I'll be discussing Mobile User Experience in my full-day workshop, Mobile UX is The New StoreFront, at the Practical Software Quality Conference this August 19 in San Diego. What many don't realize is that mobile UX is not just about placing buttons in certain places and having good contrast so people can see (usability), but more about providing an integrated experience specific to the mobile platform and specific to the tasks your users are trying to get done. For performance testing in mobile applications, there are many acceptance criteria or measurements you should examine, but we think these two are the most critical.
When we start working with a client who is in the process of converting, or have converted to agile from waterfall, one of the most common questions is "What Do Testers Do in Agile?" The typical consulting answer is 'it depends'. As much as I hate to give that answer, it really does depend on what agile recipe you are using and the skills of your team.