Acceptance Testing: The Last Hurdle For The SoftwareWith the development of software, you will always see software testing. New software needs to have many different tests performed before it can be released. One of the types of testing is acceptance testing. Acceptance testing is a form of testing that is performed on software, a system or parts of the system as part of black box testing. Acceptance testing is done prior to the release of the software. It is also referred to by many other names such as functional testing, application testing, confidence testing, final testing, and factory acceptance testing among others. There are two different areas of acceptance testing depending on if the system provider or the customer performs it. When the user or customer becomes the new owner, the customer completes the acceptance testing. In this situation, the acceptance testing is called user acceptance testing, beta testing, or site acceptance testing. Acceptance testing isn't performed until the system is completed, and when it is, it consists of a whole group of tests known as cases. Each case test works on a specific operating part of the features of the system. The result of the test will be based on the boolean 'pass or fail' system. This means that regardless of how good or bad the results are, there is no level of success or failure. The environment where the test is performed is usually as close as possible to the environment where the system will be located. The test cases much each have either data input of the test case or a formal description of what tests will be performed as well as a formal description of the results that are anticipated. The case tests are run with the input data as a form of direction for the testers so they know which guidelines to follow as well as expected results. The results that they get from the case tests are matched up against the expected results. If they match each other completely, that case test is considered as a pass. If not, either the system is rejected or if certain conditions had been agreed upon prior to the testing, it may be accepted. The whole purpose of the test to give confidence to both the sponsor and user that the system is satisfactory for use. The final phase of acceptance testing is also a way to unmask any quality defects that may have been overlooked in prior testing. The final goal of acceptance testing is that once it is completed satisfactorily to both parties, the sponsor will usually sign off saying they are satisfied with the work. When this is signed, both parties have met and honored the contract and the system may be delivered. |