nrwl / nx

Smart Monorepos · Fast CI
https://nx.dev
MIT License
23.71k stars 2.37k forks source link

e2e tests pending #7258

Closed Yohandah closed 3 years ago

Yohandah commented 3 years ago

Current Behavior

It's working perfectly fine when executing cd apps/my-project-e2e/ && cypress run but it doesn't work when I do nx e2e my-project-e2e

When I launch with --watch option I can see this error

image

and the result of the command is "All specs passed" but they're all "pending"

image

When I launch with cypress run all tests pass and they're not pending.

Expected Behavior

nx should work with cucumber ?

Steps to Reproduce

module.exports = (on, config) => { const options = { ...browserify.defaultOptions, typescript: resolve.sync('typescript', { baseDir: config.projectRoot }), };

on('file:preprocessor', cucumber(options)); };


My **angular.json** in case it's useful:

"e2e": { "builder": "@nrwl/cypress:cypress", "options": { "cypressConfig": "apps/myapp-e2e/cypress.json", "devServerTarget": "myapp:serve:development", "tsConfig": "apps/myapp-e2e/tsconfig.json" }, "configurations": { "production": { "devServerTarget": "myapp:serve:production" }, } },


### Environment

Node : 14.17.0 OS : win32 ia32 npm : 6.14.13

nx : 12.9.0 @nrwl/angular : 12.9.0 @nrwl/cli : 12.9.0 @nrwl/cypress : 12.9.0 @nrwl/devkit : 12.9.0 @nrwl/eslint-plugin-nx : 12.9.0 @nrwl/express : Not Found @nrwl/jest : 12.9.0 @nrwl/linter : 12.9.0 @nrwl/nest : 12.9.0 @nrwl/next : Not Found @nrwl/node : 12.9.0 @nrwl/nx-cloud : Not Found @nrwl/react : Not Found @nrwl/schematics : Not Found @nrwl/tao : 12.9.0 @nrwl/web : Not Found @nrwl/workspace : 12.9.0 @nrwl/storybook : 12.9.0 @nrwl/gatsby : Not Found typescript : 4.3.5

Yohandah commented 3 years ago

Turns out this was caused by the fact I was passing TAGS. --env.TAGS="@e2e-tests AND @eConfigNG", when passing tags to cypress run I fall into the same bug.

My bad, sorry for the issue

github-actions[bot] commented 1 year ago

This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context.