System and Acceptance Testing

SoC, KLETU
 System Testing
What is System Testing?
• System Testing (ST) is a black box
testing technique performed to
evaluate the complete system the
system's compliance against
specified requirements. In System
testing, the functionalities of the
system are tested from an end-to-
end perspective.
• It includes both functional and Non-
Functional testing.
Following types of System Testing to be performed for Software Engineering Course
Activity. Choose 3-4 Types of these and write 30 total number of test cases .

• Performance Testing
• Load Testing
• Security Testing
• Database Testing
• Browser/Device Compatibility Testing
• Installation Testing
• Usability Testing / Accessibility Testing
• Any other System types of System Testing related to Non-Functional Requirements
 Acceptance Testing
• Customers test a system to decide whether or not it is
ready to be accepted from the system developers and
deployed in the customer environment. Primarily for
custom systems
• Acceptance test cases are written by the customer.
• customer can refuse to take delivery of the product if their
acceptance test cases do not run properly in the
customer’s own (software and hardware) environment.
 Template for System Testing
Type of System Testing :
Test case Id Input Description Expected output Actual Output

3
Template for Acceptance test plan
Test case Id Input Description Expected output Actual Output

3
 Example: Peer review system
Test Input Description Expected output Actual
case Id Output

1 3.2.1 User creates a Details of New created course is displayed and appears
course in the list of courses on users home page

2 3.2.3 User creates a User will be asked to upload rubrics and specify the
Division/batch peer deadline. Then the details of newly created peer review
review is displayed and added to the list of reviews on user
home page

3 3.2.4 User assigns List of students with their total peer review marks are
individual scores for displayed. Option to set peer review as individual
Division/batch peer score /assign new score as individual score is given.
review Individual score can be submitted and notification is
sent to each student involved in the peer review.
 Difference in System Testing and Acceptance Testing?
System Testing Acceptance Testing

1. System testing is end to end testing 1. Acceptance testing is functionality

performed to check if the software  testing performed to check if the
can i buy provigil online meets the software meets the customer
specified requirements. requirements.

2. Acceptance testing is performed by

2. System testing is performed by independent set of testers and also the
developers and testers.
stakeholders, clients.

3. System Testing can be both 3. Acceptance testing is pure functional

functional and non functional testing testing.
4. In System testing , we test how the 4. In Acceptance testing we check if the
system is behaving a whole, the system is meeting the business needs
functionality and performed are of the organisation, usability of the
checked. product.

5. It is performed with demo data and 5. It is performed with  the actual real
not the production data. time data ,production data.

6. In this testing we test the software

for complete specification including 6. Here we test the software for the
hardware and software, memory and user needs and if user needs are met in
the developed software.
number of users.
7. System Testing comprises of System 7. Acceptance testingcomprises of
Testing and System Integration testing. alpha testing and beta testing.

8. System testing is performed before 8. Acceptance testing is performed

the Acceptance testing. after the System testing.

9. Acceptance testing involves

9. System testing involves non functional testing that is boundary
functional testing that is performance value analysis, equivalence portioning
load and stress testing.
and decision table testing.
10. In System Testing , since it is
performed by group of testers, it would 10. Acceptance Testing contains more
of positive test cases.
contain more negative test cases.

11. The defects found in system testing 11. The defects found in acceptance
can be fixed based on priorities. testing are taken as failure product.

12. Here we test the system for all the 12. Here we check the system for
possible dummy inputs. random inputs.