Probably it does not make much sense to use jest-dev-server there. I thought about the following:

startup/teardown hooks in the playwright.config
startup/teardown hooks if you test multiple browsers
There you can basically implement your own customisable async function to use e.g. that: https://www.npmjs.com/package/wait-on or execute shell commands (maybe provide a small helper for that)

e.g.

const waitOn = require('wait-on');

module.exports = {
  browsers: ['chromium', 'webkit'],
  contextOptions: {
    viewport: {
      width: 1234,
      height: 789,
    },
  },
  setup: async (state, { execCommand, runInBackground }) => {
    await execCommand('createdb foobar');
    // start the backend
    runInBackground('python manage.py runserver');
    runInBackground('nginx -d');
    // Wait until its reachable
    await waitOn({
      resources: 'http://localhost:8080'
    });
  },
  teardown: async (state, { execCommand, killBackgroundProcesses }) => {
    await killBackgroundProcesses();
    await execCommand('dropdb foobar');
  }
};

setup/teardown #9

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions