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

'index' (#25183)

Browse Source
This commit is contained in:
rahul kalasuva
2018-12-18 01:48:30 +05:30
committed by Christopher McCormack
parent 52e288423f
commit 5fe30c318f
1 changed files with 24 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@ -6,7 +6,7 @@ title: 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 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.
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 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:
@ -18,6 +18,27 @@ There are various forms of acceptance testing:
> >
> - Beta Testing > - Beta Testing
## List of acceptance-testing frameworks
- Concordion, Specification by example (SbE) framework
- Concordion.NET, acceptance testing in .NET
- Cucumber, a behavior-driven development (BDD) acceptance test framework
- Capybara, Acceptance test framework for Ruby web applications
- Behat, BDD acceptance framework for PHP
- Lettuce, BDD acceptance framework for Python
- Fabasoft app.test for automated acceptance tests
- Framework for Integrated Test (Fit)
- FitNesse, a fork of Fit
- iMacros
- ItsNat Java Ajax web framework with built-in, server based, functional web testing capabilities.
- Mocha, a popular web acceptance test framework based on Javascript and Node.js
- Ranorex
- Robot Framework
- Selenium
- Specification by example (Specs2)
- Watir
- Gauge (software)
## Acceptance Criteria ## Acceptance Criteria
Acceptance criteria are defined on the basis of the following attributes: Acceptance criteria are defined on the basis of the following attributes:
@ -107,8 +128,7 @@ An Acceptance Test is used to test relatively bigger functional blocks of softwa
### 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 users entered will return 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 must 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.
@ -131,7 +151,7 @@ You can write Acceptance Tests for each of these sub-features of the bigger dial
- 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 definition of done, these criteria can cover specific business cases that the team wants to solve. This provides a good measurement of work quality.