You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Once we have completed the feature set for the GameState API, we should update CI so that we test the application twice: one build and test config that uses the GameState API, and one that uses the Legacy API.
Detailed Description
This way we can determine if we have successfully completed all the features such that the app is fully usable in both modes, before we clean up and switch over to the GameState API in production.
One cypress run should build the frontend with VITE_USE_GAMESTATE_API=true, then boot the backend with SAILS_USE_GAMESTATE_API=true and run the tests with CYPRESS_USE_GAMESTATE_API=true.
The other should build, boot, and run the tests without these environment variables set i.e. using the regular commands.
Production config should not be affected and should still OMIT these env vars in order to continue to use the Legacy API
In order to keep CI green, this update should fix all the tests that are broken in both boot modes before it can be merged.
The text was updated successfully, but these errors were encountered:
Feature Summary
Once we have completed the feature set for the GameState API, we should update CI so that we test the application twice: one build and test config that uses the GameState API, and one that uses the Legacy API.
Detailed Description
This way we can determine if we have successfully completed all the features such that the app is fully usable in both modes, before we clean up and switch over to the GameState API in production.
One cypress run should build the frontend with
VITE_USE_GAMESTATE_API=true
, then boot the backend withSAILS_USE_GAMESTATE_API=true
and run the tests withCYPRESS_USE_GAMESTATE_API=true
.The other should build, boot, and run the tests without these environment variables set i.e. using the regular commands.
Production config should not be affected and should still OMIT these env vars in order to continue to use the Legacy API
In order to keep CI green, this update should fix all the tests that are broken in both boot modes before it can be merged.
The text was updated successfully, but these errors were encountered: