porthole/test-requirements.txt
Trung Thai b0e8e0f478 Create an initial Automation Validation Testing framework
- Setting up a runtime environment
- Add to Zuul 'check' and 'gate' pipeline
- Validate concepts:
  1) List a few unit tests successfully
  2) Execute a few simple tests successfully (pass or fail)
  3) Generate docsbuild successfully
- Each UC will have their own test suite and test cases
and will be handled seperately
- add compute-utility deployment into the gate
- add logging collector of primary
- add false / positive test cases
- add unit-test and feature-test gates

Change-Id: I55a0dcf440e9694b041d5fb8eb75bd6f4adb8913
2020-06-12 13:43:58 -04:00

23 lines
613 B
Plaintext

# The order of packages is significant, because pip processes them in the order
# of appearance. Changing the order has an impact on the overall integration
# process, which may cause wedges in the gate later.
# When modifying this file `tox -e freeze-testreq` must be run to regenerate the test-requirements-frozen.txt.
astroid==2.3.3
bandit==1.5.1
flake8==3.6.0
hacking==0.12.0 # Apache-2.0
coverage==4.5.1 # Apache-2.0
pylint==2.4.4
python-subunit==1.3.0 # Apache-2.0/BSD
oslotest==3.7.0 # Apache-2.0
stestr==2.1.1 # Apache-2.0
testtools==2.3.0 # MIT
mock==3.0.5
nose==1.3.7
responses==0.10.2
yapf==0.24.0