D
D
DarkByte20152018-10-03 13:09:30
Software testing
DarkByte2015, 2018-10-03 13:09:30

What is the difference between functional testing and acceptance testing?

As far as I understood from the docks, the whole difference is that functional tests test the interface without opening a browser (they emulate it somewhere inside), and acceptance tests open a real browser and pierce everything in it. But what is their advantage? Why then not to manage with one functional?

Answer the question

In order to leave comments, you need to log in

2 answer(s)
M
Maxim Timofeev, 2018-10-03
@webinar

https://habr.com/post/344588/

V
Vyacheslav Smirnov, 2018-10-09
@polarnik

In theory, functional and acceptance are different types of classifications.
Acceptance - one of the stages of testing in the classification "according to execution time" or "according to chronology", where there are different types:
* Smoke-test - checking that the application is running and that the main functionality works in it
* Acceptance or entry test - a quick check that the new functionality that is submitted for testing even exists in the application, and the new functionality can be tested. In practice, it is used only if developers and testers are in different departments and developers issue a large percentage of defects for testing, rush and simply delay the time by submitting a raw product for testing. And testers, in order not to waste time on testing underdeveloped versions, came up with such a stage - acceptance testing. Which chronologically comes before the main
one * Main testing - main tests for new functionality
* Retesting - rechecking after fixing defects and getting to know the new functionality better
* Regression - rechecking old and new functionality, usually those blocks that could break when new features were released
. And functional - this is a classification according to the goals of testing, and there are only two types at the top level:
* functional testing - checking compliance with functional requirements
* non-functional testing - checking compliance with non-functional requirements
Classification:
https://github.com/polarnik/TypesOfTesting
https://habr.com/company/npo-comp/blog/223833/
This is in theory. And in practice, people can call familiar words familiar actions. And acceptance testing can mean anything.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question