@ntoll that's always been the case ... but tests has only Python content in it and it's everything but trivial to test for real with a browser ... to be honest I consider that folder for Python tests or Python code while everything running on the front end as JS should imho be easy to verify and check. I wouldn't mind renaming either folder to make things a bit more clear ... such as py-tests for the current tests and js-tests for the others ... would that make more sense to you?

@ntoll to be honest, there is a lot going on in the tests folder and it's fully handled by pytest ... I don't think it would be great to merge the two folders together but as most things are just inside tests/integration maybe I can try to move things around and just have a single tests folder?

@ntoll OK ... I've merged everything into tests ... if CI is happy, I am happy too and we can move forward, I hope that's OK to you too.

Works for me.

Works for me.

not for CI though ... the error in pyscript_dom is super weird ... I have tested manually and everything looks fine? maybe we had some test relying on that test folder first ... investigating.

FYI ... a classic example on why I prefer real browsers and folders with real Web code in there and nothing else ... the pyscript_dom test was based on fake server something and impossible to debug or test, everything has been moved as part of the js-integration test now. CI should go green now and I'll merge after.

OK, I think this is fine now ... it should pass. Basically in pytest we were trusting and using the test folder (not tests) to clone or point stuff at that. I've put back py tests where they were but updated all references to test, now pointing at tests instead. Once this goes green I'll merge but surely we need to create some docs, at some point, to better explain the current state and tests tree to make sense out of it.