And a —tags, -t option

To help find flaky tests. It could look like

const { test, times } = require('@ianwalter/bff')

test('click handler', times(10), ({ expect }) => {
  let testValue = 'foo'
  const a = document.createElement('a')
  a.onclick = () => (testValue = 'bar')
  a.click()
  expect(testValue).toBe('bar')
})
``

And allow the plugins to register hooks with matching method names on modules.export

Registration pool is not really being terminated when it should be.

To allow control over the max amount of workers in the worker pool.

So that the snapshots are compatible with snapshot IDE plugins.

Default to a no-op function for the test function if not provided so you can do something like:

test.skip('TODO')

I guess you could hack something together with a plugin and a registration hook, but an official API would be cool.

• Allow bff to consider *pptr.js files as puppeteer-based tests by default
• Add a puppeteer config option to use for puppeteer config and enabling using puppeteer for specified tests
• Add a browser file with a registration method and runTest method
• During registration action, if fileContext.isPuppeteer is true, compile the test file together with the browser file using Webpack and save it to a tmp file. Then launch puppeteer to run registration in a browser and return the evaluation of a registration call.
• During test action, if isPuppeteer, launch puppeteer with compiled file and add the browser and page to the context.
• In the test action, if isPuppeteer, return evaluation of a runTest call instead of requiring the test file.
• Handle puppeteer test result

Fail test if there is an error AND evaluation returns undefined.

That can add to test context and modify test name.

Allow options some (default) and every.

Add something like let plugin; try { plugin = require(file) } catch (err) {}; plugin = plugin || require(resolve(file))

Might be a good idea for a modifier as well.

Like test.skip, test.tags, and/or test.only.

Add Modifiers and Tags sub-sections and Hooks section.

Still try to run after hooks on first sigint since they will likely be used for cleanup.

That runs something with run context, so like:

test('something', async ({ expect, browser, failure }) => {
  failure(async () => await browser.pause(99999))
  for (const button of buttons) {
    const element = await browser.$(button)
    expect(await button.getText()).toBe('Submit')
  }
})