-
-
Notifications
You must be signed in to change notification settings - Fork 16
Conversation
launch: { | ||
headless: process.env.HEADLESS !== "false" | ||
headless: process.env.HEADLESS !== 'false', | ||
slowMo: process.env.SLOWMO === 'true' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Was definitely useful in seeing what button was being pressed in real-time.
}, | ||
// https://github.com/smooth-code/jest-puppeteer/tree/master/packages/jest-dev-server#options | ||
server: { | ||
command: "jupyter lab --port 8080 --no-browser", | ||
command: "jupyter lab --port 8080 --no-browser --LabApp.token=''", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah good call
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One less configuration file.
"outDir": "build/test", | ||
"rootDir": "test" | ||
}, | ||
"include": ["test/*", "test/**/*"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah probably good call to separate these
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I recognize that, in other worlds (e.g., Go, Ruby), placing tests next to source files is common; in Node.js land, it isn't for reasons of separation of concerns. Plus, UI tests cross file divides and don't fit nicely into the foo.spec.ts
paradigm where foo
refers to foo.ts
, a source file.
// Load JupyterLab: | ||
await page.goto('http://localhost:8080/lab?reset'); | ||
|
||
// NOTE: depending on system resource constraints, this may NOT be enough time for JupyterLab to load and get "settled", so to speak. If CI tests begin inexplicably failing due to timeout failures, may want to consider increasing the sleep duration... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
:D
// Based on from https://yarnpkg.com/en/package/@rws-air/jestscreenshot | ||
|
||
const PuppeteerEnvironment = require("jest-environment-puppeteer"); | ||
const JestScreenshot = require("@rws-air/jestscreenshot"); | ||
require("jest-circus"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's interesting you didn't need this! Not sure why we did, they just had it here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was present in one of the dep documentation examples. I am not sure why it was there. If it was needed, I would disappointed, as it means importing the package has (gasp) side-effects :|.
I'm loving the green checkmark |
This PR moves files around to minimize the need to rebuild when updating tests and modifies some of the test commands.