11
School of Computer Science & Software Engineering Bachelor of Computer Science (Digital Systems Security) CSCI321- Project System Testing – 23 February 2013 Group: SS12/4B Khoo Jun Xiang 4000766 [email protected] Ang Wencan Stephen 4194032 [email protected] Goh Kheng Siang Joel 4187490 [email protected] Lim Sing Hui 4185948 [email protected] Low Jia Hui 4186448 [email protected] Supervisor: Mr Sionggo Jappit Assessor: Mr Tan Kheng Teck

DSS 12 S4 03 System Testing

Embed Size (px)

Citation preview

Page 1: DSS 12 S4 03 System Testing

School of Computer Science & Software Engineering Bachelor of Computer Science (Digital Systems Security)

CSCI321- Project

System Testing – 23 February 2013

Group: SS12/4B

Khoo Jun Xiang 4000766 [email protected]

Ang Wencan Stephen 4194032 [email protected]

Goh Kheng Siang Joel 4187490 [email protected]

Lim Sing Hui 4185948 [email protected]

Low Jia Hui 4186448 [email protected]

Supervisor: Mr Sionggo Jappit

Assessor: Mr Tan Kheng Teck

Page 2: DSS 12 S4 03 System Testing

System Testing Please note that during this phase of testing, the software might not be in its final build, hence there

might be slight difference between some screenshots and the user interface.

Create New Database

For Appendix C (System Test), an additional

database is created to ensure that our Project

could function correctly with different databases

end users might have.

About the Database

The database created is based on the Conceptual

Schema shown on the right

Parent Table - Cue

Page 3: DSS 12 S4 03 System Testing

Child Table - Fury

Child Table - Lucasi

Child Table - Mezz

Page 4: DSS 12 S4 03 System Testing

Child Table - Predator

Successfully Read-in

Expected Outcome:

Program is able to detect Database and display it's

Table

Result:

Program is able to detect Database and display it's

Table

Test: Pass

Successfully Read-in

Expected Outcome: Program is able to display Table's Attribute and

allow user to select it.

Result:

Program is able to display Table's Attribute and

allow user to select it.

Test: Pass

Page 5: DSS 12 S4 03 System Testing
Page 6: DSS 12 S4 03 System Testing

Successfully Read-in

Expected Outcome:

Program is able to read-in Database requirements as

specified by the user.

Result:

Program is able to read-in Database requirements as specified by the user.

Test: Pass

Page 7: DSS 12 S4 03 System Testing

Successfully Add Role

Expected Outcome:

Program is able to allow specified role by user to

access the database.

Result:

Program is able to allow specified role by user to access the database.

Test: Pass

Successfully Select Query

Expected Outcome:

User is able to select the Database and make queries

accordingly.

Result:

User is able to select the Database and make queries accordingly.

Test: Pass

Page 8: DSS 12 S4 03 System Testing

Successfully Generated Query

Expected Outcome:

Program is able to understand User's request and

execute query.

Result:

Program is able to understand User's request and execute query.

Test: Pass

Successfully Generate Report

Expected Outcome:

Program is able to generate report according to User's input.

Result:

Program is able to generate report according to User's input.

Test: Pass

Page 9: DSS 12 S4 03 System Testing

Successfully View Report

Expected Outcome:

User is able to view report made by User previously.

Result:

User is able to view report made by User previously.

Test: Pass

Successfully Export Report

Expected Outcome:

User is able to export report. For our program, we

allow the user to export report to either .txt or .xls format.

Result:

User is able to export report.

Test: Pass

Page 10: DSS 12 S4 03 System Testing

.xls format.

.txt format

Page 11: DSS 12 S4 03 System Testing

Successfully Open Report

Expected Outcome:

User is able to open saved report.

Result:

User is able to open saved report.

Test: Pass