Browsers executables must be put into virtualenv/Scripts folder along with Python.exe to avoid PATH issues. This is dependant on OS used. Current implementation is done for Windows 10.
How to set up:
- Install Python
- Install virtualenv
pip install virtualenv
- Create virtualenv
virtualenv <virtual environment name>
- Activate virtualenv from CLI:
.\<env name>\Scripts\activate
- Execute in CLI from respective folder:
pip install -r requirements.txt
to install project libs - For Windows: execute following in MSPowerShell to install scoop (package manager for windows) and following:
Set-ExecutionPolicy RemoteSigned -scope CurrentUser
to set rightsiex (new-object net.webclient).downloadstring('https://get.scoop.sh')'
- Install allure framework(MSPowerShell):
scoop install allure
- For other OSs please look into https://docs.qameta.io/allure/#_linux
How to run:
- Build and execute CLI command from runners.sh (eg.
pytest -s -v -tb=line --alluredir=/tmp/my_allure_results
) under the respetive virtuanv activated.- This will collect and execute tests. Also allure dfata would be stored.
- Run allure report by
allure serve <report folder>
(eg.allure serve /tmp/my_allure_results
)- This will run web server with report page generated. Run history for each TC is supported. But real time update is not, sp you need to rerun allure serve after each test execution.
DoD:
- Initial Structure
- Reporting Engine
- Some Smoke tests with FAILED reporting by trace and screenshot on failure
- Actual story test coverage