User authentication is now in place so current tests/savedPins.js fails and needs to be refactored to incorporate authentication rules. See #38 for overview of authentication concept and verifyToken method to see how we pass approved token around.
As a quick overview, when a user logs in or registers an account successfully a token is generated and assigned to the user until they log out or it expires. This token is used to authenticate the user's access to secure end points on the server - primarily saved pins and directions and search history. You will need to incorporate the passing of a valid toke into the unit test.
User authentication is now in place so current tests/savedPins.js fails and needs to be refactored to incorporate authentication rules. See #38 for overview of authentication concept and
verifyTokenmethod to see how we pass approved token around.As a quick overview, when a user logs in or registers an account successfully a token is generated and assigned to the user until they log out or it expires. This token is used to authenticate the user's access to secure end points on the server - primarily saved pins and directions and search history. You will need to incorporate the passing of a valid toke into the unit test.