Server

On this page, you'll find references for the following requests in the given sections.

• User Management
• User Information
• Action
• Reaction
• Receive an AREA

WARNING

You must check in our database that your name account isn't registered yet.

On this page when it's come talking about the database, we assume that we are talking about seeing Atlas from MongoDB.

If you don't have access to the link, contact our group leader.

User Management

This part is identified as the code UM.

Step.1 - Register:

Test:

Register a User by using an HTTP Request (Postman OR Insomnia).

Documentation about Register can be found here.

Result & Check:

According to the documentation check if the response is successful.

Then check into the database if your account has been created.

WARNING: From this point when it will come talking about a user it will be the user who has been just created.

Step.2 - Login:

Test:

Login to the previously registered User by using an HTTP Request (Postman OR Insomnia).

Documentation about Login can be found here.

Result & Check:

According to the documentation check if the response is successful.

Then check into the database if your account has the good credentials used.

Step.3 - About.json:

Test:

Proceed a GET request to the about.json page by using an HTTP Request (Postman OR Insomnia).

Documentation about About.json page can be found here.

Result & Check:

According to the documentation check if the response is successful.

User Information

This part is identified as the code UI.

Step.1 - JWT Validity:

Test:

Check JWT Validity by using an HTTP Request (Postman OR Insomnia).

Documentation about JWT Validity can be found here.

Result & Check:

According to the documentation check if the response is successful.

Step.2 - GET INFO:

Test:

Get user information by using an HTTP Request (Postman OR Insomnia).

Documentation about GET Info can be found here.

Result & Check:

According to the documentation check if the response is successful.

Then compare to the field designated for this given user in the database.

Step.3 - Add Area:

Test:

Add an area (action/reaction) by using an HTTP Request (Postman OR Insomnia).

Documentation about adding an area can be found here.

Result & Check:

According to the documentation check if the response is successful.

Then compare to the field designated for this given user in the database.

Step.4 - Delete Area:

Test:

Delete an area (action/reaction) by using an HTTP Request (Postman OR Insomnia).

Documentation about deleting an area can be found here.

Result & Check:

According to the documentation check if the response is successful.

Then compare to the field designated for this given user in the database.

Action

This part is identified as the code A.

Step.1 - Adding Action:

Test:

Add an area (action/reaction) by using an HTTP Request (Postman OR Insomnia).

Documentation about adding an area can be found here.

Result & Check:

According to the documentation check if the response is successful.

Then compare to the field designated for this given user in the database.

WARNING: This step has to be done for every set Action.

Documentation about Action can be found here.

Step.2 - Deleting Action:

Test:

Delete an area (action/reaction) by using an HTTP Request (Postman OR Insomnia).

Documentation about deleting an area can be found here.

Result & Check:

According to the documentation check if the response is successful.

Then compare to the field designated for this given user in the database.

WARNING: This step has to be done for every set Action.

Documentation about Action can be found here.

Reaction

This part is identified as the code R.

Step.1 - Adding Reaction:

Test:

Add an area (action/reaction) by using an HTTP Request (Postman OR Insomnia).

Documentation about adding an area can be found here.

Result & Check:

According to the documentation check if the response is successful.

Then compare to the field designated for this given user in the database.

WARNING: This step has to be done for every set Reaction.

Documentation about Action can be found here.

Step.2 - Deleting Reaction:

Test:

Delete an area (action/reaction) by using an HTTP Request (Postman OR Insomnia).

Documentation about deleting an area can be found here.

Result & Check:

According to the documentation check if the response is successful.

Then compare to the field designated for this given user in the database.

WARNING: This step has to be done for every set Reaction.

Documentation about Action can be found here.

Receive an AREA

This part is identified as the code AREA.

Step.1 - Void Area:

Test:

Add an area (action/reaction) by using an HTTP Request (Postman OR Insomnia). Delete an area (action/reaction) by using an HTTP Request (Postman OR Insomnia).

Documentation about adding an area can be found here.

Documentation about deleting an area can be found here.

Result & Check:

According to the documentation check if the response is successful for both requests.

Then compare to the field designated for this given user in the database for both requests.

Then look at the server logs to verify that no area (action/reaction) are active.

Step.2 - Testing Area:

Test:

Add an area (action/reaction) by using an HTTP Request (Postman OR Insomnia).

Documentation about adding an area can be found here.

Result & Check:

According to the documentation check if the response is successful for both requests.

Then compare to the field designated for this given user in the database for both requests.

Then look at the server logs to verify that the area set (action/reaction) is active.

Then look at your designated reaction method to see if you're getting action triggered.

Test clean:

Delete your just set area (action/reaction) by using an HTTP Request (Postman OR Insomnia).

Documentation about deleting an area can be found here.

WARNING: This step has to be done for every combination of Action / Reaction.

Documentation about Action can be found here.

Documentation about Action can be found here.