You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: cli/__snapshots__/cli_spec.js
+17-7
Original file line number
Diff line number
Diff line change
@@ -18,10 +18,10 @@ exports['shows help for open --foo 1'] = `
18
18
Options:
19
19
-b, --browser <browser-path> path to a custom browser to be added to the
20
20
list of available browsers in Cypress
21
+
--component runs component tests
21
22
-c, --config <config> sets configuration values. separate multiple
22
23
values with a comma. overrides any value in
23
24
cypress.json.
24
-
--ct, --component runs component tests
25
25
-C, --config-file <config-file> path to JSON file where configuration values
26
26
are set. defaults to "cypress.json". pass
27
27
"false" to disable.
@@ -66,7 +66,7 @@ exports['shows help for run --foo 1'] = `
66
66
Options:
67
67
-b, --browser <browser-name-or-path> runs Cypress in the browser with the given name. if a filesystem path is supplied, Cypress will attempt to use the browser at that path.
68
68
--ci-build-id <id> the unique identifier for a run on your CI provider. typically a "BUILD_ID" env var. this value is automatically detected for most CI providers
69
-
--ct, --component runs component tests
69
+
--component runs component tests
70
70
-c, --config <config> sets configuration values. separate multiple values with a comma. overrides any value in cypress.json.
71
71
-C, --config-file <config-file> path to JSON file where configuration values are set. defaults to "cypress.json". pass "false" to disable.
72
72
--e2e runs end to end tests
@@ -218,7 +218,9 @@ exports['cli help command shows help 1'] = `
218
218
open [options] Opens Cypress in the interactive GUI.
219
219
run [options] Runs Cypress tests from the CLI without the GUI
Copy file name to clipboardexpand all lines: npm/react/examples/find-webpack/README.md
+4-4
Original file line number
Diff line number
Diff line change
@@ -71,7 +71,7 @@ Most tests will start with `mount` from `@cypress/react`. This is similar to `re
71
71
Open the component testing runner with:
72
72
73
73
```sh
74
-
yarn cypress open-ct
74
+
yarn cypress open --component
75
75
```
76
76
77
77
And select the spec to run.
@@ -80,7 +80,7 @@ And select the spec to run.
80
80
81
81
Try making a change - the tests will re-run instantly. You not only immediately know if the test passed or failed, but be able to visually inspect and debug any changes.
82
82
83
-
You can run all the specs with `yarn cypress run-ct`. This is useful for executing all the specs in a CI environment, or one last check before you commit and push your code!
83
+
You can run all the specs with `yarn cypress run --component`. This is useful for executing all the specs in a CI environment, or one last check before you commit and push your code!
84
84
85
85
## Discussion
86
86
@@ -90,13 +90,13 @@ Cypress Component Testing is an alternative to a jsdom based testing environment
90
90
- Visual. You can see exactly what is rendered. No more scrolling through a cryptic terminal log to figure out what is rendered or to debug - just open the devtools and browse the DOM.
91
91
- Powered by Cypress - the most popular and reliable E2E testing tool out there.
92
92
93
-
It also doubles as a *design environment*. You can see the component as you develop it, and hot reload give you a near instance feedback loop. It can potentially take the place of not only your Jest based test infrastructure, but your Storybook based design infrastructure as well.
93
+
It also doubles as a *design environment*. You can see the component as you develop it, and hot reload give you a near instance feedback loop. It can potentially take the place of not only your Jest based test infrastructure, but your Storybook based design infrastructure as well.
94
94
95
95
Cypress Component Testing is still in alpha but the product is quickly evolving and promises to change the landscape of Component Testing.
96
96
97
97
## Conclusion
98
98
99
-
Cypress Component Testing brings everything that is great about Cypress to Component Testing. Since the underlying adapters are built on libraries like Webpack, you don't need to throw away your entire test suite - incremental migration is more than possible.
99
+
Cypress Component Testing brings everything that is great about Cypress to Component Testing. Since the underlying adapters are built on libraries like Webpack, you don't need to throw away your entire test suite - incremental migration is more than possible.
100
100
101
101
The visual aspect united testing and design in a single tool. My days of grepping a messy console output to figure out what the user will see are over - I can see exactly what the component will look like as my tests run.
0 commit comments