Currently we have a environment variable called TEST_TOKEN which is used in those tests. It is a regular User token, and so tests all the authorization and User stuff connected with token processing and verification.
The problem is that it is a regular User token which expires regularly. That means when CI/CD/localhost tests have an expired token, the tests fails, and the deploys are cancelled.
At this time, we are skipping these tests until we can figure out a token trick for this. Developers need to know to get a fresh token from users.t-pen.org to run these tests successfully. Developers should do this anytime changes are made to an authenticated route.
Currently we have a environment variable called TEST_TOKEN which is used in those tests. It is a regular User token, and so tests all the authorization and User stuff connected with token processing and verification.
The problem is that it is a regular User token which expires regularly. That means when CI/CD/localhost tests have an expired token, the tests fails, and the deploys are cancelled.
At this time, we are skipping these tests until we can figure out a token trick for this. Developers need to know to get a fresh token from users.t-pen.org to run these tests successfully. Developers should do this anytime changes are made to an authenticated route.