b952869e6b
This patch implements an integration framework and adds basic test cases to verify whether tacker-horizon is installed and could be opened. The integration test suite "tacker-horizon-integration-tests" is added as a gate job in non-voting mode. Selenium exception details: The tacker-horizon consists of panel groups "VNF Management" and "NFV Orchestration". The selenium reports an exception ElementNotInteractableException while opening pages for panel group "NFV Orchestration". This exception occurs when an element is not clickable or is not visible yet. By default, panel group "VNF Management" is expanded hence test cases for pages under this panel group pass. As per openstack-dashboard integration test case logic, the panel group "NFV Orchestration" is never clicked hence requested pages are not visible. [1] comprises of modified openstack-dashboard integration test logic to fix the above selenium exception. [1] https://review.opendev.org/c/openstack/horizon/+/803465 Implements: blueprint tacker-horizon-integration-test Change-Id: I6a09b945506450d9947afbd92dbab9a4a6c30de4
19 lines
792 B
Plaintext
19 lines
792 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.
|
|
# Order matters to the pip dependency resolver, so sorting this file
|
|
# changes how packages are installed. New dependencies should be
|
|
# added in alphabetical order, however, some dependencies may need to
|
|
# be installed in a specific order.
|
|
#
|
|
# Hacking should appear first in case something else depends on pep8
|
|
hacking>=4.0.0,<4.1.0 # Apache-2.0
|
|
#
|
|
coverage!=4.4,>=4.0 # Apache-2.0
|
|
nodeenv>=0.9.4 # BSD
|
|
# Horizon integration tests requirements
|
|
selenium>=2.50.1 # Apache-2.0
|
|
testtools>=2.2.0 # MIT
|
|
# This also needs xvfb library installed on your OS
|
|
xvfbwrapper>=0.1.3 #license: MIT
|