11) Server Tests

Running Server Tests

Our tests are to ensure that the implemented features work on our web application. To run the current tests we have implemented on our server, you have to have MongoDB running on the background in order to test if the information is stored properly.

In the repository, run:
gulp test:server

Testing Information

Appointment Test

• should not create the appointment
• should get appointment
• should not get appointment
• should get all appointments
• should update appointment
• should delete appointment

Company Test

• should not create the company
• should get company
• should not get company
• should get all companies
• should update company
• should delete company

Employee Testing

• should save submitted employee
• should login with employee data
• should not log in with employee data
• should update the employee data
• should login with new password
• should return all employees
• should return a specific employee
• should delete the employee data

Form Templates

• should save the template
• should responde with company template data
• should delete the template data

Submitted forms

• should save submitted form
• should respond with submitted form data

Notification

• should send an email
• should send an text

Visitor List Socket

• should add visitors to list
• should get visitors from list
• should remove visitor from list

Theme Settings Model

• should create(POST) a new setting
• should update(PUT) theme setting

Themes Route Test

• should respond with theme info for respective user_id settings that were created for first time user
• should respond with theme info for respective user_id
• should respond with theme info for respective user_id settings that were updated
• should respond with successful delete

Visitor List

• should add visitors to list
• should get visitor list
• should not get visitor list
• should delete specified visitor
• should clear visitorLists