In this case user set 'envdir' that makes all the registered testenvs share the
same venv. In this case tox-bat will recreate same venv for each testenv as
'requirements-test.txt' file belongs to testenv not venv.
In name of the .previous file we use testenv name and if file doesn't exist -
environment needs to be recreated.
Solution
Change name of the .previous file to contain SHA1 of venv path used by testenv
instead of its name.
Normally when user doesn't change 'envdir' manually, each testenv has own venv
and own .previous file.
When user sets 'envdir' to be shared between some testenvs they will share the
same .previous file.
Other changes
Small fix that sorts the parsed requirements and reshuffling or commenting
doesn't cause recreating of the venv.
Testing
Added test for this particular case that checks venv is reused between two
testenvs.
Problem
It is not supported reuse of venv between multiple testenvs. For instance::
In this case user set 'envdir' that makes all the registered testenvs share the same venv. In this case tox-bat will recreate same venv for each testenv as 'requirements-test.txt' file belongs to testenv not venv. In name of the .previous file we use testenv name and if file doesn't exist - environment needs to be recreated.
Solution
Change name of the .previous file to contain SHA1 of venv path used by testenv instead of its name. Normally when user doesn't change 'envdir' manually, each testenv has own venv and own .previous file. When user sets 'envdir' to be shared between some testenvs they will share the same .previous file.
Other changes
Small fix that sorts the parsed requirements and reshuffling or commenting doesn't cause recreating of the venv.
Testing
Added test for this particular case that checks venv is reused between two testenvs.