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
When testing config import on the frontend, we have grab fixtures from this repo, zip them and import them on CoMapeo. This has shown issues when importing (mostly import not working but not showing any errors nor warnings).
I think this is a somewhat brittle way of testing, since the fixtures are created with a different method than configs themselves.
Maybe the fixtures should be created as unbundled configs (like config repos) and built for testing using the settings-builder itself.
This would give as better reliability for testing configs and avoid pitfalls that are hard to debug
The text was updated successfully, but these errors were encountered:
When testing config import on the frontend, we have grab fixtures from this repo, zip them and import them on CoMapeo. This has shown issues when importing (mostly import not working but not showing any errors nor warnings).
I think this is a somewhat brittle way of testing, since the fixtures are created with a different method than configs themselves.
Maybe the fixtures should be created as unbundled configs (like config repos) and built for testing using the settings-builder itself.
This would give as better reliability for testing configs and avoid pitfalls that are hard to debug
The text was updated successfully, but these errors were encountered: