Cannot run multiple lib generator E2E test suites in parallel on the same workspace

chiubaka / genesis

Creates standardized monorepos and pre-configured project scaffolding for Chiubaka Technologies projects.

2 stars 0 forks source link

Cannot run multiple lib generator E2E test suites in parallel on the same workspace #116

Closed chiubaka closed 2 years ago

chiubaka commented 2 years ago

Generators seem to fail if modifications are being made to other things at the same time.

Long-term solution may be to copy a pre-output template workspace for each E2E test suite and then let it run on that on its own.

Otherwise, runInBand may work so long as parallelism isn't needed to keep CI times down.

Semi-related to #110.

chiubaka commented 2 years ago

This is starting to feel painful, TBH. I don't know how much faster it would be to copy a template project for each lib E2E generator, but the potential advantages are 2-fold:

[ ] Test isolation
[ ] Hopefully faster test runs

Right now running E2E tests takes a long enough time that my developer productivity has dropped precipitously.

chiubaka commented 2 years ago

Best idea right now:

Generate a full genesis workspace
Copy this workspace in its entirety to something like genesis-template
Delete node_modules in this workspace so that copy time improves for all other workspaces copying the template
Have every library project test copy the template workspace and run yarn install as necessary.