The coverage over the user requirements of the different executions are:
| Prompt Technique | Model | EX1 | EX2 | EX3 | EX4 | EX5 | Average | Median | STD Desv |
|---|---|---|---|---|---|---|---|---|---|
| Few -Shot + CoT | GPT 4o | 100 | 100 | 100 | 100 | 100 | 100 | 100 | 0 |
- File:
RQ1-few-shot-cot-generatescenarios-gpt-4o-2024-05-13-2024-07-24-16-40-22-.txt
### Test Scenario 1: Viewing Enrolled Courses
**Objective:** Ensure all users can see the courses they are enrolled in.
**Scenario:**
1. User logs into the application.
2. User navigates to the "My Courses" section.
3. The system displays a list of courses the user is enrolled in.
**Expected Output:**
- The user sees a list of courses they are enrolled in.
### Test Scenario 2: Accessing Course Details
**Objective:** Ensure all users can access any of the courses and see the classes ordered by date.
**Scenario:**
1. User logs into the application.
2. User navigates to the "My Courses" section.
3. User selects a course from the list.
4. The system displays the course details, including a list of classes ordered by date.
**Expected Output:**
- The user sees the course details and a list of classes ordered by date.
### Test Scenario 3: Teacher Creating a Course
**Objective:** Ensure the teacher can create courses with a title and optional image.
**Scenario:**
1. Teacher logs into the application.
2. Teacher navigates to the "Create Course" section.
3. Teacher enters a title for the course.
4. Teacher optionally uploads an image for the course.
5. Teacher submits the form to create the course.
6. The system confirms the course creation and displays it in the teacher's course list.
**Expected Output:**
- The course is created with the specified title and optional image and appears in the teacher's course list.
### Test Scenario 4: Teacher Creating a Class within a Course
**Objective:** Ensure the teacher can create a new class within a course with all required attributes.
**Scenario:**
1. Teacher logs into the application.
2. Teacher navigates to the "My Courses" section.
3. Teacher selects a course.
4. Teacher navigates to the "Create Class" section within the course.
5. Teacher enters the title, description, date and time, invited students, related files, and enables the forum if
desired.
6. Teacher submits the form to create the class.
7. The system confirms the class creation and displays it in the course's class list.
**Expected Output:**
- The class is created with all specified attributes and appears in the course's class list.
### Test Scenario 5: Student Interacting with Courses on Dashboard
**Objective:** Ensure students can interact with courses on their dashboard.
**Scenario:**
1. Student logs into the application.
2. Student navigates to the dashboard.
3. The system displays the courses the student is enrolled in with associated information.
4. Student selects a course with an enabled forum.
5. Student adds a comment to the forum.
6. Student downloads attached files if they exist.
**Expected Output:**
- The student sees the courses with associated information.
- The student can add comments to the forum and download attached files.
### Test Scenario 6: Teacher Conducting a Class
**Objective:** Ensure the teacher can conduct classes with all specified functionalities.
**Scenario:**
1. Teacher logs into the application.
2. Teacher navigates to the "My Classes" section.
3. Teacher starts a class.
4. Teacher shares/block audio and webcam as needed.
5. Teacher views class information including title, duration, attendees, and intervention times.
6. Teacher communicates via chat.
7. Teacher passes and revokes intervention turns to/from students.
8. Teacher ends the class.
**Expected Output:**
- The teacher can start, manage, and end the class with all specified functionalities.
### Test Scenario 7: Student Attending a Class
**Objective:** Ensure students can attend classes with all specified functionalities.
**Scenario:**
1. Student logs into the application.
2. Student navigates to the "My Classes" section.
3. Student enters the classroom when the teacher has started it.
4. Student receives the audio and video feed of the teacher.
5. Student mutes/unmutes the audio and video feed of the teacher.
6. Student views class information including title, duration, and attendees.
7. Student communicates via chat.
8. Student requests and cancels intervention turns.
9. Student shares their audio and webcam when granted speaking request.
**Expected Output:**
- The student can attend and interact in the class with all specified functionalities.
### Test Scenario 8: User Registration with CAPTCHA
**Objective:** Ensure users can register using their email and pass a CAPTCHA.
**Scenario:**
1. User navigates to the registration page.
2. User enters their email and other required information.
3. User completes the CAPTCHA.
4. User submits the registration form.
5. The system confirms the registration and sends a verification email.
**Expected Output:**
- The user is registered and receives a verification email.
### Test Scenario 9: User Login
**Objective:** Ensure users can log in to the application.
**Scenario:**
1. User navigates to the login page.
2. User enters their email and password.
3. User submits the login form.
4. The system authenticates the user and redirects them to the dashboard.
**Expected Output:**
- The user is authenticated and redirected to the dashboard.
### Test Scenario 10: Teacher Editing Course Attributes
**Objective:** Ensure the teacher can edit the attributes of a course at any time.
**Scenario:**
1. Teacher logs into the application.
2. Teacher navigates to the "My Courses" section.
3. Teacher selects a course.
4. Teacher navigates to the "Edit Course" section.
5. Teacher updates the course attributes.
6. Teacher submits the form to save changes.
7. The system confirms the updates and displays the updated course details.
**Expected Output:**
- The course attributes are updated and displayed correctly.
### Test Scenario 11: Teacher Editing Class Attributes
**Objective:** Ensure the teacher can edit the attributes of a class at any time.
**Scenario:**
1. Teacher logs into the application.
2. Teacher navigates to the "My Classes" section.
3. Teacher selects a class.
4. Teacher navigates to the "Edit Class" section.
5. Teacher updates the class attributes.
6. Teacher submits the form to save changes.
7. The system confirms the updates and displays the updated class details.
**Expected Output:**
- The class attributes are updated and displayed correctly.
### Test Scenario 12: User Modifying Profile
**Objective:** Ensure users can modify their profiles.
**Scenario:**
1. User logs into the application.
2. User navigates to the "Profile" section.
3. User updates their username, email, password, and profile image.
4. User submits the form to save changes.
5. The system confirms the updates and displays the updated profile information.
**Expected Output:**
- The profile information is updated and displayed correctly.
### Test Scenario 13: Teacher Adding Course Description
**Objective:** Ensure the teacher can add a description to the courses.
**Scenario:**
1. Teacher logs into the application.
2. Teacher navigates to the "My Courses" section.
3. Teacher selects a course.
4. Teacher navigates to the "Edit Course" section.
5. Teacher adds a description with text, images, and links.
6. Teacher submits the form to save changes.
7. The system confirms the updates and displays the updated course description.
**Expected Output:**
- The course description is updated and displayed correctly.
### Test Scenario 14: User Registration with CAPTCHA
**Objective:** Ensure all users pass a CAPTCHA during registration.
**Scenario:**
1. User navigates to the registration page.
2. User enters their email and other required information.
3. User completes the CAPTCHA.
4. User submits the registration form.
5. The system confirms the registration and sends a verification email.
**Expected Output:**
- The user is registered and receives a verification email.
### Test Scenario 15: Viewing Calendar
**Objective:** Ensure all users have access to a calendar displaying all their classes.
**Scenario:**
1. User logs into the application.
2. User navigates to the "Calendar" section.
3. The system displays a calendar with all the user's classes.
**Expected Output:**
- The user sees a calendar with all their classes.
### Test Scenario 16: Teacher Adding Students to a Course
**Objective:** Ensure the teacher can add students to a course in different ways.
**Scenario:**
1. Teacher logs into the application.
2. Teacher navigates to the "My Courses" section.
3. Teacher selects a course.
4. Teacher navigates to the "Add Students" section.
5. Teacher adds students using their unique email address.
6. Teacher adds students using multiple email addresses.
7. Teacher uploads a file (txt, excel, Word, PDF) to add students.
8. Teacher submits the form to add students.
9. The system confirms the addition of students and displays the updated student list.
**Expected Output:**
- The students are added to the course and displayed in the student list.
### Summary
All user requirements are covered in the test scenarios. No unnecessary steps were identified. Each scenario includes a
complete sequence of steps and the expected outputs.
- File:
RQ1-few-shot-cot-generatescenarios-gpt-4o-2024-05-13-2024-07-24-17-05-38-.txt
**Objective: Ensure all users can see the courses they are enrolled in.**
**Scenario 1: Viewing Enrolled Courses**
1. **Step**: User logs into the application.
- **Expected Output**: User is successfully logged in and redirected to the dashboard.
2. **Step**: User navigates to the "My Courses" section.
- **Expected Output**: A list of courses the user is enrolled in is displayed.
---
**Objective: Ensure all users can access any of the courses and see the classes ordered by date.**
**Scenario 2: Accessing a Course and Viewing Classes**
1. **Step**: User logs into the application.
- **Expected Output**: User is successfully logged in and redirected to the dashboard.
2. **Step**: User navigates to the "My Courses" section.
- **Expected Output**: A list of courses the user is enrolled in is displayed.
3. **Step**: User clicks on a specific course.
- **Expected Output**: The course page is displayed, showing a list of classes ordered by date.
---
**Objective: Ensure the teacher can create courses.**
**Scenario 3: Teacher Creating a Course**
1. **Step**: Teacher logs into the application.
- **Expected Output**: Teacher is successfully logged in and redirected to the dashboard.
2. **Step**: Teacher navigates to the "Create Course" section.
- **Expected Output**: A form to create a new course is displayed.
3. **Step**: Teacher fills in the course title and optionally adds an image.
- **Expected Output**: The course title and image are correctly inputted.
4. **Step**: Teacher submits the form.
- **Expected Output**: The new course is created and added to the list of courses.
---
**Objective: Ensure the teacher can create a new class within a course.**
**Scenario 4: Teacher Creating a Class**
1. **Step**: Teacher logs into the application.
- **Expected Output**: Teacher is successfully logged in and redirected to the dashboard.
2. **Step**: Teacher navigates to a specific course.
- **Expected Output**: The course page is displayed.
3. **Step**: Teacher clicks on "Create Class".
- **Expected Output**: A form to create a new class is displayed.
4. **Step**: Teacher fills in the class details: title, description, date and time, invited students, related files, and
enables the forum.
- **Expected Output**: The class details are correctly inputted.
5. **Step**: Teacher submits the form.
- **Expected Output**: The new class is created and added to the list of classes within the course.
---
**Objective: Ensure students can interact with courses on their dashboard.**
**Scenario 5: Student Interacting with Courses**
1. **Step**: Student logs into the application.
- **Expected Output**: Student is successfully logged in and redirected to the dashboard.
2. **Step**: Student navigates to the "My Courses" section.
- **Expected Output**: A list of courses the student is enrolled in is displayed.
3. **Step**: Student clicks on a specific course.
- **Expected Output**: The course page is displayed, showing a list of classes.
4. **Step**: Student clicks on a specific class.
- **Expected Output**: The class page is displayed, showing the class details.
5. **Step**: Student adds a comment to the forum if it is enabled.
- **Expected Output**: The comment is successfully added to the forum.
6. **Step**: Student downloads attached files if they exist.
- **Expected Output**: The files are successfully downloaded.
---
**Objective: Ensure the teacher can conduct classes.**
**Scenario 6: Teacher Conducting a Class**
1. **Step**: Teacher logs into the application.
- **Expected Output**: Teacher is successfully logged in and redirected to the dashboard.
2. **Step**: Teacher navigates to a specific course and selects a class.
- **Expected Output**: The class page is displayed.
3. **Step**: Teacher starts the class.
- **Expected Output**: The class is successfully started.
4. **Step**: Teacher shares or blocks audio and webcam as needed.
- **Expected Output**: Audio and webcam settings are successfully updated.
5. **Step**: Teacher views class information, including title, duration, attendees, and intervention times.
- **Expected Output**: Class information is correctly displayed.
6. **Step**: Teacher communicates via chat.
- **Expected Output**: Messages are successfully sent and received.
7. **Step**: Teacher passes and revokes intervention turns to/from students.
- **Expected Output**: Intervention turns are successfully managed.
8. **Step**: Teacher ends the class.
- **Expected Output**: The class is successfully ended.
---
**Objective: Ensure students can attend classes.**
**Scenario 7: Student Attending a Class**
1. **Step**: Student logs into the application.
- **Expected Output**: Student is successfully logged in and redirected to the dashboard.
2. **Step**: Student navigates to a specific course and selects a class.
- **Expected Output**: The class page is displayed.
3. **Step**: Student enters the classroom when the teacher has started it.
- **Expected Output**: Student successfully enters the classroom.
4. **Step**: Student receives the audio and video feed of the teacher.
- **Expected Output**: Audio and video feed are successfully received.
5. **Step**: Student mutes the audio and video feed of the teacher if needed.
- **Expected Output**: Audio and video feed are successfully muted.
6. **Step**: Student views class information, including title, duration, and attendees.
- **Expected Output**: Class information is correctly displayed.
7. **Step**: Student communicates via chat.
- **Expected Output**: Messages are successfully sent and received.
8. **Step**: Student requests and cancels intervention turns.
- **Expected Output**: Intervention turns are successfully managed.
9. **Step**: Student shares their audio and webcam if their speaking request is granted.
- **Expected Output**: Audio and webcam are successfully shared.
---
**Objective: Ensure users can register using their email.**
**Scenario 8: User Registration**
1. **Step**: User navigates to the registration page.
- **Expected Output**: Registration form is displayed.
2. **Step**: User fills in the registration details, including email.
- **Expected Output**: Registration details are correctly inputted.
3. **Step**: User completes the CAPTCHA.
- **Expected Output**: CAPTCHA is successfully completed.
4. **Step**: User submits the registration form.
- **Expected Output**: User is successfully registered and redirected to the login page.
---
**Objective: Ensure users can log in to the application.**
**Scenario 9: User Login**
1. **Step**: User navigates to the login page.
- **Expected Output**: Login form is displayed.
2. **Step**: User fills in the login details.
- **Expected Output**: Login details are correctly inputted.
3. **Step**: User submits the login form.
- **Expected Output**: User is successfully logged in and redirected to the dashboard.
---
**Objective: Ensure the teacher can edit the attributes of a course.**
**Scenario 10: Teacher Editing a Course**
1. **Step**: Teacher logs into the application.
- **Expected Output**: Teacher is successfully logged in and redirected to the dashboard.
2. **Step**: Teacher navigates to a specific course.
- **Expected Output**: The course page is displayed.
3. **Step**: Teacher clicks on "Edit Course".
- **Expected Output**: A form to edit the course is displayed.
4. **Step**: Teacher updates the course attributes.
- **Expected Output**: The course attributes are correctly updated.
5. **Step**: Teacher submits the form.
- **Expected Output**: The course is successfully updated.
---
**Objective: Ensure the teacher can edit the attributes of a class.**
**Scenario 11: Teacher Editing a Class**
1. **Step**: Teacher logs into the application.
- **Expected Output**: Teacher is successfully logged in and redirected to the dashboard.
2. **Step**: Teacher navigates to a specific course and selects a class.
- **Expected Output**: The class page is displayed.
3. **Step**: Teacher clicks on "Edit Class".
- **Expected Output**: A form to edit the class is displayed.
4. **Step**: Teacher updates the class attributes.
- **Expected Output**: The class attributes are correctly updated.
5. **Step**: Teacher submits the form.
- **Expected Output**: The class is successfully updated.
---
**Objective: Ensure users can modify their profiles.**
**Scenario 12: User Modifying Profile**
1. **Step**: User logs into the application.
- **Expected Output**: User is successfully logged in and redirected to the dashboard.
2. **Step**: User navigates to the "Profile" section.
- **Expected Output**: The profile page is displayed.
3. **Step**: User updates their profile details: username, email, password, and profile image.
- **Expected Output**: Profile details are correctly updated
.
4. **Step**: User submits the form.
- **Expected Output**: The profile is successfully updated.
---
**Objective: Ensure the teacher can add a description to the courses.**
**Scenario 13: Teacher Adding Course Description**
1. **Step**: Teacher logs into the application.
- **Expected Output**: Teacher is successfully logged in and redirected to the dashboard.
2. **Step**: Teacher navigates to a specific course.
- **Expected Output**: The course page is displayed.
3. **Step**: Teacher clicks on "Edit Course".
- **Expected Output**: A form to edit the course is displayed.
4. **Step**: Teacher adds a description to the course, including text with different formats, images, or links.
- **Expected Output**: The course description is correctly added.
5. **Step**: Teacher submits the form.
- **Expected Output**: The course is successfully updated with the new description.
---
**Objective: Ensure all users pass a CAPTCHA during registration.**
**Scenario 14: CAPTCHA Verification During Registration**
1. **Step**: User navigates to the registration page.
- **Expected Output**: Registration form is displayed.
2. **Step**: User fills in the registration details.
- **Expected Output**: Registration details are correctly inputted.
3. **Step**: User completes the CAPTCHA.
- **Expected Output**: CAPTCHA is successfully completed.
4. **Step**: User submits the registration form.
- **Expected Output**: User is successfully registered and redirected to the login page.
---
**Objective: Ensure all users have access to a calendar displaying all their classes.**
**Scenario 15: Viewing Calendar**
1. **Step**: User logs into the application.
- **Expected Output**: User is successfully logged in and redirected to the dashboard.
2. **Step**: User navigates to the "Calendar" section.
- **Expected Output**: A calendar displaying all the user's classes is displayed.
---
**Objective: Ensure the teacher can add students to a course.**
**Scenario 16: Teacher Adding Students to a Course**
1. **Step**: Teacher logs into the application.
- **Expected Output**: Teacher is successfully logged in and redirected to the dashboard.
2. **Step**: Teacher navigates to a specific course.
- **Expected Output**: The course page is displayed.
3. **Step**: Teacher clicks on "Add Students".
- **Expected Output**: A form to add students is displayed.
4. **Step**: Teacher adds students using their unique email address, multiple email addresses, or a file (txt, excel,
Word, PDF).
- **Expected Output**: Students are correctly added to the course.
5. **Step**: Teacher submits the form.
- **Expected Output**: The course is successfully updated with the new students.
- File:
RQ1-few-shot-cot-generatescenarios-gpt-4o-2024-05-13-2024-07-24-17-07-17-.txt
### Test Scenario 1: Viewing Enrolled Courses
**Objective:** Verify that all users can see the courses they are enrolled in.
**Steps:**
1. User logs into the application.
2. User navigates to the dashboard.
3. System displays a list of courses the user is enrolled in.
**Expected Output:**
- The dashboard shows a list of courses the user is enrolled in.
**User Requirements Covered:** (1)
### Test Scenario 2: Accessing Courses and Viewing Classes
**Objective:** Verify that all users can access any of the courses and see the classes ordered by date.
**Steps:**
1. User logs into the application.
2. User navigates to the dashboard.
3. User clicks on a course.
4. System displays the classes within the course, ordered by date.
**Expected Output:**
- The course page shows a list of classes ordered by date.
**User Requirements Covered:** (2)
### Test Scenario 3: Teacher Creating a Course
**Objective:** Verify that the teacher can create courses with a title and an optional image.
**Steps:**
1. Teacher logs into the application.
2. Teacher navigates to the course creation page.
3. Teacher enters a course title.
4. Teacher optionally uploads an image.
5. Teacher clicks on the "Create Course" button.
6. System creates the course and displays it in the teacher's dashboard.
**Expected Output:**
- The new course appears in the teacher's dashboard with the provided title and image.
**User Requirements Covered:** (3)
### Test Scenario 4: Teacher Creating a Class within a Course
**Objective:** Verify that the teacher can create a new class within a course with all specified attributes.
**Steps:**
1. Teacher logs into the application.
2. Teacher navigates to the course page.
3. Teacher clicks on "Create New Class."
4. Teacher enters the class title, description, date, and time.
5. Teacher selects invited students.
6. Teacher uploads related files.
7. Teacher enables the forum for the class.
8. Teacher clicks on "Create Class."
9. System creates the class and displays it within the course.
**Expected Output:**
- The new class appears within the course with all provided attributes.
**User Requirements Covered:** (4)
### Test Scenario 5: Student Interacting with Courses on Dashboard
**Objective:** Verify that students can interact with courses on their dashboard.
**Steps:**
1. Student logs into the application.
2. Student navigates to the dashboard.
3. Student clicks on a course.
4. System displays the course information.
5. Student adds a comment to the forum (if enabled).
6. Student downloads attached files (if they exist).
**Expected Output:**
- The course information is displayed.
- The comment is added to the forum.
- The files are downloaded successfully.
**User Requirements Covered:** (5)
### Test Scenario 6: Teacher Conducting Classes
**Objective:** Verify that the teacher can conduct classes with all specified functionalities.
**Steps:**
1. Teacher logs into the application.
2. Teacher navigates to the class page.
3. Teacher clicks on "Start Class."
4. Teacher shares/blocks audio and webcam.
5. Teacher views class information.
6. Teacher communicates via chat.
7. Teacher passes/revokes intervention turn to/from students.
8. Teacher ends the class.
**Expected Output:**
- The class starts, and all functionalities work as expected.
**User Requirements Covered:** (6)
### Test Scenario 7: Student Attending Classes
**Objective:** Verify that students can attend classes with all specified functionalities.
**Steps:**
1. Student logs into the application.
2. Student navigates to the class page.
3. Student enters the classroom when the teacher has started it.
4. Student receives the audio and video feed of the teacher.
5. Student mutes the audio and video feed of the teacher.
6. Student views class information.
7. Student communicates via chat.
8. Student asks for/cancels an intervention turn.
9. Student shares their audio and webcam if their speaking request is granted.
**Expected Output:**
- The student can attend the class and all functionalities work as expected.
**User Requirements Covered:** (7)
### Test Scenario 8: User Registration
**Objective:** Verify that users can register using their email and pass a CAPTCHA.
**Steps:**
1. User navigates to the registration page.
2. User enters their email and other required information.
3. User completes the CAPTCHA.
4. User clicks on "Register."
5. System registers the user and sends a confirmation email.
**Expected Output:**
- The user is registered, and a confirmation email is sent.
**User Requirements Covered:** (8), (14)
### Test Scenario 9: User Login
**Objective:** Verify that users can log in to the application.
**Steps:**
1. User navigates to the login page.
2. User enters their email and password.
3. User clicks on "Login."
4. System logs the user in and redirects to the dashboard.
**Expected Output:**
- The user is logged in and redirected to the dashboard.
**User Requirements Covered:** (9)
### Test Scenario 10: Teacher Editing Course Attributes
**Objective:** Verify that the teacher can edit the attributes of a course at any time.
**Steps:**
1. Teacher logs into the application.
2. Teacher navigates to the course page.
3. Teacher clicks on "Edit Course."
4. Teacher updates the course attributes.
5. Teacher clicks on "Save Changes."
6. System updates the course attributes.
**Expected Output:**
- The course attributes are updated successfully.
**User Requirements Covered:** (10)
### Test Scenario 11: Teacher Editing Class Attributes
**Objective:** Verify that the teacher can edit the attributes of a class at any time.
**Steps:**
1. Teacher logs into the application.
2. Teacher navigates to the class page.
3. Teacher clicks on "Edit Class."
4. Teacher updates the class attributes.
5. Teacher clicks on "Save Changes."
6. System updates the class attributes.
**Expected Output:**
- The class attributes are updated successfully.
**User Requirements Covered:** (11)
### Test Scenario 12: User Modifying Profile
**Objective:** Verify that users can modify their profiles.
**Steps:**
1. User logs into the application.
2. User navigates to the profile page.
3. User updates their username, email, password, and profile image.
4. User clicks on "Save Changes."
5. System updates the user's profile.
**Expected Output:**
- The user's profile is updated successfully.
**User Requirements Covered:** (12)
### Test Scenario 13: Teacher Adding Course Description
**Objective:** Verify that the teacher can add a description to the courses.
**Steps:**
1. Teacher logs into the application.
2. Teacher navigates to the course page.
3. Teacher clicks on "Edit Course."
4. Teacher adds a description with text, images, and links.
5. Teacher clicks on "Save Changes."
6. System updates the course description.
**Expected Output:**
- The course description is updated successfully.
**User Requirements Covered:** (13)
### Test Scenario 14: User Accessing Calendar
**Objective:** Verify that all users have access to a calendar displaying all their classes.
**Steps:**
1. User logs into the application.
2. User navigates to the calendar page.
3. System displays a calendar with all the user's classes.
**Expected Output:**
- The calendar displays all the user's classes.
**User Requirements Covered:** (15)
### Test Scenario 15: Teacher Adding Students to a Course
**Objective:** Verify that the teacher can add students to a course using different methods.
**Steps:**
1. Teacher logs into the application.
2. Teacher navigates to the course page.
3. Teacher clicks on "Add Students."
4. Teacher adds students using their unique email address.
5. Teacher adds students using multiple email addresses.
6. Teacher uploads a file (txt, excel, Word, PDF) with student information.
7. Teacher clicks on "Add."
8. System adds the students to the course.
**Expected Output:**
- The students are added to the course successfully.
**User Requirements Covered:** (16)
- File:
RQ1-few-shot-cot-generatescenarios-gpt-4o-2024-05-13-2024-07-24-17-09-04-.txt
## System Testing Scenarios
### Scenario 1: Viewing Enrolled Courses
**Objective:** Ensure all users can see the courses they are enrolled in.
**Steps:**
1. User logs into the application.
2. User navigates to the dashboard.
3. User views the list of enrolled courses.
**Expected Output:**
- The dashboard displays a list of courses the user is enrolled in.
**User Requirements Covered:** (1)
---
### Scenario 2: Accessing Courses and Viewing Classes
**Objective:** Ensure all users can access any of the courses and see the classes ordered by date.
**Steps:**
1. User logs into the application.
2. User navigates to the dashboard.
3. User clicks on a course.
4. User views the list of classes ordered by date.
**Expected Output:**
- The course page displays a list of classes ordered by date.
**User Requirements Covered:** (2)
---
### Scenario 3: Teacher Creating a Course
**Objective:** Ensure the teacher can create courses with a title and an optional image.
**Steps:**
1. Teacher logs into the application.
2. Teacher navigates to the course creation page.
3. Teacher enters a title for the course.
4. Teacher optionally uploads an image for the course.
5. Teacher submits the form to create the course.
**Expected Output:**
- The new course is created and displayed on the teacher's dashboard.
**User Requirements Covered:** (3)
---
### Scenario 4: Teacher Creating a Class within a Course
**Objective:** Ensure the teacher can create a new class within a course with all required attributes.
**Steps:**
1. Teacher logs into the application.
2. Teacher navigates to the course page.
3. Teacher clicks on "Create New Class."
4. Teacher enters the title, description, date and time, invited students, related files, and enables the forum.
5. Teacher submits the form to create the class.
**Expected Output:**
- The new class is created and displayed within the course.
**User Requirements Covered:** (4)
---
### Scenario 5: Student Interacting with Courses on Dashboard
**Objective:** Ensure students can interact with courses on their dashboard.
**Steps:**
1. Student logs into the application.
2. Student navigates to the dashboard.
3. Student views the associated information for each course.
4. Student adds comments to the forum if enabled.
5. Student downloads attached files if they exist.
**Expected Output:**
- The dashboard displays course information.
- The student can add comments to the forum.
- The student can download attached files.
**User Requirements Covered:** (5)
---
### Scenario 6: Teacher Conducting Classes
**Objective:** Ensure the teacher can conduct classes with all specified functionalities.
**Steps:**
1. Teacher logs into the application.
2. Teacher navigates to the class page.
3. Teacher starts the class.
4. Teacher shares/blocks audio and webcam as needed.
5. Teacher views class information.
6. Teacher communicates via chat.
7. Teacher passes/revokes intervention turn to/from students.
8. Teacher ends the class.
**Expected Output:**
- The class is conducted with all functionalities working as specified.
**User Requirements Covered:** (6)
---
### Scenario 7: Student Attending Classes
**Objective:** Ensure students can attend classes with all specified functionalities.
**Steps:**
1. Student logs into the application.
2. Student navigates to the class page.
3. Student enters the classroom when the teacher has started it.
4. Student receives/mutes the audio and video feed of the teacher.
5. Student views class information.
6. Student communicates via chat.
7. Student requests/cancels intervention turn.
8. Student shares audio and webcam if speaking request is granted.
**Expected Output:**
- The student can attend and interact in the class with all functionalities working as specified.
**User Requirements Covered:** (7)
---
### Scenario 8: User Registration with CAPTCHA
**Objective:** Ensure users can register using their email and pass a CAPTCHA.
**Steps:**
1. User navigates to the registration page.
2. User enters email and other required information.
3. User completes the CAPTCHA.
4. User submits the registration form.
**Expected Output:**
- The user is registered and can log in to the application.
**User Requirements Covered:** (8), (14)
---
### Scenario 9: User Login
**Objective:** Ensure users can log in to the application.
**Steps:**
1. User navigates to the login page.
2. User enters email and password.
3. User submits the login form.
**Expected Output:**
- The user is logged in and redirected to the dashboard.
**User Requirements Covered:** (9)
---
### Scenario 10: Teacher Editing Course Attributes
**Objective:** Ensure the teacher can edit the attributes of a course at any time.
**Steps:**
1. Teacher logs into the application.
2. Teacher navigates to the course page.
3. Teacher clicks on "Edit Course."
4. Teacher updates the course attributes.
5. Teacher submits the form to save changes.
**Expected Output:**
- The course attributes are updated and displayed on the course page.
**User Requirements Covered:** (10)
---
### Scenario 11: Teacher Editing Class Attributes
**Objective:** Ensure the teacher can edit the attributes of a class at any time.
**Steps:**
1. Teacher logs into the application.
2. Teacher navigates to the class page.
3. Teacher clicks on "Edit Class."
4. Teacher updates the class attributes.
5. Teacher submits the form to save changes.
**Expected Output:**
- The class attributes are updated and displayed on the class page.
**User Requirements Covered:** (11)
---
### Scenario 12: User Modifying Profile
**Objective:** Ensure users can modify their profiles.
**Steps:**
1. User logs into the application.
2. User navigates to the profile page.
3. User updates username, email, password, and profile image.
4. User submits the form to save changes.
**Expected Output:**
- The profile is updated with the new information.
**User Requirements Covered:** (12)
---
### Scenario 13: Teacher Adding Course Description
**Objective:** Ensure the teacher can add a description to the courses.
**Steps:**
1. Teacher logs into the application.
2. Teacher navigates to the course page.
3. Teacher clicks on "Edit Course."
4. Teacher adds a description with text, images, or links.
5. Teacher submits the form to save changes.
**Expected Output:**
- The course description is updated and displayed on the course page.
**User Requirements Covered:** (13)
---
### Scenario 14: User Viewing Calendar
**Objective:** Ensure all users have access to a calendar displaying all their classes.
**Steps:**
1. User logs into the application.
2. User navigates to the calendar page.
**Expected Output:**
- The calendar displays all the user's classes.
**User Requirements Covered:** (15)
---
### Scenario 15: Teacher Adding Students to a Course
**Objective:** Ensure the teacher can add students to a course using different methods.
**Steps:**
1. Teacher logs into the application.
2. Teacher navigates to the course page.
3. Teacher clicks on "Add Students."
4. Teacher adds students using their unique email address, multiple email addresses, or a file.
5. Teacher submits the form to add students.
**Expected Output:**
- The students are added to the course and displayed on the course page.
**User Requirements Covered:** (16)- File:
RQ1-few-shot-cot-generatescenarios-gpt-4o-2024-05-13-2024-07-24-17-10-59-.txt
### Scenario 1: Viewing Enrolled Courses
**Objective:** Ensure all users can see the courses they are enrolled in.
**Steps:**
1. User logs into the application.
2. User navigates to the dashboard.
3. System displays a list of courses the user is enrolled in.
**Expected Output:**
- The dashboard shows all the courses the user is enrolled in.
---
### Scenario 2: Accessing Courses and Viewing Classes
**Objective:** Ensure all users can access any of the courses and see the classes ordered by date.
**Steps:**
1. User logs into the application.
2. User navigates to the dashboard.
3. User clicks on a course.
4. System displays the course details and lists the classes ordered by date.
**Expected Output:**
- The course details page shows all the classes ordered by date.
---
### Scenario 3: Teacher Creating a Course
**Objective:** Ensure the teacher can create courses with a title and an optional image.
**Steps:**
1. Teacher logs into the application.
2. Teacher navigates to the course creation page.
3. Teacher enters a title for the course.
4. Teacher optionally uploads an image.
5. Teacher clicks the "Create Course" button.
6. System saves the course and displays it in the teacher's dashboard.
**Expected Output:**
- The new course appears in the teacher's dashboard with the provided title and image.
---
### Scenario 4: Teacher Creating a Class within a Course
**Objective:** Ensure the teacher can create a new class within a course with all required attributes.
**Steps:**
1. Teacher logs into the application.
2. Teacher navigates to the course details page.
3. Teacher clicks on "Create Class."
4. Teacher fills in the class title, description, date and time, invited students, related files, and enables the forum
if desired.
5. Teacher clicks the "Create Class" button.
6. System saves the class and displays it in the course details page.
**Expected Output:**
- The new class appears in the course details page with all provided attributes.
---
### Scenario 5: Student Interacting with Courses on Dashboard
**Objective:** Ensure students can interact with courses on their dashboard.
**Steps:**
1. Student logs into the application.
2. Student navigates to the dashboard.
3. Student clicks on a course.
4. System displays the course details.
5. Student adds a comment to the forum if enabled.
6. Student downloads attached files if available.
**Expected Output:**
- The student can see course details, add comments to the forum, and download files.
---
### Scenario 6: Teacher Conducting Classes
**Objective:** Ensure the teacher can conduct classes with all specified functionalities.
**Steps:**
1. Teacher logs into the application.
2. Teacher navigates to the course details page.
3. Teacher clicks on a class to start it.
4. Teacher starts the class.
5. Teacher shares/blocks audio and webcam as needed.
6. Teacher views class information (title, duration, attendees, intervention times).
7. Teacher communicates via chat.
8. Teacher passes and revokes intervention turns.
9. Teacher ends the class.
**Expected Output:**
- The teacher can conduct the class with all functionalities working as expected.
---
### Scenario 7: Student Attending Classes
**Objective:** Ensure students can attend classes with all specified functionalities.
**Steps:**
1. Student logs into the application.
2. Student navigates to the course details page.
3. Student clicks on a class to join it.
4. Student enters the classroom when the teacher has started it.
5. Student receives the audio and video feed of the teacher.
6. Student mutes/unmutes the audio and video feed of the teacher.
7. Student views class information (title, duration, attendees).
8. Student communicates via chat.
9. Student requests and cancels intervention turns.
10. Student shares audio and webcam if intervention turn is granted.
**Expected Output:**
- The student can attend the class with all functionalities working as expected.
---
### Scenario 8: User Registration with CAPTCHA
**Objective:** Ensure users can register using their email and pass a CAPTCHA.
**Steps:**
1. User navigates to the registration page.
2. User enters their email, username, and password.
3. User completes the CAPTCHA.
4. User clicks the "Register" button.
5. System verifies the CAPTCHA and registers the user.
**Expected Output:**
- The user is registered successfully after passing the CAPTCHA.
---
### Scenario 9: User Login
**Objective:** Ensure users can log in to the application.
**Steps:**
1. User navigates to the login page.
2. User enters their email and password.
3. User clicks the "Login" button.
4. System verifies the credentials and logs the user in.
**Expected Output:**
- The user is logged in successfully and redirected to the dashboard.
---
### Scenario 10: Teacher Editing Course Attributes
**Objective:** Ensure the teacher can edit the attributes of a course at any time.
**Steps:**
1. Teacher logs into the application.
2. Teacher navigates to the course details page.
3. Teacher clicks on "Edit Course."
4. Teacher modifies the course attributes (title, description, image).
5. Teacher clicks the "Save" button.
6. System updates the course attributes.
**Expected Output:**
- The course attributes are updated and displayed correctly.
---
### Scenario 11: Teacher Editing Class Attributes
**Objective:** Ensure the teacher can edit the attributes of a class at any time.
**Steps:**
1. Teacher logs into the application.
2. Teacher navigates to the course details page.
3. Teacher clicks on a class to edit it.
4. Teacher modifies the class attributes (title, description, date and time, invited students, related files, forum
status).
5. Teacher clicks the "Save" button.
6. System updates the class attributes.
**Expected Output:**
- The class attributes are updated and displayed correctly.
---
### Scenario 12: User Modifying Profile
**Objective:** Ensure users can modify their profiles.
**Steps:**
1. User logs into the application.
2. User navigates to the profile settings page.
3. User modifies their username, email, password, and profile image.
4. User clicks the "Save" button.
5. System updates the profile information.
**Expected Output:**
- The profile information is updated and displayed correctly.
---
### Scenario 13: Teacher Adding Course Description
**Objective:** Ensure the teacher can add a description to the courses.
**Steps:**
1. Teacher logs into the application.
2. Teacher navigates to the course details page.
3. Teacher clicks on "Edit Course."
4. Teacher adds a description with text, images, or links.
5. Teacher clicks the "Save" button.
6. System updates the course description.
**Expected Output:**
- The course description is updated and displayed correctly.
---
### Scenario 14: User Registration with CAPTCHA (Duplicate Scenario)
**Objective:** Ensure all users are required to pass a CAPTCHA during registration.
**Steps:**
1. User navigates to the registration page.
2. User enters their email, username, and password.
3. User completes the CAPTCHA.
4. User clicks the "Register" button.
5. System verifies the CAPTCHA and registers the user.
**Expected Output:**
- The user is registered successfully after passing the CAPTCHA.
*Note: This scenario is a duplicate of Scenario 8.*
---
### Scenario 15: Viewing Calendar with Classes
**Objective:** Ensure all users have access to a calendar displaying all their classes.
**Steps:**
1. User logs into the application.
2. User navigates to the calendar page.
3. System displays a calendar with all the user's classes.
**Expected Output:**
- The calendar shows all the classes the user is enrolled in.
---
### Scenario 16: Teacher Adding Students to a Course
**Objective:** Ensure the teacher can add students to a course in different ways.
**Steps:**
1. Teacher logs into the application.
2. Teacher navigates to the course details page.
3. Teacher clicks on "Add Students."
4. Teacher adds students using their unique email address, multiple email addresses, or a file (txt, excel, Word, PDF).
5. Teacher clicks the "Add" button.
6. System adds the students to the course.
**Expected Output:**
- The students are added to the course and displayed in the course details page.