Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Randomize the CLI's tests #1317

Open
jackofdiamond5 opened this issue Sep 16, 2024 · 0 comments
Open

Randomize the CLI's tests #1317

jackofdiamond5 opened this issue Sep 16, 2024 · 0 comments
Assignees
Labels
cli-package igniteui-cli package commands core @igniteui/cli-core package enhancement 🆕 status: new priority: low schematics templates component OR scenario template tests

Comments

@jackofdiamond5
Copy link
Member

Description

Currently, the CLI's tests are ran in a particular order. First acceptance tests and then unit tests. The acceptance tests create an instance of the App.container which is later on accessed by the unit tests. If the unit tests are ran before the acceptance tests, they will throw. Additionally, running only the unit tests is impossible unless a call to App.initialize is made at the beginning of the spec file. The current implementation is not correct since we should not have to rely on test order at all and every test case should be isolated.

As a side note - for all of the unit tests, we may want to ensure that any calls to the App.container are fully mocked and no calls to App.initialize are needed to run the tests normally.

  • Ignite UI CLI version: latest
  • Framework: n/a
  • Project type: n/a

Expected result

The CLI's tests should be completely randomized on every run.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cli-package igniteui-cli package commands core @igniteui/cli-core package enhancement 🆕 status: new priority: low schematics templates component OR scenario template tests
Projects
None yet
Development

No branches or pull requests

2 participants