Integration and unit tests using Cypress #1
Conversation
cypress/integration/actions_spec.js
Outdated
| todos: [] | ||
| } | ||
| const result = actions.add()(state) | ||
| cy.wrap(result).should('deep.equal', { |
There was a problem hiding this comment.
Out of curiousity, why cy.wrap over expect? It looks like cypress bundles with chai's expect, so I'm curious if it's the convention of cypress, support for cy.wrap is better, or just personal preference.
There was a problem hiding this comment.
same thing, I changed it to simple expect, no preference
| @@ -0,0 +1,39 @@ | |||
| /// <reference types="cypress" /> | |||
There was a problem hiding this comment.
this turns on IntelliSense for Cypress type in JS specs in VSCode for example
README.md
Outdated
| To run tests in the interactive mode, start the server and then open Cypress | ||
|
|
||
| ``` | ||
| npm start & |
There was a problem hiding this comment.
I prefer not suggesting running a process in the background, simply because not everyone has a lot of sh experience. Is it possible to use your start-server-and-test package to do something like: start-server-and-test start http://localhost:8080 test?
There was a problem hiding this comment.
I changed the npm test command and updated the README
|
Great feedback, I think I addressed it all in two commits |
package.json
Outdated
| "babel-loader": "^8.0.0-beta.0", | ||
| "css-loader": "^0.28.11", | ||
| "cypress": "^2.1.0", | ||
| "cypress-hyperapp-unit-test": "0.0.0-development", |
There was a problem hiding this comment.
hmm, this does not look right, the version is incorrect
|
Awesome @bahmutov thanks for the contribution 👍 💯 🥇 |
Here is an example mounting Hyperapp view function as a component and then driving it via Cypress. Also unit testing actions.
cypress-hyperapp-unit-testThe integration test checks if
TestItemrenders class, responds to click.Also added
npm run cicommand that can run the tests on CI by starting the server, waiting for it to respond, run Cypress, then shutdown the server.