Skip to content

some changes #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Ashishkhakurel wants to merge 1 commit into
base: master
Choose a base branch
from
Open

some changes #1

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion src/pages/agile/acceptance-testing/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,7 @@ There are various forms of acceptance testing:
->Alpha Testing

->Beta Testing
->Theta testing

#Acceptance Criteria
Acceptance criteria are defined on the basis of the following attributes
Expand Down Expand Up @@ -125,6 +126,6 @@ A good way of defining which acceptance tests should be written is to add accept
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, this criteria can cover specific business cases that the team wants to solve. This provides a good measurement of work quality.

# my changes
#### More Information:
- [International Software Testing Qualifications Board](http://www.istqb.org/)