We have some remix integration tests that we run separately. IMHO we should just refactor these to be regular E2E test apps - we already have some remix ones, so possibly we can even get rid of this completely…
We would lose the node coverage but we do not really test this for other, more important frameworks as well, so I think this would be OK.
Steps:
- Investigate what is covered by remix integration tests and what is covered by existing remix e2e tests
- For the gap, either add tests to existing e2e test (if possible), or create a new e2e test app if the setup is completely separate
- Stop testing different node versions for remix, unless there is specific reason to do so (same as for all other SDKs)
We have some remix integration tests that we run separately. IMHO we should just refactor these to be regular E2E test apps - we already have some remix ones, so possibly we can even get rid of this completely…
We would lose the node coverage but we do not really test this for other, more important frameworks as well, so I think this would be OK.
Steps: