Just not sure if this is due to how my app is doing login/auth, or if it is a testcafe issue etc.
So my app uses http only cookies to handle authentication.
If you go to the app/any URL, nginx will redirect you do https://domain/auth/login?orig=
So i've tried setting up a Role that has https://domain or https://domain/auth/login (as the URL for the role).
For my tests, I've tried both have a .page on the fixture, as well as not doing that at all, but putting async t.navigateTo in each test.
So I have 2 test files. Both of their fixtures invoke the Role.
If I run just ONE Of the tests - -it passes (either one).
But if I run them BOTH, the 2nd test always fails hung up on my login page.
I feel like i've tried every combo of Role vs Role URL vs preserveUrl = true vs setting .page on a fixture vs not... and no "combo" seems to end up with my being able to make use of TestCafe to 'test my site'
I really want it to work hah, because i'd rather not go down the Selenium/Nightwatch etc route (that is up next to test out)
I can probably get a test site IP whitelisted & my test files provided if someone thinks they can do a little deep dive into how on earth to make this all work out