perf(`@fluentui/e2e`): slow cypress tests execution
Describe the issue:
It turns out that executing yarn workspace @fluentui/e2e test takes significant time to run time from our PR CI pipeline exectuion duration (in avg 33% when affected).
Technical details:
- cypress is used to execute those tests
We should investigate why is that happening and improve execution performance.
Actual behavior:
On my local machine (M1) the whole test case suite takes almost 10 minutes Finished 'test' after 9.27 min
Expected behavior:
e2e tests execution time should be improved
did some initial investigation:
test task consist of following phases:
- bundling (webpack)
- starting express server that serves build assets
- cypress run
bundling (Webpack)
time duration: approx 30 seconds.
- tried to use esbuild-loader instead babel-loader ( non observable effect )
- the main slow-down is typescript which is invoked via
ForkTsCheckerWebpackPlugin. By removing type checking from build process the compilation improved by 40% !- actionable: move type-checking to separate pipeline (
type-checktask)
- actionable: move type-checking to separate pipeline (
starting express server that serves build assets
Fast. no actionable needed.
cypress run
time duration: approx 8 minutes.
Extremely slow 🚨
- tried to use esbuild (https://github.com/bahmutov/cypress-esbuild-preprocessor) for spec compilation, which is a no go (failed) as spec files are using
__filenameand other nodejs globs that are not supported by esbuild
update:
turns out we are on cypress version that doesn't support native M1 https://github.com/microsoft/fluentui/pull/24462
Because this issue has not had activity for over 150 days, we're automatically closing it for house-keeping purposes.
Still require assistance? Please, create a new issue with up-to date details.
Because this issue has not had activity for over 150 days, we're automatically closing it for house-keeping purposes.
Still require assistance? Please, create a new issue with up-to date details.
Because this issue has not had activity for over 150 days, we're automatically closing it for house-keeping purposes.
Still require assistance? Please, create a new issue with up-to date details.
Because this issue has not had activity for over 150 days, we're automatically closing it for house-keeping purposes.
Still require assistance? Please, create a new issue with up-to date details.
as v0 is in maintenance mode, this will be probably closed as wont fix as v0 will be branched to follow our LTS policy
This issue has not had activity for over 180 days! We're adding Soft close label and will close it soon for house-keeping purposes. Still require assistance? Please add comment - "keep open".
This issue has not had activity for over 180 days! We're adding Soft close label and will close it soon for house-keeping purposes. Still require assistance? Please add comment - "keep open".
This issue has not had activity for over 180 days! We're adding Soft close label and will close it soon for house-keeping purposes. Still require assistance? Please add comment - "keep open".