Category ID
Category Name
Test Case
Description
1
Dashboard Login
1.1
Dashboard Login
2.1
Overview Tab
3.1
3.2
Insert Tasks
View Tasks
3.3
Sort Tasks Alphabetically
3.4
Sort Tasks Numerically
3.5
Filter Tasks
3.6
Update Tasks
3.7
Delete Tasks
3.8
Update Database
4.1
Select Message Recipients
4.2
Enter and Submit Message
Content
5.1
Activity Tab
6.1
View Files
6.2
Sort Files
2
Dashboard Tabs
Objective
Verify login of authorized
users
Verify functions of Overview
Tab
Verify creation of Tasks
Verify display of Tasks
Verify correct alphabetic
sorting of Tasks in Task
display table
Verify correct numeric
sorting of Tasks in Task
display table
Verify ability to filter display
of Tasks in Task display table
Verify ability of Instructors
to edit existing Tasks
Verify ability of Instructors
to delete Tasks
Verify that Dashboard
integrates with back-end
database and actually
changes underlying data
Verify that Instructors and
TAs may select multiple
message recipients
Verify that Instructors and
TAs may compose and send
messages
Verify that the Activity Tab
displays the correct data
Verify that Instructors and
TAs may view existing Team
Site files
Verify that files may be
sorted by file name
3
Team Sites
6.3
Filter Files
7.1
Present Course Selector
7.2
Present List of Teams
7.3
Present List of Students
7.4
Present All Files Regarding
Tasks
7.5
Grade and Feedback
Management
8.1
Admin Tab: Courses
8.2
Admin Tab: Teams
9.1
Student Tasks: Display
9.2
Student Tasks: Submit
9.3
Student Tasks:
Create/Assign
9.4
Student Tasks: Delete
9.5
Student Tasks: Edit
Verify ability to filter display
of files in the Files display
table
Verify that Grades Tab
allows Instructors and TAs
to select from the correct
Courses
Verify that Grades Tab
allows Instructors and TAs
to select from the correct
Teams
Verify that Grades Tab
allows Instructors and TAs
to select from the correct
Students
Verify that Grades Tab
makes available for grading
the correct files
Verify that Grades Tab
allows Instructors and TAs
to grade deliverables and
record feedback
Verify ability of Admin Tab
to create and edit Courses
Verify ability of Admin Tab
to create and edit Teams
Verify that Tasks Script
accurately displays tasks
Verify the Students may
submit local files for Tasks
Verify that Students may
create and assign nongraded Tasks
Verify that Students may
delete non-graded Tasks
Verify that Students may
edit non-graded Tasks
4
TPOT Database
10.1
Grade Task Filter
10.2
Grade Privacy
10.3
Empty Grades
10.4
Correct Grades Display
10.5
Grader Identity
10.6
Grade Date
11.1
Student Messages
12.1
Database Login
12.2
Course Table
12.3
Task Table
12.4
Submission Slot Table
12.5
User Table
Verify that the Grades Script
displays grades for only
graded Tasks
Verify that a Student's may
only view their own grades
Verify that a Student is
notified when no grades are
available
Verify that completed tasks
which have not been graded
are properly displayed
Verify that the email
address of the grader of
Tasks and Courses is
properly displayed
Verify that the date a grade
was issued is properly
displayed
Verify that Students may
send messages to any
number of their teammates
or Instructors
Verify that the TPOT
database may accessed
both locally and remotely
Verify the existence and
correctness of the Course
table
Verify the existence and
correctness of the Task
table
Verify the existence and
correctness of the
Submission Slot table
Verify the existence and
correctness of the User
table
12.6
Instructor Table
12.7
TA Table
12.8
Master Administrator Table
12.9
Team Table
12.10
Actions of Tasks Table
12.11
Assignment of Tasks Table
12.12
Task Grades Table
12.13
Team Creation Table
12.14
Course Creation Table
12.15
Course Grades Table
12.16
Team Membership Table
12.17
Course Enrollment Table
12.18
Course Membership Table
Verify the existence and
correctness of the Instructor
table
Verify the existence and
correctness of the TA table
Verify the existence and
correctness of the Master
Administrator table
Verify the existence and
correctness of the Team
table
Verify the existence and
correctness of the Actions
on Tasks table
Verify the existence and
correctness of the
Assignment of Tasks table
Verify the existence and
correctness of the Task
Grades table
Verify the existence and
correctness of the Team
Creation table
Verify the existence and
correctness of the Course
Creation table
Verify the existence and
correctness of the Course
Grades table
Verify the existence and
correctness of the Team
Membership table
Verify the existence and
correctness of the Course
Enrollment table
Verify the existence and
correctness of the Course
5
Membership table
Verify the existence and
correctness of the Task
Submission table
12.19
Task Submission Table
12.20
Visits Table
Verify the existence and
correctness of the Visits
table
12.21
Future Task Team Test Data
Verify that a set of data with
tasks due in the future
exists for demo purposes
Past Task Team Test Data
Verify that a set of data with
tasks already due exists for
demo purposes
Test Harness Data
12.22
Test Category:
Integration
Description: Verify the ability to login to the TPOT Dashboard with only
Google-authorized Instructor and TA accounts
Test Case: 1.1
Case Name: Dashboard
Login
Requirements Fulfilled:
3.1.1.1.1 – 3.1.1.1.5
Purpose: To verify that only Instructor and TA accounts which are
authorized by Google may proceed into the tabbed Dashboard area of the
TPOT site. To also verify that authorized users are directed to the correct
page.
Version: 1.0
Written By: Aaron
Walden
Setup Conditions:
 Obtain the requirements document
 Obtain the email address and password of an Instructor or TA Google account
 Obtain the email address and password of a non-Instructor and non-TA Google account
 Open a web browser
Test Case Activity
Pass/Fail
Comments
Expected Result
1
Navigate to
http://411tpot.cs.odu.edu:8080/
TPOT Google login page appears.
2
Click Login with Google. Enter
the credentials of a nonInstructor, non-TA account.
Google verifies user but user is
redirected back to the TPOT Google
login page.
3
Click Login with Google. Enter
the credentials of an Instructor or
TA account.
Google verifies user and user is
redirected to the TPOT tabs home.
4
Visually verify that the user has
been directed to the TPOT tabs
home, Overview tab, and that the
user's Google account username
appears in the top right corner of
the page.
Overview tab is selected and the
user's Google email address appears
in the top right corner of the TPOT
tabs home.
Test Category:
Integration
Description: Verify that the Overview Tab displays the correct data
Test Case: 2.1
Case Name: Overview Tab
Requirements Fulfilled:
3.1.1.2.5.1
Purpose: To verify that Overview Tab displays the correct data regarding
recent Team Site activity.
Version: 1.0
Written By: Aaron
Walden
Setup Conditions:
 Obtain the requirements document
 Test Case 1.1 verified
 Obtain an Instructor/TA Google account which presides over at least one Team
 Obtain the URL of that Team's Google Site
 Open a web browser to http://411tpot.cs.odu.edu:8080/
 Log in to the TPOT Dashboard with an Instructor/TA Google account
Test Case Activity
1
2
3
4
Visually verify that the tables
presented on the Overview Tab
display recent site activity, Task
completion progress, and Tasks
in need of grading.
Navigate to the URL of the team
site overseen by the Instructor or
TA account used to log in.
Navigate to the recent activity
page of the site. Visually verify
that the data there matches the
data presented in the Overview
Tab recent activity table.
Navigate to the Tasks section of
the Team Site. Visually verify
that the Task data matches that
found in the Overview Tab Task
completion status table and the
Tasks in need of grading table.
Pass/Fail
Comments
Expected Result
The desired tables appear.
Team Site is accessed.
Data matches exactly.
Data matches exactly.
Test Category: Unit
Description: User Interface
Test Case: 3.1
Case Name: Insert Tasks
Version: 1
Written By: Josh Ward
Requirements
Purpose: To ensure instructors may insert new tasks and teacher's
Fulfilled: 3.1.1.2.7.1
assistants may not insert new tasks.
Setup Conditions:
 User has logged in to TPOT.
 User has navigated to Tasks tab.
Test Case Activity
1 Teacher's assistant navigates
to New Task tab.
2 Teacher's assistant accepts
error message pop up.
3 Instructor navigates to New
Task tab.
4 Instructor enters name,
description, course, assignee,
date due, and gradable status
in New Task panel and selects
Post New Task.
5 Instructor accepts
acknowledgement pop up.
Pass/Fail Comments
Expected Result
Teacher's assistant receives error
message pop up.
Error message pop up is cleared.
Instructor receives New Task panel.
Task is inserted into database, fields are
cleared and instructor receives
acknowledgement pop up.
Acknowledgement pop up is cleared.
Test Category: Unit
Description: User Interface
Test Case: 3.2
Case Name: View Tasks
Version: 1
Written By: Josh Ward
Requirements
Purpose: To ensure instructors and teacher's assistants may view existing
Fulfilled: 3.1.1.2.7.2
tasks.
Setup Conditions:
 User has logged in to TPOT.
 User has navigated to Tasks tab.
Test Case Activity
1 User navigates to View / Edit
Task tab.
Pass/Fail Comments
Expected Result
User receives View / Edit Task panel,
populated with all tasks in TPOT
database, composed of name,
description, course, assignee, date
assigned, date due, number of
submission slots, and gradable status
attributes. Attributes are formatted in
accordance with the requirements
document.
Test Category: Unit
Description: User Interface
Test Case: 3.3
Case Name: Sort Tasks
Version: 1
Written By: Josh Ward
Alphabetically
Purpose: To ensure instructors and teacher's assistants may sort existing
tasks alphabetically.
Requirements
Fulfilled: 3.1.1.2.7.2,
3.1.1.2.7.3
Setup Conditions:
 User has logged in to TPOT.
 User has navigated to Tasks tab.
 User has navigated to View / Edit Task tab.
Test Case Activity
1 User selects name attribute in
table header.
2 User selects description
attribute in table header.
3 User selects course attribute in
table header.
4 User selects assignee attribute
in table header.
5 User selects gradable status
attribute in table header.
Pass/Fail Comments
Expected Result
Table is sorted alphabetically by name.
Table is sorted alphabetically by
description.
Table is sorted alphabetically by course.
Table is sorted alphabetically by
assignee.
Table is sorted alphabetically by
gradable status.
Test Category: Unit
Description: User Interface
Test Case: 3.4
Case Name: Sort Tasks
Version: 1
Written By: Josh Ward
Numerically
Purpose: To ensure instructors and teacher's assistants may sort existing
tasks numerically.
Requirements
Fulfilled: 3.1.1.2.7.2,
3.1.1.2.7.4
Setup Conditions:
 User has logged in to TPOT.
 User has navigated to Tasks tab.
 User has navigated to View / Edit Task tab.
Test Case Activity
1 User selects date assigned
attribute in table header.
2 User selects date due attribute
in table header.
3 User selects number of
submission slots attribute in
table header.
4 User selects gradable status
attribute in table header.
Pass/Fail Comments
Expected Result
Table is sorted numerically by date
assigned.
Table is sorted numerically by date due.
Table is sorted numerically by number
of submission slots.
Table is sorted numerically by gradable
status.
Test Category: Unit
Description: User Interface
Test Case: 3.5
Case Name: Filter Tasks
Version: 1
Written By: Josh Ward
Requirements
Purpose: To ensure instructors and teacher's assistants may filter
Fulfilled: 3.1.1.2.7.2,
existing tasks.
3.1.1.2.7.5
Setup Conditions:
 User has logged in to TPOT.
 User has navigated to Tasks tab.
 User has navigated to View / Edit Task tab.
Test Case Activity
1
2
3
4
5
6
7
8
9
10
11
12
13
14
User selects a name from
selector in table header.
User selects all names from
selector in table header.
User selects a description
from selector in table header.
User selects all descriptions
from selector in table header.
User selects a course from
selector in table header.
User selects all courses from
selector in table header.
User selects an assignee from
selector in table header.
User selects all assignees
from selector in table header.
User selects a date assigned
from selector in table header.
User selects all dates assigned
from selector in table header.
User selects a date due from
selector in table header.
User selects all dates due
from selector in table header.
User selects a number of
submission slots from selector
in table header.
User selects all numbers of
submission slots from selector
in table header.
Pass/Fail
Comments
Expected Result
All tasks not matching selection are
removed from table.
All tasks not matching selection are
restored to table.
All tasks not matching selection are
removed from table.
All tasks not matching selection are
restored to table.
All tasks not matching selection are
removed from table.
All tasks not matching selection are
restored to table.
All tasks not matching selection are
removed from table.
All tasks not matching selection are
restored to table.
All tasks not matching selection are
removed from table.
All tasks not matching selection are
restored to table.
All tasks not matching selection are
removed from table.
All tasks not matching selection are
restored to table.
All tasks not matching selection are
removed from table.
All tasks not matching selection are
restored to table.
15 User selects a gradable status
from selector in table header.
16 User selects all gradable
statuses from selector in table
header.
All tasks not matching selection are
removed from table.
All tasks not matching selection are
restored to table.
Test Category: Unit
Description: User Interface
Test Case: 3.6
Case Name: Update Tasks
Version: 1
Written By: Josh Ward
Requirements
Purpose: To ensure instructors may update existing tasks and teacher's
Fulfilled: 3.1.1.2.7.2,
assistants may not update existing tasks.
3.1.1.2.7.6, 3.1.1.2.7.8
Setup Conditions:
 User has logged in to TPOT.
 User has navigated to Tasks tab.
 User has navigated to View / Edit Task tab.
Test Case Activity
1
2
3
4
5
6
7
Teacher's assistant selects
Update Task.
Teacher's assistant accepts
error message pop up.
Instructor selects Update
Task.
Instructor selects task to
update.
Instructor selects Cancel
Update.
Instructor accepts
acknowledgement pop up.
Instructor edits name field and
selects Accept Update.
8
Instructor accepts
acknowledgement pop up.
9 Instructor edits description
field and selects Accept
Update.
10 Instructor accepts
acknowledgement pop up.
11 Instructor edits assignee field
and selects Accept Update.
12 Instructor accepts
acknowledgement pop up.
13 Instructor edits date due field
and selects Accept Update.
Pass/Fail Comments
Expected Result
Teacher's assistant receives error
message pop up.
Error message pop up is cleared.
Instructor is prompted for task to
update.
Selected task fields in table become
editable.
Task is updated in database, fields
become uneditable, and instructor
receives acknowledgement pop up.
Acknowledgement pop up is cleared.
Task is updated in database, fields
become uneditable, and instructor
receives acknowledgement pop up.
Acknowledgement pop up is cleared.
Task is updated in database, fields
become uneditable, and instructor
receives acknowledgement pop up.
Acknowledgement pop up is cleared.
Task is updated in database, fields
become uneditable, and instructor
receives acknowledgement pop up.
Acknowledgement pop up is cleared.
Task is updated in database, fields
become uneditable, and instructor
receives acknowledgement pop up.
14 Instructor accepts
acknowledgement pop up.
15 Instructor edits number of
submission slots field and
selects Accept Update.
16 Instructor accepts
acknowledgement pop up.
Acknowledgement pop up is cleared.
Task is updated in database, fields
become uneditable, and instructor
receives acknowledgement pop up.
Acknowledgement pop up is cleared.
Test Category: Unit
Description: User Interface
Test Case: 3.7
Case Name: Delete Tasks
Version: 1
Written By: Josh Ward
Requirements
Purpose: To ensure instructors may delete existing tasks and teacher's
Fulfilled: 3.1.1.2.7.2, assistants may not delete existing tasks.
3.1.1.2.7.7
Setup Conditions:
 User has logged in to TPOT.
 User has navigated to Tasks tab.
 User has navigated to View / Edit Task tab.
Test Case Activity
Pass/Fail Comments
Expected Result
1 Teacher's assistant selects
Delete Task.
2 Teacher's assistant accepts
error message pop up.
3 Instructor selects Delete Task.
Teacher's assistant receives error
message pop up.
Error message pop up is cleared.
4 Instructor selects task to
delete.
5 Instructor selects Cancel
Delete.
6 Instructor selects Accept
Delete.
Instructor receives verification pop up.
Instructor is prompted for task to delete.
Verification pop up is cleared.
Task is deleted from database,
verification pop up is cleared, and
instructor receives acknowledgement
pop up.
Test Category: Unit
Description: User Interface
Test Case: 3.8
Case Name: Update
Version: 1
Written By: Josh Ward
Database
Purpose: To ensure instructors may update existing tasks and teacher's
assistants may not update existing tasks.
Requirements
Fulfilled: 3.1.1.2.7.2,
3.1.1.2.7.6, 3.1.1.2.7.8
Setup Conditions:
 User has logged in to TPOT.
 User has navigated to Tasks tab.
 User has navigated to View / Edit Task tab.
Test Case Activity
1
2
3
4
5
6
7
Teacher's assistant selects
Update Task.
Teacher's assistant accepts
error message pop up.
Instructor selects Update
Task.
Instructor selects task to
update.
Instructor selects Cancel
Update.
Instructor accepts
acknowledgement pop up.
Instructor edits name field and
selects Accept Update.
8
Instructor accepts
acknowledgement pop up.
9 Instructor edits description
field and selects Accept
Update.
10 Instructor accepts
acknowledgement pop up.
11 Instructor edits assignee field
and selects Accept Update.
12 Instructor accepts
acknowledgement pop up.
13 Instructor edits date due field
and selects Accept Update.
Pass/Fail Comments
Expected Result
Teacher's assistant receives error
message pop up.
Error message pop up is cleared.
Instructor is prompted for task to
update.
Selected task fields in table become
editable.
Task is updated in database, fields
become uneditable, and instructor
receives acknowledgement pop up.
Acknowledgement pop up is cleared.
Task is updated in database, fields
become uneditable, and instructor
receives acknowledgement pop up.
Acknowledgement pop up is cleared.
Task is updated in database, fields
become uneditable, and instructor
receives acknowledgement pop up.
Acknowledgement pop up is cleared.
Task is updated in database, fields
become uneditable, and instructor
receives acknowledgement pop up.
Acknowledgement pop up is cleared.
Task is updated in database, fields
become uneditable, and instructor
receives acknowledgement pop up.
14 Instructor accepts
acknowledgement pop up.
15 Instructor edits number of
submission slots field and
selects Accept Update.
16 Instructor accepts
acknowledgement pop up.
Acknowledgement pop up is cleared.
Task is updated in database, fields
become uneditable, and instructor
receives acknowledgement pop up.
Acknowledgement pop up is cleared.
Test Category: Unit
Description: User Interface
Test Case: 4.1
Case Name: Select
Version: 1
Written By: Joe Elder
Message Recipients
Purpose: To ensure instructors and Teacher’s Assistants can select the
correct subset of message recipients.
Requirements
Fulfilled: 3.1.1.2.3.1
Setup Conditions:
 User has logged in to TPOT.
 User has navigated to Messages tab.
Test Case Activity
1 Instructor selects desired
Course from drop down
selector
2 Instructor selects desired
Team from drop down selector
3 Instructor selects desired UserType from drop down selector
4 Instructor clicks submit and
proceeds
Pass/Fail Comments
Expected Result
The table which shows users will be
populated only with users associated
with the selected course.
The table which shows users will be
populated only with users associated
with the selected team.
The table which shows users will be
populated only with users of the selected
type.
The instructor will be taken to another
page which contains a form to enter
messages.
Test Category: Unit
Description: User Interface
Test Case: 4.2
Case Name: Enter and
Version: 1
Written By: Joe Elder
Submit Message Content
Purpose: To ensure instructors and teacher's assistants may add message
content and send messages
Requirements
Fulfilled: 3.1.1.2.3.2,
3.1.1.2.3.3
Setup Conditions:
 User has logged in to TPOT.
 User has navigated to Messages tab.
 User has completed unit test 4.1
Test Case Activity
1 User clicks inside the subject
text box and enters content.
2 User clicks inside the message
text box and enters content.
3 User clicks send button
sending the message to the
desired subset of users.
4 Message Recipients check
emails
Pass/Fail Comments
Expected Result
Textbox functions correctly displaying
the letters typed.
Textbox functions correctly displaying
the letters typed.
The messages are sent to the selected
subset of users successfully
Messages containing the correct content
for Subject and Message content exist
and are correct
Test Category:
Integration
Description: Verify that the Activity Tab displays the correct sortable and
filterable data
Test Case: 5.1
Case Name: Activity Tab
Requirements Fulfilled:
3.1.1.2.1.1 – 3.1.1.2.1.3
Purpose: To verify that Activity Tab displays the correct data regarding
recent Team Site activity and that the data is sortable and filterable.
Version: 1.0
Written By: Aaron
Walden
Setup Conditions:
 Obtain the requirements document
 Test Case 1.1 verified
 Obtain an Instructor/TA Google account which presides over at least one Team
 Obtain the URL of that Team's Google Site
 Open a web browser to http://411tpot.cs.odu.edu:8080/
 Log in to the TPOT Dashboard with an Instructor/TA Google account
 Click the Activity Tab
Test Case Activity
1
2
3
4
5
6
Visually verify that the table on
the Activity Tab displays
activities with the attributes listed
in requirement 3.1.1.2.1.1.
For each attribute listed in
3.1.1.2.1.1, click its heading in
the Activity table to sort by
attribute. Visually verify that
sorting is correct.
Click each attribute again.
Visually verify that sorting
reverses and is correct.
For each attribute listed in
3.1.1.2.1.1, begin typing in the
filter box. Visually verify the
rows which remain contain the
text entered in the target attribute.
Navigate to the URL of the team
site overseen by the Instructor or
TA account used to log in.
Navigate to the recent activity
page of the site. Verify that the
data there matches the data
presented in the Activity Tab.
Pass/Fail
Comments
Expected Result
The desired attributes are present.
Proper sorting occurs.
Proper sorting occurs.
Proper filtering occurs.
Team Site is accessed.
Data matches exactly.
Test Category: Unit
Description: User Interface
Test Case: 6.1
Case Name: View Files
Version: 1
Written By: Josh Ward
Requirements
Purpose: To ensure instructors and teacher's assistants may view existing
Fulfilled: 3.1.1.2.2.1
files.
Setup Conditions:
 User has logged in to TPOT.
Test Case Activity
1 User navigates to Files tab.
Pass/Fail Comments
Expected Result
User receives View Files panel,
populated with all files in TPOT
database, composed of course, team,
user email address, filename, file path,
action performed, and date
accomplished attributes. Attributes are
formatted in accordance with the
requirements document.
Test Category: Unit
Description: User Interface
Test Case: 6.2
Case Name: Sort Files
Version: 1
Written By: Josh Ward
Requirements
Purpose: To ensure instructors and teacher's assistants may sort existing
Fulfilled: 3.1.1.2.2.1, files.
3.1.1.2.2.2
Setup Conditions:
 User has logged in to TPOT.
 User has navigated to Files tab.
Test Case Activity
1 User selects course attribute in
table header.
2 User selects team attribute in
table header.
3 User selects user email address
attribute in table header.
4 User selects activity type
attribute in table header.
5 User selects filename attribute
in table header.
6 User selects date
accomplished attribute in table
header.
Pass/Fail Comments
Expected Result
Table is sorted by course.
Table is sorted by team.
Table is sorted by user email address.
Table is sorted by activity type.
Table is sorted by filename.
Table is sorted by date accomplished.
Test Category: Unit
Description: User Interface
Test Case: 6.3
Case Name: Filter Files
Version: 1
Written By: Josh Ward
Requirements
Purpose: To ensure instructors and teacher's assistants may filter
Fulfilled: 3.1.1.2.2.1,
existing files.
3.1.1.2.2.3
Setup Conditions:
 User has logged in to TPOT.
 User has navigated to Files tab.
Test Case Activity
1
User selects a course from
selector in table header.
2 User selects all courses from
selector in table header.
3 User selects a team from
selector in table header.
4 User selects all teams from
selector in table header.
5 User selects a user email
address from selector in table
header.
6 User selects all user email
addresses from selector in
table header.
7 User selects an activity type
from selector in table header.
8 User selects all activity types
from selector in table header.
9 User selects a filename from
selector in table header.
10 User selects all filenames
assigned from selector in table
header.
11 User selects a date
accomplished from selector in
table header.
12 User selects all dates
accomplished from selector in
table header.
Pass/Fail Comments
Expected Result
All tasks not matching selection are
removed from table.
All tasks not matching selection are
restored to table.
All tasks not matching selection are
removed from table.
All tasks not matching selection are
restored to table.
All tasks not matching selection are
removed from table.
All tasks not matching selection are
restored to table.
All tasks not matching selection are
removed from table.
All tasks not matching selection are
restored to table.
All tasks not matching selection are
removed from table.
All tasks not matching selection are
restored to table.
All tasks not matching selection are
removed from table.
All tasks not matching selection are
restored to table.
Test Category: Unit
Description: User Interface
Test Case: 7.1
Case Name: Present
Version: 1
Written By: Joe Elder
Course Selector
Purpose: To present authorized users with a Course Drop down selector
and lists containing all graded tasks and course final grades
Requirements
Fulfilled: 3.1.1.2.4.1,
3.1.1.2.4.2
Setup Conditions:
 User has logged in to TPOT.
 User has navigated to Grades tab.
Test Case Activity
1 Authorized users click a
Course selector drop down
2 Authorized User selects a
menu item by clicking
Pass/Fail Comments
Expected Result
The drop down menu appears populated
with only the courses associated with
that authorized user.
The list of all graded Tasks in that
course and final grades will appear
Test Category: Unit
Description: User Interface
Test Case: 7.2
Case Name: Present list of Version: 1
Written By: Joe Elder
teams
Purpose: To present authorized users with a Course Drop down selector
and lists containing all graded tasks and course final grades
Requirements
Fulfilled: 3.1.1.2.4.3
Setup Conditions:
 User has completed unit test 7.1
Test Case Activity
1 Authorized users click a
Teams drop down selector
2 Authorized User selects a
menu item by clicking
Pass/Fail Comments
Expected Result
The drop down menu appears populated
with only the teams associated with that
authorized user and Course.
The list of all Teams enrolled in the
selected Course will appear
Test Category: Unit
Description: User Interface
Test Case: 7.3
Case Name: Present list of Version: 1
Written By: Joe Elder
Students
Purpose: To present authorized users with a Course Drop down selector
and lists containing all graded tasks and course final grades
Requirements
Fulfilled: 3.1.1.2.4.4
Setup Conditions:
 User has completed unit test 7.2
Test Case Activity
1 Authorized users click a
Student drop down selector
2 Authorized User selects a
menu item by clicking
Pass/Fail Comments
Expected Result
The drop down menu appears populated
with only the students associated with
that authorized user, Course, and Team.
The list of all Students enrolled in the
selected Course will appear
Test Category: Unit
Description: User Interface
Test Case: 7.4
Case Name: Present all
Version: 1
Written By: Joe Elder
files regarding Tasks
Purpose: To present authorized users with all Files submitted toward
completion of a graded Task
Requirements
Fulfilled: 3.1.1.2.4.5
Setup Conditions:
 User has completed unit test 7.3
Test Case Activity
1 Authorized user clicks view
files link
Pass/Fail Comments
Expected Result
The list of all Files submitted toward
completion of a graded Task appears
Test Category: Unit
Description: User Interface
Test Case: 7.5
Case Name: Grade and
Version: 1
Written By: Joe Elder
Feedback management
Purpose: To present authorized users with a form to submit feedback and
a grade for selected task or the final grade.
Requirements
Fulfilled: 3.1.1.2.4.6,
3.1.1.2.4.7
Setup Conditions:
 User has completed unit test 7.3
Test Case Activity
1 Authorized user clicks the edit
link next to the data they wish
to update
2 Authorized user enters desired
grade into Team grade text
box or individual grade text
boxes accordingly
3 Authorized user enters desired
feedback
4 Authorized user clicks submit
Pass/Fail Comments
Expected Result
Upon clicking the link users will be
presented with a form
Text boxes function correctly displaying
the typed content.
Text box functions correctly displaying
the typed content
The form is processed updating records
in the database. The user will be taken
back to the grades page where the
updated records will now be visible.
Test Category:
Integration
Description: Verify that Courses may be created, edited, and deleted
through the Admin Tab
Test Case: 8.1
Case Name: Admin Tab
Requirements Fulfilled:
3.1.1.2.7.1 – 3.1.1.2.7.3,
3.1.1.2.7.6
Purpose: To verify administration of an Instructor's own Courses is
possible through the Admin Tab's interface.
Version: 1.0
Written By: Aaron
Walden
Setup Conditions:
 Obtain the requirements document
 Test Case 1.1 verified
 Obtain an Instructor Google account
 Open a web browser to http://411tpot.cs.odu.edu:8080/
 Log in to the TPOT Dashboard with an Instructor/TA Google account
 Click the Admin Tab, then the Create Course section
Test Case Activity
Pass/Fail
Comments
Expected Result
1
Visually verify that the fields in
the Create Course section
correspond to the fields listed in
requirements section 3.1.1.2.7.1.
The correct fields are present.
2
Fill out the fields listed in
requirements section 3.1.1.2.7.1.
Press the 'Create' button.
Page reloads and a green success
message appears.
3
Click on the Edit Course section.
Visually verify that the fields in
the Edit Course section
correspond to the fields listed in
section 3.1.1.2.7.1.
The correct Edit Course fields
appear.
4
In the drop-down selector, locate
the Course just created. Select it.
Page reloads and the Edit Course
fields are populated the information
entered in Step 2.
Edit every attribute of the Course
detailed in section 3.1.1.2.7.1.
Press the 'Update' button.
Page reloads and a green success
message appears.
6
Repeat Steps 3 and 4.
Page reloads and the Edit Course
fields are populated the information
entered in Step 2.
7
Press the 'Delete Course' button.
Page reloads and a green success
message appears.
8
Click the Edit Course section.
Visually verify that the Course
created in Step 2 does not appear.
Course does not appear.
5
Test Category:
Integration
Description: Verify that Teams may be created, edited, and deleted
through the Admin Tab
Test Case: 8.2
Case Name: Admin Tab
Requirements Fulfilled:
3.1.1.2.7.4 – 3.1.1.2.7.6,
3.1.1.2.7.7
Purpose: To verify administration of an Instructor's own Teams is possible
through the Admin Tab's interface.
Version: 1.0
Written By: Aaron
Walden
Setup Conditions:
 Obtain the requirements document
 Test Case 1.1 verified
 Obtain an Instructor Google account
 Obtain the URL of any Google Site owned by the Google account
 Open a web browser to http://411tpot.cs.odu.edu:8080/
 Log in to the TPOT Dashboard with an Instructor/TA Google account
 Click the Admin Tab, then the Create Team section
Test Case Activity
Pass/Fail
Comments
Expected Result
1
Visually verify that the fields in
the Create Team section
correspond to the fields listed in
requirements section 3.1.1.2.7.4.
The correct fields are present.
2
Fill out the fields listed in
requirements section 3.1.1.2.7.4.
Press the 'Create' button.
Page reloads and a green success
message appears, including the URL
of the Team's new Team Site.
3
4
5
Click the URL of the new Team's
Team Site. Visually verify that
the site displays the correct
theme and was properly copied
from the site feed URL specified
in Step 2.
Click on the Edit Team section.
Visually verify that the fields in
the Edit Team section correspond
to the fields listed in section
3.1.1.2.7.4.
In the drop-down selector, locate
the Team just created. Select it.
The correct Team Site appears.
The correct Edit Team fields appear.
Page reloads and the Edit Team fields
are populated the information entered
in Step 2.
6
Edit every attribute of the Team
detailed in section 3.1.1.2.7.4.
Press the 'Update' button.
Page reloads and a green success
message appears, including the URL
of the Team's new Team Site.
7
Repeat Step 3.
Correct Team Site appears.
8
Repeat Steps 4 and 5.
Page reloads and the Edit Team fields
are populated the information entered
in Step 2.
8
Press the 'Delete Team' button.
Page reloads and a green success
message appears.
9
Click the Edit Team section.
Visually verify that the Team
created in Step 2 does not appear.
Team does not appear.
Test Category:
Integration
Description: This will test if the task script displays all the task for the
specific user
Test Case: 9.1
Case Name: Student Task
GUI
Requirements
Fulfilled: 3.1.1.2.1,
3.1.2.1.8
Purpose: Test if the script accurately displays tasks.
Version: 1.0
Written By: TJ Carson
Setup Conditions:



Load tasks into the database associated with the user that will be used to test the script
Login with the associated Google Account to the Team Site
Go to the task page on the team page
Test Case Activity
Pass/Fail
Comments
Expected Result
1 Table show display with tasks
associated with the user.
Graded task will display with a file
upload slot for as many slots that are
assigned for the task and ungraded task
will display for checkboxes
2 Click the "Due Date" column.
Column sorts tasks by Due Date in
descending order (newest first).
3 Click the "Due Date" column
again.
Column sorts tasks by Due Date in
ascending order (oldest first).
Test Category:
Integration
Description: This will test if the upload slots work
Test Case: 9.2
Case Name: Student Task
GUI
Requirements
Fulfilled: 3.1.2.1.2
Purpose: Test if files can be uploaded for graded tasks
Version: 1.0
Written By: TJ Carson
Setup Conditions:

Have a graded task put in the database for the testing user.
Test Case Activity
1 Click the upload button for
each of the submission slots
Pass/Fail
Comments
Expected Result
Filenames
must be
unique
Brings up a file window and allows the
user to select a file from their computer
2 Click the Submit button
The cell should then display the file
names that have been upload instead of
the upload button
3 Refresh the page
Page refreshes
4 Check bottom of the page for
files
Files that have been uploaded will be
displayed at the bottom of the page.
Test Category:
Integration
Description: This will test creating a task and test the checkbox
Test Case: 9.3
Case Name: Student Task
GUI
Requirements
Fulfilled: 3.1.2.1.3,
3.1.2.1.5, 3.1.2.1.7,
3.1.2.1.9
Purpose: Check if the user can create a task for their team, individual
team member, or themselves. Then check the checkbox for functionality
Version: 1.0
Written By: TJ Carson
Setup Conditions:

Test Case Activity
1 Click the Create tab on the
script
Pass/Fail
Comments
Expected Result
Takes the user to the create task menu
2 Enter information into the
correct fields and set the
assign tab to another user
3 Click the Submit Button
A confirmation message will appear
with the user the task has been assigned
to.
4 Have the user the task was
assigned to click the View task
tab on the script
Takes the user to the view Tasks screen
5 Look for the task that was just
created
The task will be at the bottom of the list
6 Click the Complete Checkbox
The box has will fill with a checkbox
7 Refresh the page
The box will stay checked
Test Category:
Integration
Description: Delete a task
Test Case: 9.4
Case Name: Student Task
GUI
Requirements
Fulfilled: 3.1.2.1.4,
3.1.2.1.9
Purpose: Test if a user can delete a created task
Version: 1.0
Written By: TJ Carson
Setup Conditions:

Create a task from the create task
Test Case Activity
Pass/Fail
Comments
Expected Result
1 Click the View Task Tab
Takes the user to the view task tab
2 Click the Delete Button on the
recently created tab
The task will be deleted from the
database and not show on the table
anymore
Test Category:
Integration
Description: Edit Task
Test Case: 9.5
Case Name: Student Task
GUI
Requirements
Fulfilled: 3.1.2.1.6
Purpose: To test the functionality of the edit task
Version: 1.0
Written By: TJ Carson
Setup Conditions:

Create a task from the create task
Test Case Activity
Pass/Fail
Comments
Expected Result
1 Click the View Task Tab
Takes the user to the view task tab
2 Click the Edit Task button on
the task that was just created
This will take you to the edit task menu
3 Change one or more fields of
the task
4 Click Submit
This will take the user back to the view
task tab with the new task in place
Test Category: Unit
Description: Filter of the gradable tasks
Test Case:
Case Name: Grade Task
filter
10.1
Requirements
Fulfilled: 3.1.2.2.13.1.2.2.3
Version: 1.0
Written By: Jose
Brandariz
Purpose: Determine that the tasks shown are the gradable tasks only.
Setup Conditions:


The user must have at least one grade in a task and a non-gradable task.
The user must be in a team.
Test Case Activity
Pass/Fail
Comments
Expected Result
1 Enter Team Site
Log in with an
appropriate user
and password to
a Team Site
2 Go to Grades page
Click on the
Grades Page on
your Team Site
3 Look into Tasks Grades
Check Visually
Tasks shown must be the gradable
tasks for that user only.
4 Look into Course Grades
Check Visually
Proper message is shown for the
course grade. Message of ¨No
available grade at this time¨ or the
proper grade for the course.
Test Category: Unit
Description: Test to determine the proper function of the grades script
Test Case:
Case Name: Grades privacy
Version: 1.0
10.2
Requirements
Fulfilled: 3.1.2.2.13.1.2.2.3
Written By: Jose
Brandariz
Purpose: Determine that the grades are only visible by the appropriate user.
Setup Conditions:



The user must have at least one grade in a task.
The user must have a grade in the course.
The user must be in a team.
Test Case Activity
Pass/Fail
Comments
Expected Result
1 Enter Team Site
Log in with an
appropriate user
and password to
a Team Site
2 Go to Grades page
Click on the
Grades Page on
your Team Site
3 Look into Tasks Grades
Check Visually
Grades shown must be the ones for
that user. No other user’s grades
shown. No other team grades for
the user are shown.
4 Look into Course Grades
Check Visually
Grade for the course shown must be
the one for that user. No other
user´s grades or other course grade
shown.
Test Category: Unit
Description: Test to determine the proper function of the grades script
Test Case:
Case Name: Grades Page
Empty.
10.3
Requirements
Fulfilled: 3.1.2.2.13.1.2.2.3
Version: 1.0
Written By: Jose
Brandariz
Purpose: Determine that the Grades Page displays the proper message to user
without tasks or course grade.
Setup Conditions:



The user does not have grades on course or tasks.
The user does not have any tasks pending.
The user must be in a team.
Test Case Activity
Pass/Fail
Comments
Expected Result
1 Enter Team Site
Log in with an
appropriate user
and password to
a Team Site
2 Go to Grades page
Click on the
Grades Page on
your Team Site
3 Look into Tasks Grades
Check Visually
¨No grades available at this time¨
must be shown on the page.
4 Look into Course Grades
Check Visually
¨No grade available at this time¨
must be shown on the page.
Test Category: Unit
Description: Test to determine the proper function of the grades script
Test Case:
Case Name: Grades Correct
Display
10.4
Requirements
Fulfilled: 3.1.2.2.13.1.2.2.3
Version: 1.0
Written By: Jose
Brandariz
Purpose: Determine that the task pending to be graded show the proper
message.
Setup Conditions:


The user does have tasks pending to be graded.
The user must be in a team.
Test Case Activity
Pass/Fail
Comments
Expected Result
1 Enter Team Site
Log in with an
appropriate user
and password to
a Team Site
2 Go to Grades page
Click on the
Grades Page on
your Team Site
3 Look into Tasks Grades
Check Visually
“Pending to be graded” must be
shown on task delivered but not yet
graded. Tasks already graded must
be shown.
4 Look into Course Grades
Check Visually
Proper message is shown for the
course grade. Message of ¨No
available grade at this time¨ or the
proper grade for the course.
Test Category: Unit
Description: Grader e-mail must be shown correctly
Test Case:
Case Name: Grader e-mail
Version: 1.0
10.5
Requirements
Fulfilled: 3.1.2.2.5
Written By: Jose
Brandariz
Purpose: Determine that the grader e-mail is shown for grades assigned.
Setup Conditions:


The user must have at least one grade in a task.
The user must be in a team.
Test Case Activity
Pass/Fail
Comments
Expected Result
1 Enter Team Site
Log in with an
appropriate user
and password to
a Team Site
2 Go to Grades page
Click on the
Grades Page on
your Team Site
3 Look into Tasks Grades
Check Visually
The grader e-mail must be the one
from the person that submitted the
grade.
4 Look into Course Grades
Check Visually
In case there is a grade, the grader
e-mail must be the one from the
person that submitted the grade.
Test Category: Unit
Description: Grade Date
Test Case:
Case Name: Grade Date
Version: 1.0
10.6
Requirements
Fulfilled: 3.1.2.2.4
Written By: Jose
Brandariz
Purpose: Determine that the date for the grade given to a task is in a correct
format.
Setup Conditions:


The user must have at least one grade in a task.
The user must be in a team.
Test Case Activity
Pass/Fail
Comments
Expected Result
1 Enter Team Site
Log in with an
appropriate user
and password to
a Team Site
2 Go to Grades page
Click on the
Grades Page on
your Team Site
3 Look into Tasks Grades
Check Visually
The date shown on the graded task
has the format (YYYY-MM-DD
HH:MM:SS).
4 Look into Course Grades
Check Visually
The date shown on the grade for the
course has the format described
above.
Test Category: Unit
Description: Verify that the Team Site's Messages Script allows Students to
send emails to any number of their teammates and instructors
Test Case: 11.1
Case Name: Messages
Script
Requirements
Fulfilled: 3.1.2.3.1 3.1.2.3.3
Purpose: To verify that the Team Site's Messages Script allows Students to
quickly communicate with their teammates and instructors
Version: 1.0
Written By: Aaron
Walden
Setup Conditions:





Obtain the requirements document
Obtain an email account with access to a Team Site
Obtain the email accounts of several students who have access to the same Team Site
Open a web browser
Navigate to the aforementioned Team Site
Test Case Activity
1
2
3
Navigate to the Messages
page.
Visually verify that the
following fields are present:
email subject, email body,
selector containing
aforementioned team
members, 'send' button.
Select all of the available team
members. Fill in the email
subject and body fields with
arbitrary text.
Pass/Fail
Comments
Expected Result
Messages interface loads.
Fields are present.
Fields accept selection and text entry.
4
Press send.
A message verifies that message
composed was sent to the selected
parties.
5
Open Gmail and log into the
accounts of the team members
the message was sent to in
step 4.
Sent message is found, from the original
email address, with the subject and body
entered in step 3.
Test Category: Unit
Description: Verify the ability to login to the TPOT database from local and
remote machines
Test Case: 12.1
Case Name: Local and
Remote Database Login
Requirements
Fulfilled: 3.1.3.1.1.1,
3.1.3.1.2.1
Purpose: To verify that the both the machine that hosts TPOT and other,
remote machines may log into the TPOT database and run queries.
Version: 1.0
Written By: Aaron
Walden
Setup Conditions:





Obtain the requirements document
Note the 'root' password for the TPOT database, defined here as ROOTPW
Note the 'remote' password for the TPOT database, defined here as REMOTEPW
Obtain an account username and password which has access to the TPOT virtual machine
Log into the ODU virtual machine which hosts the TPOT database
Test Case Activity
Pass/Fail
Comments
Expected Result
1
Open a command prompt
within the virtual machine's
remote desktop.
Command prompt window appears.
2
Run MySQL with the
command "mysql –uroot –
pROOTPW tpottest"
MySQL login message appears and user
is presented with a MySQL prompt:
"mysql>"
3
Execute the statement "show
grants for 'root'@'localhost';"
A message containing the words
"GRANT ALL PRIVILEGES ON *.*
TO 'root'@'localhost'" appears.
4
Execute the statement "show
grants for 'remote'@'%';"
A message containing the words
"GRANT ALL PRIVILEGES ON
`tpottest`.* TO 'remote'@'%'" appears.
5
Open a command prompt
outside of the virtual
machine's remote desktop.
Command prompt window appears.
6
Run MySQL with the
command "mysql –uremote –
pREMOTEPASS tpottest"
MySQL login message appears and user
is presented with a MySQL prompt:
"mysql>"
Test Category: Unit
Description: Test for the existence, correctness, and proper functioning of the
Course table
Test Case: 12.2
Case Name: Course Table
Requirements
Fulfilled: 3.1.3.2.1.1,
3.1.3.2.1.2,3.1.3.2.1.3
Purpose: To verify the existence, correctness, and ability to accept insertions
of the Course table such that it is ready to be used by the Dashboard and Team
Sites.
Version: 1.0
Written By: Aaron
Walden
Setup Conditions:




Obtain the requirements document
Open a command prompt
Test Case 12.1 verified
Run MySQL and connect with the command "mysql –h 411tpot.cs.odu.edu –uremote –
premotepass tpottest"
Test Case Activity
1
2
3
4
5
Execute the statement
"describe course;"
Visually verify that the
columns of the table
correspond to the
requirements document
section 3.1.3.2.1.2
Execute the statement "insert
into course (title, subject,
crsenum, begin, end) values
('Test Course', 'TEST', 101,
'2014-06-01', '2014-08-15');"
Execute the statement "select
* from course where
name='Test Course' order by
idnum asc;"
Visually verify that the values
inserted in Step 3 are present
in the last row returned.
Pass/Fail
Comments
Expected Result
The description of the course table is
printed to the console
A list of columns with data type
information is displayed, matching the
requirements document
Console prints "Query OK, 1 row
affected."
At least one row is displayed.
Contents of the last row are those
inserted in Step 3.
Test Category: Unit
Description: Test for the existence, correctness, and proper functioning of the
Task table
Test Case: 12.3
Case Name: Task Table
Requirements
Fulfilled: 3.1.3.2.2.1,
3.1.3.2.2.2,3.1.3.2.2.3
Purpose: To verify the existence, correctness, and ability to accept insertions
of the Task table such that it is ready to be used by the Dashboard and Team
Sites.
Version: 1.0
Written By: Aaron
Walden
Setup Conditions:





Obtain the requirements document
Open a command prompt
Test Cases 12.1, 12.2 verified
Obtain the IDNum of a Course in the Course table, defined here as CN
Run MySQL and connect with the command "mysql –h 411tpot.cs.odu.edu –uremote –
premotepass tpottest"
Test Case Activity
1
2
3
4
5
Execute the statement
"describe task;"
Visually verify that the
columns of the table
correspond to the
requirements document
section 3.1.3.2.2.2
Execute the statement "insert
into task (crsenum, name,
due_date, description) values
(CN, 'TestTask', '2014-06-06',
'Test desc');"
Execute the statement "select
* from task where
name='TestTask' order by
idnum asc;"
Visually verify that the values
inserted in Step 3 are present
in the last row returned.
Pass/Fail
Comments
Expected Result
The description of the course table is
printed to the console
A list of columns with data type
information is displayed, matching the
requirements document
Console prints "Query OK, 1 row
affected."
At least one row is displayed.
Contents of the last row are those
inserted in Step 3.
Test Category: Unit
Description: Test for the existence, correctness, and proper functioning of the
Submission Slot table
Test Case: 12.4
Case Name: Submission
Slot Table
Requirements
Fulfilled: 3.1.3.2.3.1,
3.1.3.2.3.2,3.1.3.2.3.3
Purpose: To verify the existence, correctness, and ability to accept insertions
of the Submission Slot table such that it is ready to be used by the Dashboard
and Team Sites.
Version: 1.0
Written By: Aaron
Walden
Setup Conditions:





Obtain the requirements document
Open a command prompt
Test Cases 12.1, 12.3 verified
Obtain the IDNum of a Task in the Task table, defined here as TN
Run MySQL and connect with the command "mysql –h 411tpot.cs.odu.edu –uremote –
premotepass tpottest"
Test Case Activity
1
2
3
4
5
Execute the statement
"describe sub_slot;"
Visually verify that the
columns of the table
correspond to the
requirements document
section 3.1.3.2.3.2
Execute the statement "insert
into sub_slot (tid, name,
slotnum) values (TN,
'testname', 1)
Execute the statement "select
* from sub_slot where tid=TN
and slotum=1;
Visually verify that the values
inserted in Step 3 are present
in the row returned.
Pass/Fail
Comments
Expected Result
The description of the course table is
printed to the console
A list of columns with data type
information is displayed, matching the
requirements document
Console prints "Query OK, 1 row
affected."
One row is displayed.
Contents of the row are those inserted in
Step 3.
Test Category: Unit
Description: Test for the existence, correctness, and proper functioning of the
User table
Test Case: 12.5
Case Name: User Table
Version: 1.0
Written By: Aaron
Walden
Purpose: To verify the existence, correctness, and ability to accept insertions
Requirements
Fulfilled: 3.1.3.2.4.1, of the User table such that it is ready to be used by the Dashboard and Team
3.1.3.2.4.2, 3.1.3.2.4.3 Sites.
Setup Conditions:




Obtain the requirements document
Open a command prompt
Test Case 12.1 verified
Run MySQL and connect with the command "mysql –h 411tpot.cs.odu.edu –uremote –
premotepass tpottest"
Test Case Activity
1
2
3
4
5
Execute the statement
"describe user;"
Visually verify that the
columns of the table
correspond to the
requirements document
section 3.1.3.2.4.2
Execute the statement "insert
into user (idnum, firstname,
middlename, lastname) values
('test@test.com', 't', 'e', 'st');"
Execute the statement "select
* from user where
idnum='test@test.com';
Visually verify that the values
inserted in Step 3 are present
in the row returned.
Pass/Fail
Comments
Expected Result
The description of the course table is
printed to the console
A list of columns with data type
information is displayed, matching the
requirements document
Console prints "Query OK, 1 row
affected."
One row is displayed.
Contents of the row are those inserted in
Step 3.
Test Category: Unit
Description: Test for the existence, correctness, and proper functioning of the
Instructor table
Test Case: 12.6
Case Name: Instructor
Table
Version: 1.0
Written By: Aaron
Walden
Purpose: To verify the existence, correctness, and ability to accept insertions
Requirements
Fulfilled: 3.1.3.2.4.4, of the Instructor table such that it is ready to be used by the Dashboard and
3.1.3.2.4.5, 3.1.3.2.4.6 Team Sites.
Setup Conditions:





Obtain the requirements document
Open a command prompt
Test Cases 12.1, 12.5 verified
Obtain the IDNum (email address) of some entry in the User table, defined here as UID
Run MySQL and connect with the command "mysql –h 411tpot.cs.odu.edu –uremote –
premotepass tpottest"
Test Case Activity
Pass/Fail
Comments
Expected Result
1
Execute the statement
"describe instructor;"
The description of the course table is
printed to the console
2
Visually verify that the
columns of the table
correspond to the
requirements document
section 3.1.3.2.4.5
A list of columns with data type
information is displayed, matching the
requirements document
3
Execute the statement "insert
into instructor (uid) values
(UID);
Console prints "Query OK, 1 row
affected."
4
Execute the statement "select
* from instructor where
uid=UID;
One row is displayed.
5
Visually verify that the values
inserted in Step 3 are present
in the row returned.
Contents of the row are those inserted in
Step 3.
Test Category: Unit
Description: Test for the existence, correctness, and proper functioning of the
TA table
Test Case: 12.7
Case Name: TA Table
Version: 1.0
Written By: Aaron
Walden
Purpose: To verify the existence, correctness, and ability to accept insertions
Requirements
Fulfilled: 3.1.3.2.4.7, of the TA table such that it is ready to be used by the Dashboard and Team
3.1.3.2.4.8, 3.1.3.2.4.9 Sites.
Setup Conditions:





Obtain the requirements document
Open a command prompt
Test Cases 12.1, 12.5 verified
Obtain the IDNum (email address) of some entry in the User table, defined here as UID
Run MySQL and connect with the command "mysql –h 411tpot.cs.odu.edu –uremote –
premotepass tpottest"
Test Case Activity
Pass/Fail
Comments
Expected Result
1
Execute the statement
"describe TA;"
The description of the course table is
printed to the console
2
Visually verify that the
columns of the table
correspond to the
requirements document
section 3.1.3.2.4.8
A list of columns with data type
information is displayed, matching the
requirements document
3
Execute the statement "insert
into TA (uid) values (UID);
Console prints "Query OK, 1 row
affected."
4
Execute the statement "select
* from TA where uid=UID;
One row is displayed.
5
Visually verify that the values
inserted in Step 3 are present
in the row returned.
Contents of the row are those inserted in
Step 3.
Test Category: Unit
Description: Test for the existence, correctness, and proper functioning of the
Master Administrator table
Test Case: 12.8
Case Name: Master
Administrator Table
Requirements
Fulfilled: 3.1.3.2.4.10,
3.1.3.2.4.11,
3.1.3.2.4.12
Purpose: To verify the existence, correctness, and ability to accept insertions of
the Master Administrator table such that it is ready to be used by the Dashboard
and Team Sites.
Version: 1.0
Written By: Aaron Walden
Setup Conditions:





Obtain the requirements document
Open a command prompt
Test Cases 12.1, 12.5 verified
Obtain the IDNum (email address) of some entry in the User table, defined here as UID
Run MySQL and connect with the command "mysql –h 411tpot.cs.odu.edu –uremote –premotepass
tpottest"
Test Case Activity
Pass/Fail
Comments
Expected Result
1
Execute the statement
"describe Master
Administrator;"
The description of the course table is
printed to the console
2
Visually verify that the
columns of the table
correspond to the
requirements document
section 3.1.3.2.4.11
A list of columns with data type
information is displayed, matching the
requirements document
3
Execute the statement "insert
into Master Administrator
(uid) values (UID);
Console prints "Query OK, 1 row
affected."
4
Execute the statement "select
* from Master Administrator
where uid=UID;
One row is displayed.
5
Visually verify that the values
inserted in Step 3 are present
in the row returned.
Contents of the row are those inserted in
Step 3.
Test Category: Unit
Description: Test for the existence, correctness, and proper functioning of the
Team table
Test Case: 12.9
Case Name: Team Table
Requirements
Fulfilled: 3.1.3.2.5.1,
3.1.3.2.5.2, 3.1.3.2.5.3
Purpose: To verify the existence, correctness, and ability to accept insertions of
the Team table such that it is ready to be used by the Dashboard and Team Sites.
Version: 1.0
Written By: Aaron Walden
Setup Conditions:




Obtain the requirements document
Open a command prompt
Test Cases 12.1 verified
Run MySQL and connect with the command "mysql –h 411tpot.cs.odu.edu –uremote –premotepass
tpottest"
Test Case Activity
1
2
3
4
5
Execute the statement
"describe Team;"
Visually verify that the
columns of the table
correspond to the
requirements document
section 3.1.3.2.5.2
Execute the statement "insert
into Team (name, site,
domain) values ('testname',
'site', 'dom');
Execute the statement "select
* from team where
name='testname' order by
idnum asc;
Visually verify that the values
inserted in Step 3 are present
in the last row returned.
Pass/Fail
Comments
Expected Result
The description of the course table is
printed to the console
A list of columns with data type
information is displayed, matching the
requirements document
Console prints "Query OK, 1 row
affected."
At least one row is displayed.
Contents of the last row are those inserted
in Step 3.
Test Category: Unit
Description: Test for the existence, correctness, and proper functioning of the
Actions on Tasks table
Test Case: 12.10
Case Name: Actions on
Tasks Table
Requirements
Fulfilled: 3.1.3.3.1.1,
3.1.3.3.1.2, 3.1.3.3.1.3,
3.1.3.3.1.4
Purpose: To verify the existence, correctness, and ability to accept insertions of
the Actions on Tasks table such that it is ready to be used by the Dashboard and
Team Sites.
Version: 1.0
Written By: Aaron Walden
Setup Conditions:






Obtain the requirements document
Open a command prompt
Test Cases 12.1, 12.3, 12.5 verified
Obtain the IDNum of a Task in the Course table, defined here as TN
Obtain the IDNum (email address) of some entry in the User table, defined here as UID
Run MySQL and connect with the command "mysql –h 411tpot.cs.odu.edu –uremote –premotepass
tpottest"
Test Case Activity
1
2
3
4
5
Execute the statement
"describe acts_on_t;"
Visually verify that the
columns of the table
correspond to the
requirements document
section 3.1.3.3.1.2
Visually verify that
enumerated values of the
Action column are the actions
described in requirements
document section 3.1.3.3.1.3
Execute the statement "insert
into acts_on_t (uid, tid,
action) values (UID, TN,
'Create');
Execute the statement "select
* from acts_on_t where
uid=UIT and tid=TN and
action='create';
Pass/Fail
Comments
Expected Result
The description of the course table is
printed to the console
A list of columns with data type
information is displayed, matching the
requirements document
The enumerated actions match those found
in the requirements document precisely.
Console prints "Query OK, 1 row
affected."
One row is displayed.
6
Visually verify that the values
inserted in Step 4 are present
in the row returned.
Contents of the row are those inserted in
Step 4.
Test Category: Unit
Description: Test for the existence, correctness, and proper functioning of the
Assignment of Tasks table
Test Case: 12.11
Case Name: Assignment
of Tasks Table
Requirements
Fulfilled: 3.1.3.3.2.1,
3.1.3.3.2.2, 3.1.3.3.2.3
Purpose: To verify the existence, correctness, and ability to accept insertions of
the Assignment of Tasks table such that it is ready to be used by the Dashboard
and Team Sites.
Version: 1.0
Written By: Aaron Walden
Setup Conditions:







Obtain the requirements document
Open a command prompt
Test Cases 12.1, 12.3, 12.5 verified
Obtain the IDNum of a Task in the Task table, defined here as TN
Obtain the IDNum (email address) of some entry in the User table, defined here as UID1
Obtain the IDNum (email address) of some other entry in the User table, defined here as UID2
Run MySQL and connect with the command "mysql –h 411tpot.cs.odu.edu –uremote –premotepass
tpottest"
Test Case Activity
1
2
3
4
5
Execute the statement
"describe assigns;"
Visually verify that the
columns of the table
correspond to the
requirements document
section 3.1.3.3.2.2
Execute the statement "insert
into assigns (assigner,
assignee, tid) values (UID1,
UID2, TN);"
Execute the statement "select
* from assigns where
assigner=UID1 and
assignee=UID2 and tid=TN;"
Visually verify that the values
inserted in Step 3 are present
in the row returned.
Pass/Fail
Comments
Expected Result
The description of the course table is
printed to the console
A list of columns with data type
information is displayed, matching the
requirements document
Console prints "Query OK, 1 row
affected."
One row is displayed.
Contents of the row are those inserted in
Step 3.
Test Category: Unit
Description: Test for the existence, correctness, and proper functioning of the
Task Grades table
Test Case: 12.12
Case Name: Task Grades
Table
Requirements
Fulfilled: 3.1.3.3.3.1,
3.1.3.3.3.2, 3.1.3.3.3.3
Purpose: To verify the existence, correctness, and ability to accept insertions of
the Task Grades table such that it is ready to be used by the Dashboard and Team
Sites.
Version: 1.0
Written By: Aaron Walden
Setup Conditions:







Obtain the requirements document
Open a command prompt
Test Cases 12.1, 12.3, 12.5 verified
Obtain the IDNum of a Task in the Task table, defined here as TN
Obtain the IDNum (email address) of some entry in the User table, defined here as UID1
Obtain the IDNum (email address) of some other entry in the User table, defined here as UID2
Run MySQL and connect with the command "mysql –h 411tpot.cs.odu.edu –uremote –premotepass
tpottest"
Test Case Activity
1
2
3
4
5
Execute the statement
"describe receives_grade_t;"
Visually verify that the
columns of the table
correspond to the
requirements document
section 3.1.3.3.3.2
Execute the statement "insert
into receives_grade_t (uid, iid,
tid, grade, feedback) values
(UID1, UID2, TN, '100',
'rad');"
Execute the statement "select
* from receives_grade_t
where uid=UID1 and
tid=TN;"
Visually verify that the values
inserted in Step 3 are present
in the row returned.
Pass/Fail
Comments
Expected Result
The description of the course table is
printed to the console
A list of columns with data type
information is displayed, matching the
requirements document
Console prints "Query OK, 1 row
affected."
One row is displayed.
Contents of the row are those inserted in
Step 3.
Test Category: Unit
Description: Test for the existence, correctness, and proper functioning of the
Team Creation table
Test Case: 12.13
Case Name: Team
Creation Table
Requirements
Fulfilled: 3.1.3.3.4.1,
3.1.3.3.4.2, 3.1.3.3.4.3
Purpose: To verify the existence, correctness, and ability to accept insertions of
the Team Creation table such that it is ready to be used by the Dashboard and
Team Sites.
Version: 1.0
Written By: Aaron Walden
Setup Conditions:






Obtain the requirements document
Open a command prompt
Test Cases 12.1, 12.5, 12.9 verified
Obtain the IDNum of a Team in the Team table, defined here as TN
Obtain the IDNum (email address) of some entry in the user table, defined here as UID
Run MySQL and connect with the command "mysql –h 411tpot.cs.odu.edu –uremote –premotepass
tpottest"
Test Case Activity
Pass/Fail
Comments
Expected Result
1
Execute the statement
"describe creates_t;"
The description of the course table is
printed to the console
2
Visually verify that the
columns of the table
correspond to the
requirements document
section 3.1.3.3.4.2
A list of columns with data type
information is displayed, matching the
requirements document
3
Execute the statement "insert
into creates_t (uid, tid) values
(UID, TN);"
Console prints "Query OK, 1 row
affected."
4
Execute the statement "select
* from creates_t where
uid=UID and tid=TN;"
One row is displayed.
5
Visually verify that the values
inserted in Step 3 are present
in the row returned.
Contents of the row are those inserted in
Step 3.
Test Category: Unit
Description: Test for the existence, correctness, and proper functioning of the
Course Creation table
Test Case: 12.14
Case Name: Course
Creation Table
Requirements
Fulfilled: 3.1.3.3.5.1,
3.1.3.3.5.2, 3.1.3.3.5.3
Purpose: To verify the existence, correctness, and ability to accept insertions of
the Course Creation table such that it is ready to be used by the Dashboard and
Team Sites.
Version: 1.0
Written By: Aaron Walden
Setup Conditions:






Obtain the requirements document
Open a command prompt
Test Cases 12.1, 12.2, 12.5 verified
Obtain the IDNum of a Course in the Course table, defined here as CN
Obtain the IDNum (email address) of some entry in the User table, defined here as UID
Run MySQL and connect with the command "mysql –h 411tpot.cs.odu.edu –uremote –premotepass
tpottest"
Test Case Activity
Pass/Fail
Comments
Expected Result
1
Execute the statement
"describe creates_c;"
The description of the course table is
printed to the console
2
Visually verify that the
columns of the table
correspond to the
requirements document
section 3.1.3.3.5.2
A list of columns with data type
information is displayed, matching the
requirements document
3
Execute the statement "insert
into creates_c (uid, cid) values
(UID, CN);"
Console prints "Query OK, 1 row
affected."
4
Execute the statement "select
* from creates_c where
uid=UID and cid=CN;"
One row is displayed.
5
Visually verify that the values
inserted in Step 3 are present
in the row returned.
Contents of the row are those inserted in
Step 3.
Test Category: Unit
Description: Test for the existence, correctness, and proper functioning of the
Course Grades table
Test Case: 12.15
Case Name: Course
Grades Table
Requirements
Fulfilled: 3.1.3.3.6.1,
3.1.3.3.6.2, 3.1.3.3.6.3
Purpose: To verify the existence, correctness, and ability to accept insertions of
the Course Grades table such that it is ready to be used by the Dashboard and
Team Sites.
Version: 1.0
Written By: Aaron Walden
Setup Conditions:







Obtain the requirements document
Open a command prompt
Test Cases 12.1, 12.2, 12.5 verified
Obtain the IDNum of a Course in the Course table, defined here as CN
Obtain the IDNum (email address) of some entry in the User table, defined here as UID1
Obtain the IDNum (email address) of some entry in the User table, defined here as UID2
Run MySQL and connect with the command "mysql –h 411tpot.cs.odu.edu –uremote –premotepass
tpottest"
Test Case Activity
1
2
3
4
5
Execute the statement
"describe receives_grade_c;"
Visually verify that the
columns of the table
correspond to the
requirements document
section 3.1.3.3.6.2
Execute the statement "insert
into receives_grade_c (uid,
idd, cid, grade, feedback)
values (UID1,UID2, CN,
'100', 'rad');"
Execute the statement "select
* from receives_grade_c
where uid=UID1 and
cid=CN;"
Visually verify that the values
inserted in Step 3 are present
in the row returned.
Pass/Fail
Comments
Expected Result
The description of the course table is
printed to the console
A list of columns with data type
information is displayed, matching the
requirements document
Console prints "Query OK, 1 row
affected."
One row is displayed.
Contents of the row are those inserted in
Step 3.
Test Category: Unit
Description: Test for the existence, correctness, and proper functioning of the
Team Membership table
Test Case: 12.16
Case Name: Team
Membership Table
Requirements
Fulfilled: 3.1.3.3.7.1,
3.1.3.3.7.2, 3.1.3.3.7.3
Purpose: To verify the existence, correctness, and ability to accept insertions of
the Team Membership table such that it is ready to be used by the Dashboard and
Team Sites.
Version: 1.0
Written By: Aaron Walden
Setup Conditions:






Obtain the requirements document
Open a command prompt
Test Cases 12.1, 12.2, 12.5 verified
Obtain the IDNum of a Team in the Team table, defined here as TN
Obtain the IDNum (email address) of some entry in the User table, defined here as UID
Run MySQL and connect with the command "mysql –h 411tpot.cs.odu.edu –uremote –premotepass
tpottest"
Test Case Activity
1
2
3
4
5
Execute the statement
"describe member_of_t;"
Visually verify that the
columns of the table
correspond to the
requirements document
section 3.1.3.3.7.2
Execute the statement "insert
into member_of_t (uid,
teamid, role) values (UID,
TN, 'S');"
Execute the statement "select
* from member_of_t where
uid=UID1 and teamid=TN;"
Visually verify that the values
inserted in Step 3 are present
in the row returned.
Pass/Fail
Comments
Expected Result
The description of the course table is
printed to the console
A list of columns with data type
information is displayed, matching the
requirements document
Console prints "Query OK, 1 row
affected."
One row is displayed.
Contents of the row are those inserted in
Step 3.
Test Category: Unit
Description: Test for the existence, correctness, and proper functioning of the
Course Enrollment table
Test Case: 12.17
Case Name: Course
Enrollment Table
Requirements
Fulfilled: 3.1.3.3.8.1,
3.1.3.3.8.2, 3.1.3.3.8.3
Purpose: To verify the existence, correctness, and ability to accept insertions of
the Course Enrollment table such that it is ready to be used by the Dashboard and
Team Sites.
Version: 1.0
Written By: Aaron Walden
Setup Conditions:






Obtain the requirements document
Open a command prompt
Test Cases 12.1, 12.2, 12.5 verified
Obtain the IDNum of a Course in the Course table, defined here as CN
Obtain the IDNum (email address) of some entry in the User table, defined here as UID
Run MySQL and connect with the command "mysql –h 411tpot.cs.odu.edu –uremote –premotepass
tpottest"
Test Case Activity
Pass/Fail
Comments
Expected Result
1
Execute the statement
"describe enrolled_in;"
The description of the course table is
printed to the console
2
Visually verify that the
columns of the table
correspond to the
requirements document
section 3.1.3.3.8.2
A list of columns with data type
information is displayed, matching the
requirements document
3
Execute the statement "insert
into enrolled_in (uid, cid,
role) values (UID, CN, 'S');"
Console prints "Query OK, 1 row
affected."
4
Execute the statement "select
* from enrolled_in where
uid=UID and cid=CN;"
One row is displayed.
5
Visually verify that the values
inserted in Step 3 are present
in the row returned.
Contents of the row are those inserted in
Step 3.
Test Category: Unit
Description: Test for the existence, correctness, and proper functioning of the
Course Membership table
Test Case: 12.18
Case Name: Course
Membership Table
Requirements
Fulfilled: 3.1.3.3.9.1,
3.1.3.3.9.2, 3.1.3.3.9.3
Purpose: To verify the existence, correctness, and ability to accept insertions of
the Course Membership table such that it is ready to be used by the Dashboard
and Team Sites.
Version: 1.0
Written By: Aaron Walden
Setup Conditions:






Obtain the requirements document
Open a command prompt
Test Cases 12.1, 12.2, 12.9 verified
Obtain the IDNum of a Course in the Course table, defined here as CN
Obtain the IDNum of a Team in the Team table, defined here as TN
Run MySQL and connect with the command "mysql –h 411tpot.cs.odu.edu –uremote –premotepass
tpottest"
Test Case Activity
Pass/Fail
Comments
Expected Result
1
Execute the statement
"describe member_of_c;"
The description of the course table is
printed to the console
2
Visually verify that the
columns of the table
correspond to the
requirements document
section 3.1.3.3.9.2
A list of columns with data type
information is displayed, matching the
requirements document
3
Execute the statement "insert
into member_of_c (teamid,
cid) values (TN, CN);"
Console prints "Query OK, 1 row
affected."
4
Execute the statement "select
* from member_of_c where
teamid=TN and cid=CN;"
One row is displayed.
5
Visually verify that the values
inserted in Step 3 are present
in the row returned.
Contents of the row are those inserted in
Step 3.
Test Category: Unit
Description: Test for the existence, correctness, and proper functioning of the
Task Submission table
Test Case: 12.19
Case Name: Task
Submission Table
Requirements
Fulfilled: 3.1.3.3.10.1,
3.1.3.3.10.2,
3.1.3.3.10.3
Purpose: To verify the existence, correctness, and ability to accept insertions of
the Task Submission table such that it is ready to be used by the Dashboard and
Team Sites.
Version: 1.0
Written By: Aaron Walden
Setup Conditions:







Obtain the requirements document
Open a command prompt
Test Cases 12.1, 12.3, 12.4, 12.5 verified
Obtain the IDNum of a Task in the Task table, defined here as TN
Obtain the slotnum of a Submission Slot in the Submission Slot table, defined here as SN
Obtain the IDNum (email address) of some entry in the User table, defined here as UID
Run MySQL and connect with the command "mysql –h 411tpot.cs.odu.edu –uremote –premotepass
tpottest"
Test Case Activity
1
2
3
4
5
Execute the statement
"describe submits;"
Visually verify that the
columns of the table
correspond to the
requirements document
section 3.1.3.3.10.2
Execute the statement "insert
into submits (uid, tid, slotnum,
file) values (UID, TN, SN,
'x');"
Execute the statement "select
* from submits where
uid=UID and tid=TN and
slotnum=SN;"
Visually verify that the values
inserted in Step 3 are present
in the row returned.
Pass/Fail
Comments
Expected Result
The description of the course table is
printed to the console
A list of columns with data type
information is displayed, matching the
requirements document
Console prints "Query OK, 1 row
affected."
One row is displayed.
Contents of the row are those inserted in
Step 3.
Test Category: Unit
Description: Test for the existence, correctness, and proper
functioning of the Visits table
Test Case: 12.20
Case Name: Visits Table
Requirements Fulfilled:
3.1.3.3.11.1, 3.1.3.3.11.2,
3.1.3.3.11.3
Purpose: To verify the existence, correctness, and ability to accept
insertions of the Visits table such that it is ready to be used by the
Dashboard and Team Sites.
Version: 1.0
Written By: Aaron
Walden
Setup Conditions:






Obtain the requirements document
Open a command prompt
Test Case 12.1, 12.5, 12.9 verified
Obtain the IDNum of a Team in the Team table, defined here as TN
Obtain the IDNum (email address) of some entry in the User table, defined here as UID
Run MySQL and connect with the command "mysql –h 411tpot.cs.odu.edu –uremote –premotepass
tpottest"
Test Case Activity
Pass/Fail
Comments
Expected Result
1
Execute the statement "describe visits;"
The description of the course table
is printed to the console
2
Visually verify that the columns of the
table correspond to the requirements
document section 3.1.3.3.11.2
A list of columns with data type
information is displayed,
matching the requirements
document
3
Execute the statement "insert into visits
(uid, teamid, url) values (UID,TN,
'http://sites.google.com/a/odu.edu/tb');"
Console prints "Query OK, 1 row
affected."
4
Execute the statement "select * from
visits where uid=UID and teamid=TN
order by ts asc;"
At least one row is displayed.
5
Visually verify that the values inserted
in Step 3 are present in the last row
returned.
Contents of the last row are those
inserted in Step 3.
Test Category: Unit
Description: Verify that test data exists for a team with a task due on a future
date
Test Case: 12.21
Case Name: Future Task
Team Test Data
Requirements
Fulfilled: 3.1.4.1
Purpose: To verify that a set of data exists in the database that can be used to
demonstrate the features TPOT prototype with regard to impending task due
dates.
Version: 1.0
Written By: Aaron Walden
Setup Conditions:




Obtain the requirements document
Open a command prompt
Test Cases 12.1, 12.2, 12.3, 12.4, 12.5, 12.9, 12.11, 12.17, 12.20 verified
Run MySQL and connect with the command "mysql –h 411tpot.cs.odu.edu –uremote –premotepass
tpottest"
Test Case Activity
Pass/Fail
Comments
Expected Result
1
Execute the statement "select
* from team;"
A list of teams appears.
2
Choose a team. Note its
IDNum.
IDNum obtained. Hereafter defined as
TMN.
3
Execute the statement "select
* from member_of_c where
teamid=TMN;"
One row is displayed. Obtain the CID of
Team's Course, hereafter defined as CN.
4
Execute the statement "select
* from task where
CourseNum=CN;"
At least one row is displayed. Note the
IDNum of a task with a due date later than
today's date and hereafter refer to it as TN.
5
Execute the statement "select
* from enrolled_in where
teamid=TN;"
A list of students appears. Note the IDNum
of a student and hereafter refer to it as UID.
6
Execute the statement "select
* from sub_slot where
TID=TN;"
At least one row is displayed. Note the
slotnum of the sub_slot and hereafter refer
to it as SN.
5
Execute the statement "select
* from assigns where
assignee=UID;"
At least one row is displayed.
Test Category: Unit
Description: Verify that test data exists for a team with a task due on a
past date
Test Case: 12.22
Case Name: Past Task
Team Test Data
Requirements Fulfilled:
3.1.4.2
Purpose: To verify that a set of data exists in the database that can be used
to demonstrate the features TPOT prototype with regard to previously
submitted files for a task.
Version: 1.0
Written By: Aaron
Walden
Setup Conditions:




Obtain the requirements document
Open a command prompt
Test Cases 12.1, 12.2, 12.3, 12.4, 12.5, 12.9, 12.17, 12.18, 12.20 verified
Run MySQL and connect with the command "mysql –h 411tpot.cs.odu.edu –uremote –premotepass
tpottest"
Test Case Activity
Pass/Fail
Comments
Expected Result
1
Execute the statement "select * from
team;"
A list of teams appears.
2
Choose a team. Note its IDNum,
site, and domain.
IDNum, site, and domain obtained.
Hereafter defined as TMN, DMN,
ST.
3
Visit
http://sites.google.com/a/DMN/ST/
A Team Site exists at the URL.
3
Execute the statement "select * from
member_of_c where teamid=TMN;"
One row is displayed. Obtain the CID
of Team's Course, hereafter defined
as CN.
Execute the statement "select * from
task where CourseNum=CN;"
At least one row is displayed. Note
the IDNum of a task with a due date
earlier than today's date and hereafter
refer to it as TN.
4
5
Execute the statement "select * from
enrolled_in where teamid=TN;"
A list of students appears. Note the
IDNum of a student and hereafter
refer to it as UID.
6
Execute the statement "select * from
submits where TID=TN and
uid=UID;"
At least one row is displayed. Note
the File entry, which should be a
URL.
5
Download the file at the given URL.
File exists.
Component
Req ID
3.1.1.1.1
3.1.1.1.2
3.1.1.1.3
3.1.1.1.4
3.1.1.1.5
3.1.1.2.1.1
3.1.1.2.1.2
3.1.1.2.1.3
3.1.1.2.2.1
3.1.1.2.2.2
3.1.1.2.2.3
3.1.1.2.3.1
3.1.1.2.3.2
3.1.1.2.3.3
3.1.1.2.4.1
3.1.1.2.4.2
3.1.1.2.4.3
3.1.1.2.4.4
3.1.1.2.4.5
3.1.1.2.4.6
3.1.1.2.4.7
3.1.1.2.5.1
3.1.1.2.6.1
3.1.1.2.6.2
3.1.1.2.6.3
3.1.1.2.6.4
3.1.1.2.6.5
3.1.1.2.6.6
3.1.1.2.6.7
3.1.1.2.6.8
1.1
x
x
x
x
x
2.1
3.1
3.2
3.3
3.4
3.5
3.6
Test Case ID
3.7 3.8 4.1
4.2
5.1
6.1
6.2
6.3
x
x
x
x
7.1
7.2
x
x
x
x
x
x
x
x
x
x
x
Component
Req ID
3.1.1.2.7.1
3.1.1.2.7.2
3.1.1.2.7.3
3.1.1.2.7.4
3.1.1.2.7.5
3.1.1.2.7.6
3.1.1.2.7.7
3.1.2.1.1
3.1.2.1.2
3.1.2.1.3
3.1.2.1.4
3.1.2.1.5
3.1.2.1.6
3.1.2.1.7
3.1.2.1.8
3.1.2.1.9
3.1.2.2.1
3.1.2.2.2
3.1.2.2.3
3.1.2.2.4
3.1.2.2.5
3.1.2.3.1
3.1.2.3.2
3.1.2.3.3
3.1.3.1.1
3.1.3.1.1.1
3.1.3.1.2.1
3.1.3.2.1.1
3.1.3.2.1.2
3.1.3.2.1.3
3.1.3.2.2.1
1.1
2.1
3.1
x
3.2
3.3
3.4
3.5
x
x
x
x
x
Test Case ID
3.6 3.7 3.8
x
x
x
x
x
x
x
x
4.1
4.2
5.1
6.1
6.2
6.3
Component
Req ID
3.1.1.2.4.1
3.1.1.2.4.2
3.1.1.2.4.3
3.1.1.2.4.4
3.1.1.2.4.5
3.1.1.2.4.6
3.1.1.2.4.7
3.1.1.2.5.1
3.1.1.2.6.1
3.1.1.2.6.2
3.1.1.2.6.3
3.1.1.2.6.4
3.1.1.2.6.5
3.1.1.2.6.6
3.1.1.2.6.7
3.1.1.2.6.8
3.1.1.2.7.1
3.1.1.2.7.2
3.1.1.2.7.3
3.1.1.2.7.4
3.1.1.2.7.5
3.1.1.2.7.6
3.1.1.2.7.7
3.1.2.1.1
3.1.2.1.2
3.1.2.1.3
3.1.2.1.4
3.1.2.1.5
3.1.2.1.6
3.1.2.1.7
3.1.2.1.8
3.1.2.1.9
Test Case ID
7.3 7.4 7.5 8.1 8.2 9.1 9.2 9.3 9.4 9.5 10.1
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
10.2
10.3
10.4
10.5
10.6
11.1
Component
Req ID
3.1.2.2.1
3.1.2.2.2
3.1.2.2.3
3.1.2.2.4
3.1.2.2.5
3.1.2.3.1
3.1.2.3.2
3.1.2.3.3
Test Case ID
7.3 7.4 7.5 8.1 8.2 9.1 9.2 9.3 9.4 9.5 10.1
x
x
x
10.2
x
x
x
10.3
x
x
x
10.4
x
x
x
10.5
10.6
11.1
x
x
x
x
x
Component
Req ID
3.1.3.1.1.1
3.1.3.1.2.1
3.1.3.2.1.1
3.1.3.2.1.2
3.1.3.2.1.3
3.1.3.2.2.1
3.1.3.2.2.2
3.1.3.2.2.3
3.1.3.2.3.1
3.1.3.2.3.2
3.1.3.2.3.3
3.1.3.2.4.1
3.1.3.2.4.2
3.1.3.2.4.3
3.1.3.2.4.4
3.1.3.2.4.5
3.1.3.2.4.6
3.1.3.2.4.7
3.1.3.2.4.8
3.1.3.2.4.9
3.1.3.2.4.10
3.1.3.2.4.11
3.1.3.2.4.12
3.1.3.2.5.1
3.1.3.2.5.2
3.1.3.2.5.3
3.1.3.3.1.1
3.1.3.3.1.2
3.1.3.3.1.3
3.1.3.3.1.4
12.1
x
x
12.2
12.3
12.4
Test Case ID
12.5
12.6
12.7
12.8
12.9
12.10
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
Component
Req ID
3.1.3.3.2.1
3.1.3.3.2.2
3.1.3.3.2.3
3.1.3.3.3.1
3.1.3.3.3.2
3.1.3.3.3.3
3.1.3.3.4.1
3.1.3.3.4.2
3.1.3.3.4.3
3.1.3.3.5.1
3.1.3.3.5.2
3.1.3.3.5.3
3.1.3.3.6.1
3.1.3.3.6.2
3.1.3.3.6.3
3.1.3.3.7.1
3.1.3.3.7.2
3.1.3.3.7.3
3.1.3.3.8.1
3.1.3.3.8.2
3.1.3.3.8.3
3.1.3.3.9.1
3.1.3.3.9.2
3.1.3.3.9.3
3.1.3.3.10.1
3.1.3.3.10.2
3.1.3.3.10.3
3.1.3.3.11.1
3.1.3.3.11.2
3.1.3.3.11.3
3.1.4.1
3.1.4.2
12.11
x
x
x
12.12
12.13
12.14
12.15
Test Case ID
12.16 12.17
12.18
12.19
12.20
12.21
12.22
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x