ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
w
2
TEST LIST – [..Module or System Name..] v 1-0 (build 001A)
3
4
START DATE:
SIGNED BY: ____________________
5
END DATE:
6
TESTED BY:ttd.
7
8
9
NumberFeature NamePICScenarioExpected ResultsActual ResultsStatus
10
Tuliskan nomor fiturTuliskan nama fiturtulis nama anggota yang mengerjakan (hanya boleh 1 orang)Tuliskan daftar skenario yang perlu dijalankan oleh user untuk mengetes fitur terkait.Tuliskan hasil yang diharapkan berdasarkan skenario yang dibuat Diisi oleh asisten saat proses UAT, kolom ini diprotect hanya asisten dan dosen yang bisa editDiisi oleh asisten, apakah fitur: Accepted
Accepted with minor condition,
Accepted with major condition,
Rejected.
11
Pastikan ada skenario positif (basic case jika skenario berhasil).
12
Pastikan ada skenario negatif (alternate case jika flow gagal).
13
Test case dibuat lebih dari satu. Tuliskan data dummy yang perlu dimasukkan. Misal untuk login tuliskan beberapa variasi username dan password.
14
15
16
3Assignment TrackerRevaldy HafizCreate Assignment:

Successful Scenario:

Precondition: User logged in as Student

Steps:
1. User fills out the assignment title, description, study resources, deadline, and tasks.
2. User clicks the "Submit" button.
3. System saves the assignment and redirects the user to the main page.
4. The new assignment appears on the main page with correct details.

Unsuccessful Scenario:

Steps:
1. User fills out only some of the required fields (e.g., title and description but not tasks or study resources).
2. User clicks the "Submit" button.
3. System displays an error message prompting the user to fill in all required fields.		Succesful Scenario:
Assignment is added successfully, and details are displayed on the main page.

Unsuccessful Scenario:
Assignment is not added, and the user is alerted to fill in all required fields.		Same
17
18
sdfsdf
19
20
2. Edit Assignment


Precondition: There is an existing Assignment

Successful Scenario:

1. User navigates to the assignment edit page by clicking the "Edit" button on the main page.
2. User updates the assignment details.
3. User clicks the "Update" button.
4. System saves the changes and redirects the user to the main page.
5. The updated assignment appears on the main page with correct details.

Unsuccessful Scenario:

Steps:
1. User navigates to the assignment edit page.
2. User clears some required fields and clicks the "Update" button.
3. System displays an error message prompting the user to fill in all required fields.		Succesful Scenario:
Assignment is updated successfully, and changes are reflected on the main page and view page.

Unsuccessful Scenario:
Assignment is not updated, and the user is alerted to fill in all required fields.		Same
21
3. Delete Assignment

Precondition: There is an exisiting Assignment
Successful Scenario:

1. User clicks the "Delete" button next to an assignment on the main page.
2. System deletes the assignment and updates the main page.

Unsuccessful Scenario:

Steps:
1. User clicks the "Delete" button next to an assignment.
2. There is a temporary issue with the server or database, preventing the deletion.
3. System attempts to delete the assignment but fails.
Succesful Scenario
Expected Result: Assignment is deleted successfully, and it no longer appears on the main page.

Unsuccessful Scenario:
Expected Result: Assignment is not deleted, and it remains on the main page.
22
4. View Assignment Details

Precondition: There is an existing Assignment

Successful Scenario:

1. User clicks the "View" button next to an assignment on the main page.
2. System displays the assignment details page.

Unsuccessful Scenario:

Steps:
1. User tries to access a non-existent assignment by manipulating the URL.		Succesful Scenario:

Expected Result: Assignment details are displayed correctly.

Unsuccesful Scenario:

Expected Result: System displays an error message
23
5. Complete Task within an Assignment
Successful Scenario:

Preconditions: User is logged in, there is an existing assignment with tasks.
Steps:

1. User navigates to the assignment details page.
2. User clicks the "Mark as Complete" button next to a task.
3. System marks the task as complete and updates the progress.

Unsuccessful Scenario:

Steps:
1. User attempts to mark an already completed task as complete again.		Succesful Scenario:

Expected Result: Task is marked as complete, and progress is updated correctly.

Unsuccessful Scenario:

Expected Result: System prevents the action and shows the task as already complete.
24
6. Mark Assignment as Complete
Successful Scenario:

Preconditions: there is an existing assignment with all tasks completed.
Steps:
1. User navigates to the assignment details page.
2. User clicks the "Complete Assignment" button.
3. System marks the assignment as complete and updates the main page.

Unsuccessful Scenario:

Steps:
1. User attempts to mark an assignment as complete when not all tasks are completed.		Succesful Scenario:

Expected Result: Assignment is marked as complete, and status is updated on the main page.

Unsuccessful Scenario:

Expected Result: System prevents the action and alerts the user to complete all tasks first.		Using "COMPLETED:" as assignment name will automatically consider it completed
25
4View Schedule List (with Student Login)Ardhika Satria Narendra
Positive Scenario:
1. Navigate to the schedule list page.
2. Ensure all schedules are displayed correctly.


Negative Scenario:
1. Try to access the schedule list page without proper authentication 		Positive Scenario:
1. Verify that the page loads successfully and displays a table with the header "Schedule List".
2. The schedule is saved and displayed in the schedule list.

Negative Scenario:
1. Access is denied and redirected to a login page.		Same
26
5Create Schedule (with Student Login)Ardhika Satria Narendra
Positive Scenario:
1. Click the "Add Schedule" button.
2. Fill in the form with valid data and submit.

Negative Scenario:
1. Fill in the form with invalid data (e.g., missing required fields) and submit.		Positive Scenario:
1. The schedule creation form is displayed.
2. The schedule is saved and displayed in the schedule details.

Negative Scenario:
1. An error message is shown, and the schedule is not saved.		Same
27
6Edit Schedule (with Student Login)Ardhika Satria Narendra
Positive Scenario:
1. Click the "Edit" button next to a schedule entry.
2. Modify the schedule data and submit.

Negative Scenario:
1. Modify the schedule data with invalid inputs and submit.
2. Cancel the edit action.		Positive Scenario:
1. The schedule edit form is displayed with existing data.
2. The schedule is updated and displayed in the schedule list.

Negative Scenario:
1. An error message is shown, and the schedule is not updated.
2. The schedule remains in the list and is not edited.		Same
28
7Delete Schedule (with Student Login)Ardhika Satria Narendra
Positive Scenario:
1. Click the "Delete" button next to a schedule entry.
Positive Scenario:
1. The schedule is removed from the list.
2. The schedule is permanently deleted from the database.
Same
29
8View Schedule DetailsArdhika Satria Narendra
Positive Scenario:
1. Click on a schedule entry to view details.
Positive Scenario:
1. Ensure that the page displays all relevant details, including Start Time, End Time, Course Name, and Day of the Week.		Same
30
Dashboard CustomizationFerdinand Raja Kenedy1. Student form
Positive Scenario: 1. Student fill the form correctly, the name is the same as the one logged in right now and no data misssing.		1. Student Form
Successful scenario: Navigated into schedule customization page and student data are saved in the database		Minor mistake in routing for studente form
31
2. Student click submit and navigated into a schedule customization page
32
Negative scenario: 1. Student fill the form uncorrectly, there are missing value or the name that is inputted is not the same as the one logged in

2. Custom Dashboard ( Add Student)
Positive Scenario:
1. Educator navigated into the dashboard, click the add student,

Negative Scenario:
1. The one logged in is not an Educator

3. Custom Dashboard (Delete student)
Positive scenario: Educator press a delete button in students card

4. Custom Dashboard( Delete dashboard)x
Positive Scenario: Educator press a delete dashboard button at the bottom of the page

5. Student List Page (add student):
Positive Scenario:
The one logged in is Educator, press an add student button

Negative Scenario:
The one logged in is not an educator		Unsuccessful scenario: Student will still be on the form page and can't go to other page unless fill the form correctly. Student data will not be saved.

2. Custom Dashboard(add student)
Successful scenario: Can navigated into dashboard page, can add a student, and will be navigated to a student's list page

Unsuccessful Scenario: If the one logged in is not an educator, the user can't go to the dashboard page and student list page.

3. Delete student: The student's card in the dashboard page is deleted

4. Delete Dashboard: All student's card in the dashboard are deleted.

5. Student List Page:
Successful scenario: Will be navigated into student list page, press the add student and will be navigated back to the main dashboard

Unsuccessful Scenario: Will be navigated into student scheduler
33
Feedback FeatureAdam Muhammad1. Add Feedback

Success scenario:
Preconditions: Educator is logged in.
Steps:
Navigate to the "Students Without Feedback" page.
Click "Add Feedback" next to a student.
Fill out the feedback form (title, message, optional document).
Click "Submit".


Unsuccess scenario:

Add Feedback without Required Fields

Steps:
Navigate to the "Add Feedback" form.
Leave the title or message field empty.
Click "Submit".
Expected Result: Form validation errors are displayed, and feedback is not added.		Success scenario:
Expected Result: Feedback is added, and the user is redirected to the feedback list.

Unsuccess scenario:
Expected Result: Form validation errors are displayed, and feedback is not added.		Same
34
Adam Muhammad2. Edit Feedback

Success scenario:

Preconditions: Feedback already exists.
Steps:
Navigate to the "Feedback List" page.
Click "Edit" next to a feedback item.
Modify the feedback details.
Click "Update".


Unsuccess scenario:

Edit Feedback with Empty Fields

Preconditions: Feedback already exists.
Steps:
Navigate to the "Edit Feedback" form.
Clear the title or message field.
Click "Update".
Minor mistake in title and PDF edit
35
Adam Muhammad3. Delete Feedback

Success scenario:

Delete Feedback

Preconditions: Feedback already exists.
Steps:
Navigate to the "Feedback List" page.
Click "Delete" next to a feedback item.
Confirm the deletion.



Unsuccess scenario:

Delete Feedback without Confirmation

Preconditions: Feedback already exists.
Steps:
Navigate to the "Feedback List" page.
Click "Delete" next to a feedback item.
Do not confirm the deletion.
Success scenario:
Expected Result: Feedback is deleted, and it no longer appears in the feedback list.

Unsuccess scenario:
Expected Result: Feedback is not deleted.		Same
36
Adam Muhammad4. View Feedback

Success scenario:

View Feedback List

Preconditions: Educator is logged in.
Steps:
Navigate to the "Feedback List" page.



Unsuccess scenario:

View Feedback List without Proper Authorization

Preconditions: Student is logged in.
Steps:
Attempt to navigate to the "Feedback List" page.
Success scenario:
Expected Result: All feedback entries are displayed with options to edit or delete.

Unsuccess scenario:
Expected Result: Access is denied or restricted, and the student cannot view the feedback list.		Same
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100