SuperTokens is an open source authentication solution offering features like: Different types of login: Email / password, Passwordless (OTP or Magic link based).

SuperTokens.com

Hi! 
I would like to programmatically (and locally) test the ST backend SDK (Nodejs) for signing up multiple users (passwordless) and setting user roles. I would also need to programmatically sign-in to simulate being a specific user with a specific role. Could you point me to a guide/example or just give some hints where to start?

hey <@1004662270426619934> sure. Have a look at our tests: https://github.com/supertokens/supertokens-node/blob/master/test/passwordless/apis.test.js#L44

Hi <@498057949541826571>, while I am able to test ST using Postman or Curl (by manually starting my server and ST core locally), I have not managed to get it to work with Supertest.

When I just run a plain Express server, Supertest works. Then I add the SuperTokens-specific code snippets to my server and run the following simple test:
```
test("get local tests working", async () => {
  const response = await supertest(getApp(SubDomain.mgmt)).get("/api");
  expect(response.status).toEqual(200);
});
```
While the response is still 200, the console print the following error message:
```
    Error: Error: Response for preflight has invalid HTTP status code 401
        at Object.dispatchError (/Users/arnewolframm/retality/node_modules/jsdom/lib/jsdom/living/xhr/xhr-utils.js:63:19)
        at EventEmitter.<anonymous> (/Users/arnewolframm/retality/node_modules/jsdom/lib/jsdom/living/xhr/XMLHttpRequest-impl.js:655:18)
        at EventEmitter.emit (node:events:525:35)
        at EventEmitter.emit (node:domain:489:12)
        ...etc...
```
What might I be doing wrong in the setup?

You want to return a 200 from the OPTIONS APi call with the right headers

Sorry, to make this clearer, this would be the call that I am testing for the auth api:

```
await supertest(getApp(SubDomain.mgmt))
    .get("/auth/signup/email/exists")
    .query("email=arne.wolframm@gmail.com");
```
I don't think any additional headers are needed?

preflight usually refers to an OPTIONS APi call

I guess it is a supertest issue. When I run in my terminal:
```curl --location --request GET 'http://localhost:3331/auth/signup/email/exists?email=arne.wolframm@gmail.com'```
I get ```{"exists":true,"status":"OK"}```

When I use the above supertest, I get 401

This also works:
```
const response = await supertest.agent("http://localhost:3331")
    .get("/auth/signup/email/exists")
    .query("email=arne.wolframm@gmail.com");
```
I seem to get the error when I let supertest actually start the server by passing the Express app to it.

Is it possible to get some paid support time to help me setup the testing?

hey <@1004662270426619934> i'll have to get back to you about pricing on monday

Hi Arne. We'd share some pricing after our last call. Did you have any thoughts around that?