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
@eBsowka we were discussing with @hms1 about the newly added functionalities.
A main struggle with assertions if using a demo env is the volatility of the app and the collections.
We have attempted in the past to use a mongo db to connect to with success that is created on the fly in the CI with mongo dumps. In this scenario, we would need to take it a step further, where we have an instance of CB running that we have full control of, and for the test we would
purge all collections available
resurrect with the db that we have saved from the dumped collections
This would reassure us that we are not breaking anything in the package without having to account for CB app unpredictable changes.
This is low priority for now, but keeping it as we have committed to ensure reproducibility for mongo related CI tests.
The text was updated successfully, but these errors were encountered:
@eBsowka we were discussing with @hms1 about the newly added functionalities.
A main struggle with assertions if using a demo env is the volatility of the app and the collections.
We have attempted in the past to use a mongo db to connect to with success that is created on the fly in the CI with mongo dumps. In this scenario, we would need to take it a step further, where we have an instance of CB running that we have full control of, and for the test we would
This would reassure us that we are not breaking anything in the package without having to account for CB app unpredictable changes.
This is low priority for now, but keeping it as we have committed to ensure reproducibility for mongo related CI tests.
The text was updated successfully, but these errors were encountered: