Is it possible to store a DB connection in global state and use across tests?

do you want to setup different DB connection for each test?

No I want to share 1 connection which I can use across my tests

I have tried to save in global variable but that doesn't work unfortunately

try to use the global setup to connect to your DB https://playwright.dev/docs/test-global-setup-teardown#setup

and you can creae a separate class such as dbContext connect to DB in the global setup and use the dbContext instance in any of your tests

like test.extend(DBhelper)?

try like this: https://stackoverflow.com/questions/65208715/how-to-pass-object-retrieved-from-mongo-db-to-the-test-in-javascript

write your custom helper and use it anywhere 🙂

So sharing between tests is not possible I guess

It's fine, I test file I use the DB a new connection and use it in the testfile

maybe you can do it like in a fixture

DB connection is not compatible with a playwright fixture I guess

try doing like this:

1. define a custom class

class DBContext {

  constructor(connString: string) { }

  /// some logic
  openConnection()
  {

  }

  close() {

  }

  create() {

  }

  read () {

  }

  update() {

  }

  delete() {
    
  }
}

2. in the fixture do the next:

type FixturePages = {
  dbContext: DBContext;
};

export const e2eTest = base.extend<FixturePages>({
  dbContext: async ({}, use) => {
    const dbcontext = new DBContext('someconnstring');
    dbcontext.openConnection();
    await use(dbcontext);
    dbcontext.close();
  }
});

3. Now u r able to use the dbContext in your tests

e2eTest('dbContext', ({ dbContext }) => {
  dbContext.create();
  dbContext.read();
  dbContext.update();
  dbContext.delete();
})

this is working, but this will create a new connection I guess everytime you run a test

Yes you are right.

try use beforeAll/afterAll hooks

define context to use the one instance of the dbContext between your tests

openConnection in the beforeAll and close it in afterAll 🙂

it's sad that you cannot export anything from the spec file. U'd create a global setup and export the db instance it would be really nice

but the tests should be isolated between each other, therefore this is good that each suit u r connecting to the db, innit?