Skip to content

Conversation

@JohnC-80
Copy link
Contributor

@JohnC-80 JohnC-80 commented Nov 8, 2024

This is still very WIP...

Thus far there are very few show-stopping changes to tests themselves. Most of them - interactors included - work without issue aside from failures that will need to be investigated.

This suite works in a workspace, but still more work is required (in stripes-cli) for standalone usage.
Code coverage needs to be added (stripes-cli)

Cypress behaviorally requires the presence of a project-level cypress.config.js For convenience I've exported a function to generate the base configuration from stripes-cli.

Automatically, cypress adds a few support directories... will have to check and see if this is still an automatic add when using our tooling.

With this change, you can run yarn test to run cypress tests headlessly or yarn test-dev to run cypress tests within the cypress UI.

@github-actions
Copy link

github-actions bot commented Nov 8, 2024

Bigtest Unit Test Results

0 files   -     1  0 suites   - 1   0s ⏱️ -15s
0 tests  - 1 531  0 ✅  - 1 523  0 💤  - 8  0 ❌ ±0 
0 runs   - 1 533  0 ✅  - 1 525  0 💤  - 8  0 ❌ ±0 

Results for commit 968ebb1. ± Comparison against base commit 2f43c1c.

♻️ This comment has been updated with latest results.

@sonarqubecloud
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant