General Tests Documentation

UNIT TESTS:

New Row Generator Test: The new row generator test allows us to check if we can create a new row for the rubric while circumventing the UI.

Create Test Project Test: The Create Test Project test allows us to check if we can create a test project and test rubric while circumventing the UI as we are testing the individual functions.

Import Sys Code: This allows us to import the necessary systems, libraries, and other tools while circumventing the UI so that we can run the other tests that were created.

Runnig Unit Tests Test: This allows us just to run all of the tests that were created before we change it to fit the modularization that Daniel has done.

Select Column by Name Tests: This allows us to go and select each individual column by its name while not going through the UI.

Select Index By Group Eva Tests: This allows to go and select each individual evaluation as pseudo students while circumventing the UI.

Select Index By Group Eva Owner Tests: This allows us to go and select each individual evaluation as pseudo instructors while not having to go through the UI.

Select Index By Group Eva Owner Date Tests: This allows us to be pseudo-instructors and access evaluations on a specific day while going around the UI.

Select Students by Group Tests: This allows us to check if we can select each group and each student in each specific group.

Test Get Students by Group Tests: This allows us to check if we can get individual students from each group.

Select Map By Index Tests: This just allows us to access the rubric while bypassing the UI.

New Map Generator Test: This allows us to test if we can create a new rubric.

Select Row by Group ID Test: This allows us to see if we can select each row by each individual group while bypassing the UI.

Select Row by Index Test: This allows us to check if we can select each individual row by its index.

Flask Tests/PyTests:

Flask Tests Notes: This gives us a basic overview on why there is a header in the tests.

ConfTest: This test just configures the environment so we can run the Flask tests while not going through the UI.

Index Test: This test helps us check if we can access the home page of the ELIPSS SkillBuilder website while not going through the UI.

Instructor Dashboard Test: This allows us to check if we can get through the instructor dashboard while bypassing the UI and having to create an account.

Instructor Project Test: This allows us to check if we can log in as a pseudo instructor.

Login Test:This test allows us on the Back-End team to check if we can log in while circumventing the UI.

Sign-Up Test: This test allows us, the Back-End team, to check whether we can or can not sign up/create an account while circumventing the UI.

Create Project Test: These test(s) use GETs and POSTs (when applicable) to the '/create_project' route to check the proper behavior of the @create_project route.

Project Profile Jump-Tool Test: These test(s) use GETs and POSTs (when applicable) to the '/project_profile_jumptool' route to check the proper behavior of the @project_profile_jumptool route.

Search Account Test: These test(s) use GETs and POSTs (when applicable) to the '/search_account' route to check the proper behavior of the search_account route.

Toolbar Test: This test uses GETs to the routes that the toolbar appears in. Each route that contains the toolbar is listed in the array "routes".behavior of the @instructor_project route. The words/phrases asserted below are what the toolbar contains.

Copy Rubric Test:This file (test_copy_rubric.py) contains the functional test(s) for the '/account/success' route. These test(s) use GETs and POSTs (when applicable) to the '/account/success' route to check the proper behavior of the @login route.

Load Project Test: This file (test_load_project.py) contains the functional test(s) for the '/load_project/string:project_id/string:msg' route. These test(s) use GETs and POSTs (when applicable) to the '/load_project/string:project_id/string:msg' route to check the proper behavior of the '/load_project/string:project_id/string:msg' route.

Manage Projects Test: This file (test_manage_projects.py) contains the functional test(s) for the '/project_profile/string:project_id/string:msg' route. These test(s) use GETs and POSTs (when applicable) to the '/login' route to check the proper behavior of the @login route.

Search Project Test: This file (test_search_account.py) contains the functional test(s) for the '/search_project' route. These test(s) use GETs and POSTs (when applicable) to the '/search_account' route to check the proper behavior of the search_project route.