This type of testing is done by the engineers sitting in the customer place just after the product is delivered.
Let say Wipro has signed a contract with Fedx to deliver a product on X th day. Assume that a critical bug has occurred just few days before the delivery of the product.
Now if the company asks for more time from the customer, then the company will be accountable for the further billing i.e.company will be accountable/pay the expenses till the product is released.
But the project manager cant delivery the product having bugs on the release date bcoz the customer will not accept the product blindly, instead will the test the product in detail. This verification is done by test engineers. This kind of testing is called as Acceptance Testing.
Almost every company will have its own IT division. If a company wants a software to be developed, it will send the requirements across companies and its own IT division will bid for it.
The company with the best bid and good plan/layout will get the contract and the preference will be given to its own IT division if only it has the best bid or best bid will get the contract.
For Eg: Wipro will do only Functional testing, Integration Testing and System Testing. But Fedx will do Acceptance testing with the other 3 types of testing .
The acceptance testers will have domain knowledge on the product or will hire the domain experts or train them.
Case1: Engineers at the customer place will do acceptance testing based on the real time scenarios, these engineers will have enough domain knowledge.
Case2: If the project is too big and the IT division is too small. The customer doesn't have enough engineers to do acceptance testing, then the product is given to some of the staff of the Fedx (for whom the product is developed) for do testing it for a particular period of time(dummy implementation of real time business takes place). The staff is trained on the product and then they start testing it or experiment it.
Here the acceptance testing is done by a user who is an end user.so it is called as UAT.
The end user uses the product in real time scenarios and tests the application or is the product is working fine without any error before release of the product on the production floor,
Case3: If the customer doesn't have sufficient staff to test the product once it released and customer doesn't have enough budget to hire new engineers or outsource the product for doing AT. In this case, customer will call the wipro engineers to do the acceptance testing who already on domain knowledge and have done testing on the product. The test lead of the customer monitors these engineers who will have to execute the real time scenarios.
Case4: Instead of calling the test engineers, the test lead will go to the company and monitors the test engineers by providing new real time scenarios for testing
Acceptance testing takes 2 to 3 cycles of testing.
Now if the company asks for more time from the customer, then the company will be accountable for the further billing i.e.company will be accountable/pay the expenses till the product is released.
But the project manager cant delivery the product having bugs on the release date bcoz the customer will not accept the product blindly, instead will the test the product in detail. This verification is done by test engineers. This kind of testing is called as Acceptance Testing.
Almost every company will have its own IT division. If a company wants a software to be developed, it will send the requirements across companies and its own IT division will bid for it.
The company with the best bid and good plan/layout will get the contract and the preference will be given to its own IT division if only it has the best bid or best bid will get the contract.
For Eg: Wipro will do only Functional testing, Integration Testing and System Testing. But Fedx will do Acceptance testing with the other 3 types of testing .
The acceptance testers will have domain knowledge on the product or will hire the domain experts or train them.
Case1: Engineers at the customer place will do acceptance testing based on the real time scenarios, these engineers will have enough domain knowledge.
Case2: If the project is too big and the IT division is too small. The customer doesn't have enough engineers to do acceptance testing, then the product is given to some of the staff of the Fedx (for whom the product is developed) for do testing it for a particular period of time(dummy implementation of real time business takes place). The staff is trained on the product and then they start testing it or experiment it.
Here the acceptance testing is done by a user who is an end user.so it is called as UAT.
Case3: If the customer doesn't have sufficient staff to test the product once it released and customer doesn't have enough budget to hire new engineers or outsource the product for doing AT. In this case, customer will call the wipro engineers to do the acceptance testing who already on domain knowledge and have done testing on the product. The test lead of the customer monitors these engineers who will have to execute the real time scenarios.
Hello,
ReplyDeleteThe Article on Acceptance Testing, gives amazing information about it. Thanks for Sharing the information about definition of acceptance testing, For More information check the detail on the User Acceptance Testing here Software Testing Company
Wow, What a Excellent post. I really found this to much informatics. It is what i was searching for.I would like to suggest you that please keep sharing such type of info.Visit here for Penetration testing services
ReplyDelete