What is User Acceptance Testing (UAT) & Its Different Types?

What is User Acceptance Testing (UAT)?

User Acceptance Testing is a phase of software development in which the developed software is tested in the real environment by the end users. The process is to verify the intended functionality of the developed system on the end user’s perspective emulating real-world scenarios.

In short, User acceptance testingis the process of checking that developed software works for intended users. This may be easy to hear at first, but, practically it is not.

Types of User Acceptance Testing

1. Alpha & Beta Testing: Alpha testing is the type of acceptance testing performed by internal employees or by potential user groups at the developer’s location, prior to the release of the product to customers.
2. Contract Acceptance Testing: In Contract Acceptance Testing, the software developed is tested to meet the specifications and criteria which have been pre-decided and mutually agreed upon in the contract.
3. Regulation Acceptance Testing/Compliance Acceptance Testing: The Regulation Acceptance Testing tests the developed software against certain rules and regulations.
4. Operational Acceptance Testing: Operational Acceptance Testing, also called Operational Readiness or Production Acceptance Testing, ensures that there is a proper workflow for the software that is being used.
5. Black Box Testing: Black Box Testing is time and again classified as functional testing, but to some degree of level, can be considered as a type of User Acceptance Testing.

To read in details, visit original blog post - https://www.bugraptors.com/blog/types-user-acceptance-test/

Read More

QA Role in Agile Methodology

There are responsibilities to be fulfilled by a tester in order to provide the clients/end users with a quality product whilst staying in an agile environment, some of which are:

1. Find and clear out differences in requirement & its documentation:

Agile processes started up with QA when people realized that testers can play an active role in analyzing the first requirements document that comes to them other than simply testing. They are expected to:


2. Be an aqueduct between developers and end users:
You can’t just simply sit and wait for some product to come to you correctly if you are a QA in an Agile environment.


3. Stay alert in planning sessions:

QA needs to actively participate in planning sessions bright from the point of outset to bring and maintain sync between developers and end users.

Continue Reading - https://www.bugraptors.com/blog/responsibilities-of-qa-in-agile/

Read More

Internet for all: Improving accessibility for consumers with disability

The Web and the Internet in whole is an increasingly important resource 
in many aspects of our life which includes: education, employment, 
government, commerce, health care, recreation, and more. It is important 
that the Web be accessible to everyone in order to provide equal access and 
equal opportunity to people with disabilities. An accessible Web can help
 people with disabilities participate more actively in society.

Also, an accessible website is often one of the easiest ways to do business
 with many people with disabilities, for instance, people who cannot read 
print material, people who have difficulty going to a physical store or mall,
 and others. Furthermore, what you do for accessibility overlaps with other
 best practices such as mobile Web design, usability, and search engine optimization (SEO)

An accessible website gives access to information and interaction for many
 people with disabilities. That is, the accessibility barriers to print, audio,
 and visual media can be much more easily overcome through Web 
technologies. Accessibility testing is challenging for testers as they are 
unfamiliar with disabilities so there are different ways of testing. 

Read the full post, here: https://www.bugraptors.com/blog/why-accessibility-testing-matters/

Read More