Only parse configuration once per session

[rnestler]

To avoid having to re-read the configuration for every single test we
put it into a "session" fixture. To still have a fresh copy of the
configuration for every test (in case a test modifies it) we wrap it in
a "function" fixture which makes a deepcopy of it.

[rnestler]

General questions, why is conftest.py duplicated in the repo? Can we just symlink on to the other (or will this break stuff on Windows)?

[ElSnoMan]

General questions, why is conftest.py duplicated in the repo? Can we just symlink on to the other (or will this break stuff on Windows)?

This was done at the very beginning of the project when there was a conftest.py specific to the repo and a conftest.py that was meant to be packaged. At first, I was going to use the "plugin" approach so the user wouldn't get a conftest.py file at all (while still having all our fixtures like py), but there were so many different use-cases people had that I hadn't thought of. It was easier to give them the conftest.py file to start so they could edit/extend as needed.

However, now the pylenium.json and conftest.py files are the same at the workspace root and in the scripts folder, so if you know how to remove the duplication, I'm very open to doing so!