@xfumihiro

First of all, thanks for sharing the setup configuration, it really helped me to get started with jest + puppeteer.

With my current configuration, I cannot get the reference of global document variable.
I understand that it replaces jest-environment-jsdom with jest-environment-node.
Can you please let me know what I'm missing here & how your example code works?

Thank you.

it('should load without error', async () => {
    let text = await page.evaluate(() => document.body.textContent)
    expect(text).toContain('google')
})

I'm not blocked though, I'm using page.$eval to get element handle.

Is it expected that the setup runs once PER test? This is the output I get:

Determining test suites to run...Setup Puppeteer Environment.
Setup Puppeteer Test Environment.
 PASS  __tests__/test3.js
Setup Puppeteer Test Environment.
 PASS  __tests__/test1.js
Setup Puppeteer Test Environment.
 PASS  __tests__/test2.js
Setup Puppeteer Test Environment.
 PASS  __tests__/test5.js
Setup Puppeteer Test Environment.
 PASS  __tests__/test4.js

Test Suites: 5 passed, 5 total
Tests:       5 passed, 5 total
Snapshots:   0 total
Time:        2.049s
Ran all test suites.
Teardown Puppeteer Environment.

I can't see an explanation here or in this repo...

Why is it so complicated?

The examples show test google.com, it's online server.

Is there a way we can configure the config files and run puppeteer in headless or non-headless mode from command line. if yes, how ? If you could share that will be great.

chrome changed behaviour where if you are on google.com, it goes to startup page instead of the actual site. your sample tests are hitting this case and never finishing since you are never on an actual website

Hi @xfumihiro,

This is really cool that you have put this example together and would be definitely very helpful.
While ago I started a project with the same purpose and has a full integration of jest and puppeteer in it.
https://github.com/NimaSoroush/differencify
jest section:
https://github.com/NimaSoroush/differencify#usage-with-jest

Maybe worth linking these two projects together. Let me know what are your thoughts?

How can we run all test in our own order like
I want to run all tests in ascending or Descending order how can I do?

Question: should we be closing the page after each test? eg:

afterAll(async () => {
  await page.close()
})

I'm starting from scratch learning node + jest + puppeteer and this repo really helped, thanks!

I would add the commands needed to run it, as it would make it easier for people new to the frontend world to have a working test suite of jest + puppetter. These steps may be

1. Install node dependencies from package.json using npm (or yarn)
   npm install
2. Run jest from the recently installed package (not global)
   /usr/bin/env node node_modules/jest/bin/jest.js
3. Confirm that all the tests passed (image from README.md)

These steps were the ones I found to work but maybe there's a better or more general way.