:: QC Boss :: Testing, Independent Software Testing, Manual Testing, Website Testing, Functionality Testing, Usability Testing, QC, QA, UAT

Let us see why system testing and acceptance testing playing the major role in the software testing. Below we can see some important points of System and Acceptance Testing.

SYSTEM TESTING

• System testing performed by developers and/or software testers.
• System testing should be performed before Acceptance Testing.
• System testing will focus on determining whether or not the software specifications have been implemented as specified.
• System testing is done by integrating the component of a system and any defect that occurs in the system is due to the defect in the integration of the system, but not in the individual components.
• These tests check for factors such as Cross-Tool testing, memory management and other operating system factors.

ACCEPTANCE TESTING

• It is performed by user personal and may include assistant by software testers.
• It should focus on input processing, use of the software in the organization, and whether or not the specifications meet the true processing needs of the user.
• It is considered to be the final stage of validation. This is the time to see that the system under test meets the users needs and provides confidence in its use.
• It is the process of comparing a program to its requirements. Acceptance must be performed by the actual user’s and their Assistants including consultants, auditors, internal systems staff, etc.
• The actual software and hardware configuration (or equivalent configuration) must be tested.
• The actual policies, procedures, manuals, operations, organization structure, and controls that will be in place and required to meet the stated objectives of the Systems must be used in the test.

Execute the Acceptance Test Plan

• Objective is to determine whether the acceptance criteria have been met.
• Can be accomplished through reviews, or testing. Determination of which (or both) is used depends on criticality of the software, the size of the program, the resources involved, and the time period over which the software is being developed.

Acceptance decisions need a framework in which to operate:

• Contracts
• Acceptance criteria
• Formal mechanisms
• Periodic reviews

Acceptance Decision

Final acceptance testing is the last opportunity for the user to examine the software for functional, interface, performance, and quality features prior to the final acceptance review.

Typical acceptance decisions include:

• Required changes are accepted before progressing to the next activity.
• Some changes must be made and accepted before further development of that section of the product; other changes may be made and accepted at the next major review.
• Progress may continue and changes may be accepted at the next review.
• No changes are required and progress may continue.

Q) Explain in detail about Acceptance Testing?

Acceptance testing is a customer/user responsibility. However, testers

• Help develop an acceptance test plan.
• Include that plan in the system test plan to avoid test duplication.
• May perform or assist in performing the acceptance test.

Overview of Acceptance Testing

• Acceptance testing is formal testing conducted to determine whether a software system satisfies acceptance criteria.
• Enables buyer to determine whether to accept the system.
• Frequently, the software acceptance testing is only the time buyer is involved in acceptance and the only opportunity to identify deficiencies in a critical software system.
• To reduce risk, the buyer must become involved with software acceptance early in the acquisition process.
• Software acceptance is an incremental process of approving or rejecting software system during development or maintenance, according to how well it satisfies predefined criteria.
• For purposes of acceptance, software maintenance is assumed to share the properties of software development.
• Software acceptance is an incremental process of approving or rejecting software system during development or maintenance, according to how well it satisfies predefined criteria.
• For purposes of acceptance, software maintenance is assumed to share the properties of software development.
• Acceptance Decisions occur at pre-specified times, when the following meet the pre-defined acceptance criteria:

• Processes
• Support tools
• Interim documentation
• Segments of the software
• Total software system

• Final acceptance decision occurs with verification that delivered documentation is adequate and consistent with the executable system and that the complete software system meets all buyer requirements.
• Must occur at end of development process.
• Consists of tests to determine whether the system meets these predetermined criteria:

• Functionality
• Performance
• Quality
• Interface
• Security or safety (may be mandated legally or by nature of the system)

Software acceptance enables

Early detection of software problems (and time for the customer or user to plan for possible late delivery):

• Preparation of appropriate test facilities.
• Early consideration of the user’s needs during software development.
• Ensure user involvement in developing system requirements and acceptance criteria.
• Identify interim and final products for acceptance, their acceptance criteria, and schedule.
• Plan how and by whom each acceptance activity will be performed.
• Plan resources for providing information on which to base acceptance decisions.
• Schedule adequate time for buyer staff to receive and examine products and evaluations prior to acceptance review.
• Prepare the Acceptance Plan.
• Respond to the analyses of project entities before accepting or rejecting.
• Approve the various interim software products against quantified criteria at interim points.
• Perform the final acceptance activities, including formal acceptance testing, at delivery.
• Make an acceptance decision for each product.

Acceptance testing is designed to determine whether the software is fit for use.

The four components of fit are:

Data

The reliability, timeliness, consistency, and usefulness of the data included in the automated application.

People

People should have the skills, training, aptitude, and desire to properly use and interact with the automated application.

Structure

The structure is the proper development of application systems to optimize technology and satisfy requirements.

Rules

The rules are the procedures to follow in processing the data.