The react-screenshot-test-with-create-react-app from fwouts

react-screenshot-test-with-create-react-app's Introduction

This project was bootstrapped with Create React App.

Available Scripts

In the project directory, you can run:

`yarn start`

Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.

The page will reload if you make edits.
You will also see any lint errors in the console.

`yarn test`

Launches the test runner in the interactive watch mode.
See the section about running tests for more information.

`yarn build`

Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.
Your app is ready to be deployed!

See the section about deployment for more information.

`yarn eject`

Note: this is a one-way operation. Once you eject, you can’t go back!

If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.

Instead, it will copy all the configuration files and the transitive dependencies (Webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.

You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.

Learn More

You can learn more in the Create React App documentation.

To learn React, check out the React documentation.

react-screenshot-test-with-create-react-app's People

Contributors

Watchers

react-screenshot-test-with-create-react-app's Issues

Socket hang up issue

Hi @fwouts

thank you for the nice lib, it seems to have a convenient API with multiple screen resolutions support and encapsulates the whole puppeteer/Docker setup problem making the testing easier, so I decided to give it a try. However I hit some issue while running the test for the first time: Error: socket hang up (I have posted the full error output below).

My steps: clone the repo, npm install, npm run screenshot-test-local
My environment is: Ubuntu 16, Node 12

Could you have a look please?

/react-screenshot-test-with-create-react-app-master
> jest -c jest.screenshot.config.js

 FAIL  src/App.screenshot.jsx (10.426s)
  App
    Desktop
      ✕ app (5004ms)
    iPhone X
      ✕ app (5002ms)

  ● App › Desktop › app

    : Timeout - Async callback was not invoked within the 5000ms timeout specified by jest.setTimeout.Timeout - Async callback was not invoked within the 5000ms timeout specified by jest.setTimeout.Error:

      at new Spec (node_modules/jest-jasmine2/build/jasmine/Spec.js:116:22)
      at Suite.<anonymous> (node_modules/react-screenshot-test/dist/lib/react/ReactScreenshotTest.js:141:25)

  ● App › iPhone X › app

    : Timeout - Async callback was not invoked within the 5000ms timeout specified by jest.setTimeout.Timeout - Async callback was not invoked within the 5000ms timeout specified by jest.setTimeout.Error:

      at new Spec (node_modules/jest-jasmine2/build/jasmine/Spec.js:116:22)
      at Suite.<anonymous> (node_modules/react-screenshot-test/dist/lib/react/ReactScreenshotTest.js:141:25)

Test Suites: 1 failed, 1 total
Tests:       2 failed, 2 total
Snapshots:   0 total
Time:        10.445s
Ran all test suites.
events.js:291
      throw er; // Unhandled 'error' event
      ^

Error: socket hang up
    at connResetException (internal/errors.js:609:14)
    at Socket.socketOnEnd (_http_client.js:459:23)
    at Socket.emit (events.js:326:22)
    at Socket.EventEmitter.emit (domain.js:483:12)
    at endReadableNT (_stream_readable.js:1223:12)
    at processTicksAndRejections (internal/process/task_queues.js:84:21)
Emitted 'error' event on ClientRequest instance at:
    at Socket.socketOnEnd (_http_client.js:459:9)
    at Socket.emit (events.js:326:22)
    [... lines matching original stack trace ...]
    at processTicksAndRejections (internal/process/task_queues.js:84:21) {
  code: 'ECONNRESET'
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] screenshot-test-local: `jest -c jest.screenshot.config.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] screenshot-test-local script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/me/.npm/_logs/2020-11-06T07_50_51_545Z-debug.log

Recommend Projects

fwouts / react-screenshot-test-with-create-react-app Goto Github PK

react-screenshot-test-with-create-react-app's Introduction

Available Scripts

yarn start

yarn test

yarn build

yarn eject

Learn More

Code Splitting

Analyzing the Bundle Size

Making a Progressive Web App

Advanced Configuration

Deployment

yarn build fails to minify

react-screenshot-test-with-create-react-app's People

Contributors

Watchers

Forkers

react-screenshot-test-with-create-react-app's Issues

Recommend Projects

Recommend Topics

Recommend Org

`yarn start`

`yarn test`

`yarn build`

`yarn eject`

`yarn build` fails to minify