gaspersic/freeCodeCamp
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Made capitalization and grammar corrections (#28057)

Browse Source
This commit is contained in:
Yash Kapadia
2018-12-17 15:54:38 -05:00
committed by Christopher McCormack
parent 3fc3fabb0a
commit 1ee2095bd2
1 changed files with 21 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files

43
guide/english/agile/acceptance-testing/index.md
View File

@ -4,9 +4,9 @@ title: Acceptance Testing
## Acceptance Testing ## Acceptance Testing
Acceptance testing, is a testing technique performed to determine whether the software system has met the requirement specifications. The main purpose of this test is to evaluate the system's compliance with the business requirements and verify if it has met the required criteria for delivery to end users. Acceptance testing is a testing technique which determines whether or not the software system has met the requirement specifications. The main purpose of this testing technique is to evaluate the system's compliance with business requirements and verify if it is has met the required criteria for delivery to end users.
In software development, user acceptance testing (UAT) - also called beta testing, application testing, and end user testing - is a phase of software development in which the software is tested in the "real world" by the intended audience. In engineering and its various subdisciplines acceptance testing is a test conducted to determine if the requirements of a specification or contract are met. In software development, user acceptance testing (UAT) - also called beta testing, application testing, and end user testing - is a phase of software development in which the software is tested in the "real world" by the intended audience. In engineering and its various subdisciplines, acceptance testing is a test conducted to determine if the requirements of a specification or contract are met.
There are various forms of acceptance testing: There are various forms of acceptance testing:
@ -64,9 +64,9 @@ Acceptance criteria are defined on the basis of the following attributes:
> - Documentation > - Documentation
## Acceptance Test Plan - Attributes ## Acceptance Test Plan - Attributes
The acceptance test activities are carried out in phases. Firstly, the basic tests are executed, and if the test results are satisfactory then the execution of more complex scenarios are carried out. Acceptance test activities are carried out in phases. First, the basic tests are executed, and if the test results are satisfactory then the execution of more complex scenarios are carried out.
The Acceptance test plan has the following attributes: The acceptance test plan has the following attributes:
> - Introduction > - Introduction
> >
@ -94,7 +94,7 @@ The Acceptance test plan has the following attributes:
> >
> - Resources > - Resources
The acceptance test activities are designed to reach one of the conclusions below: Acceptance test activities are designed to reach one of the following conclusions:
- Accept the system as delivered - Accept the system as delivered
@ -103,7 +103,7 @@ The acceptance test activities are designed to reach one of the conclusions belo
- Do not accept the system - Do not accept the system
## Acceptance Test Report - Attributes ## Acceptance Test Report - Attributes
The Acceptance Test Report has the following attributes: The acceptance test report has the following attributes:
> - Report Identifier > - Report Identifier
> >
@ -117,43 +117,42 @@ The Acceptance Test Report has the following attributes:
> >
> - Approval Decision > - Approval Decision
Acceptance Testing focuses on checking if the developed software meets all the requirements. Its main purpose is to check if the solution developed meets the user expectations. Acceptance Testing focuses on checking if the developed software meets all the requirements. Its main purpose is to check if the solution developed meets user expectations.
Acceptance Testing is a well-established practice in software development. Acceptance Testing is a major part of Functional Testing of your code. Acceptance Testing is a well-established practice in software development. Acceptance Testing is a major part of the Functional Testing of your code.
An Acceptance Test determines if the code performs as expected i.e. produces the expected output, given the expected inputs. An Acceptance Test tests that the code performs as expected (i.e., produces the expected output, given the expected inputs).
An Acceptance Test is used to test relatively bigger functional blocks of software aka Features. Acceptance Tests are used to test relatively large functional blocks of software (i.e., features).
### Example ### Example
You have created a page that requires the user to first enter their name in a dialog box before they can see the content. You have a list of invited users, so any other users entered will return an error. You have created a page that requires the user to first enter their name in a dialog box before they can see the content. You have a list of invited users, so any other user will be returned an error.
There are multiple scenarios here, such as: There are multiple scenarios here, such as:
- Every time you load the page, you must enter your name. - Every time you load the page, you need to enter your name.
- If your name is in the list, the dialog will disappear and you will see the article. - If your name is in the list, the dialog will disappear and you will see the article.
- If your name is not in the list, the dialog box will show an error. - If your name is not in the list, the dialog box will show an error.
You can write Acceptance Tests for each of these sub-features of the bigger dialog box feature. Aside from the code that handles the infrastructure of how the test will be executed, your test for the first scenario could look like (in pseudocode): You can write Acceptance Tests for each of these sub-features of the bigger dialog box feature. Aside from the code that handles the infrastructure of how the test will be executed, your test for the first scenario could look like (in pseudocode):
- Given that the page is opened - Given that the page is opened
- The dialog box should be visible - The dialog box should be visible,
- The dialog box should contain an input box - The dialog box should contain an input box, and
- The input box should have placeholder text "Your name, please!" - The input box should have placeholder text "Your name, please!"
- The dialog box shoud contain a "Submit" button - The dialog box shoud contain a "Submit" button
### Notes ### Notes
- Acceptance Tests can be written in any language and run using various tools available that would take care of the infrastructure mentioned above e.g. Opening a browser, loading a page, providing the methods to access elements on the page, assertion libraries and so on. Acceptance Tests can be written in any language and run using various tools available that would take care of the infrastructure mentioned above (e.g., opening a browser, loading a page, providing the menthods to access elements on the page, assertion libraries and more).
- Every time you write a piece of software that will be used again (even by yourself), it helps to write a test for it. When you yourself or another makes changes to this code, running the tests will ensure that you have not broken existing functionality. Every time you write a piece of software that will be used again (even by yourself), it helps to write a test for it. When you or another person makes changes to this code, running the tests will ensure that you have not broken existing functionality.
- It is usually performed by the users or the Subject Matter Experts. It is also called the User Acceptance Testing (UAT). UAT involves most common real life scenarios. Unlike system testing, it does not focus on the errors or crashes, but on the functionality. UAT is done at the end of the testing life-cycle and will decide if the software is moved to the next environment or not. It is usually performed by the users or the Subject Matter Experts. This is also called User Acceptance Testing (UAT). UAT involves most common real-life scenarios. Unlike system testing, it does not focus on the errors or crashes, but on functionality. UAT is done at the end of the testing life-cycle and will decide if the software is moved to the next environment or not.
- A good way of defining which acceptance tests should be written is to add acceptance criteria to a user story. With acceptance criteria, you can define when a user story is ready to deploy, and the issue completed to your wishes. A good way of defining which acceptance tests should be written is to add acceptance criteria to a user story. With acceptance criteria, you can define when a user story is ready to deploy, and the issue completed to your wishes.
- In an Agile project it is important for the team to have acceptance criteria defined for all user stories. The Acceptance Testing work will use the defined criteria for evaluating the delivered functionality. When a story can pass all acceptance criteria it is complete. In an Agile project, it is important for the team to have acceptance criteria defined for all user stories. The Acceptance Testing work will use the defined criteria for evaluating the delivered functionality. When a story can pass all acceptance criteria, it is complete.
- Acceptance testing can also validate if a completed epic/story/task fulfills the defined acceptance criteria. In contrast to definition of done, these criteria can cover specific business cases that the team wants to solve. This provides a good measurement of work quality. Acceptance testing can also validate if a completed epic/story/task fulfills the defined acceptance criteria. In contrast to the definition of done, this criteria can cover specific business cases that the team wants to solve. This provides a good measurement of work quality.
#### More Information: #### More Information:
- [International Software Testing Qualifications Board](http://www.istqb.org/) - [International Software Testing Qualifications Board](http://www.istqb.org/)