Hi Mayasen
Sorry for late response
As per my knowledge, Acceptance testing is done to build confidence in the system, so that the product can be accepted by user.At this level our motive is to check whether we can release the product and not on finding new bug. In other word we can say that acceptance testing is done to satisfy the stakeholder, this stakeholder can be a group of 2 person or a crores of person including user etc...
Some example where acceptance testing is done at different level of testing.
1.) A Commercial Off The Shelf (COTS) software product may be acceptance tested when it is installed or integrated.
2.) Acceptance testing of the usability of a component may be done during component testing.
3.) Acceptance testing of a new functional enhancement may come before system testing.
4.) A large-scale system integration test may come after the acceptance of a system.
Note:
Source : Foundations of software testing By Rex Black, D Graham etc..
Now think of a practical scenario,
Gmail is a web application, It had been installed on some box(server or system) first then application would have been tested exhaustively, when the application seems working fine i.e. system testing and acceptance testing is done it is released in market.
At the time of installation if the application is not installed properly will the developer or tester be able to work on that application? Certainly not. So successful installation of application is required and we can say that installation is successful if it go through acceptance testing to satisfy the stakeholder at that time i.e. developer, tester, the owner of application.
This is my thinking, my view may be wrong, may be right. I am trying to learn more about it.If you disagree mail me at:
dheeraj.silicon@gmail.com
With Regards
Dheeraj