Skip to content

Commit

Permalink
chore: unscope cypress E2E in CI
Browse files Browse the repository at this point in the history
There is no real reason to scope cypress tests since the `--since`
argument in lage should already help with running only affected tests
  • Loading branch information
ling1726 committed Jun 8, 2022
1 parent 2da2d47 commit 34825be
Showing 1 changed file with 2 additions and 7 deletions.
9 changes: 2 additions & 7 deletions azure-pipelines.yml
Original file line number Diff line number Diff line change
Expand Up @@ -104,14 +104,9 @@ jobs:
# This MUST have a trailing slash, or the links to PR deploy site assets won't work
githubTargetLink: $(deployUrl)/

# only run e2e tests when the appropriate storybook is published by scoping to relevant packages
- script: |
yarn e2e $(sinceArg) --scope @fluentui/react-components
displayName: v9 Cypress E2E tests
- script: |
yarn e2e $(sinceArg) --scope @fluentui/react
displayName: v8 Cypress E2E tests
yarn e2e $(sinceArg)
displayName: Cypress E2E tests
- template: .devops/templates/cleanup.yml

Expand Down

0 comments on commit 34825be

Please sign in to comment.