Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
D
devstack
Overview
Overview
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
OpenEdx
devstack
Commits
e65c5244
Commit
e65c5244
authored
Aug 14, 2017
by
Jeremy Bowman
Committed by
Jeremy Bowman
Aug 14, 2017
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
PLAT-1683 Run e2e tests in Travis
parent
652c2623
Show whitespace changes
Inline
Side-by-side
Showing
3 changed files
with
16 additions
and
5 deletions
+16
-5
.travis.yml
+1
-0
Makefile
+3
-0
README.rst
+12
-5
No files found.
.travis.yml
View file @
e65c5244
...
@@ -35,4 +35,5 @@ script:
...
@@ -35,4 +35,5 @@ script:
-
sleep 60
# LMS needs like 60 seconds to come up
-
sleep 60
# LMS needs like 60 seconds to come up
-
make healthchecks
-
make healthchecks
-
make validate-lms-volume
-
make validate-lms-volume
-
make e2e-tests
-
make up-marketing-detached
-
make up-marketing-detached
Makefile
View file @
e65c5244
...
@@ -94,6 +94,9 @@ studio-shell: ## Run a shell on the Studio container
...
@@ -94,6 +94,9 @@ studio-shell: ## Run a shell on the Studio container
healthchecks
:
##
Run a curl against all services' healthcheck endpoints to make sure they are up. This will eventually be parameterized
healthchecks
:
##
Run a curl against all services' healthcheck endpoints to make sure they are up. This will eventually be parameterized
./healthchecks.sh
./healthchecks.sh
e2e-tests
:
##
Run the end-to-end tests against the service containers
docker run
-t
--network
=
devstack_default
-v
${
DEVSTACK_WORKSPACE
}
/edx-e2e-tests:/edx-e2e-tests
-v
${
DEVSTACK_WORKSPACE
}
/edx-platform:/edx-e2e-tests/lib/edx-platform
--env-file
${
DEVSTACK_WORKSPACE
}
/edx-e2e-tests/devstack_env edxops/e2e env
TERM
=
$(TERM)
bash
-c
'paver e2e_test --exclude="whitelabel\|enterprise"'
validate-lms-volume
:
##
Validate that changes to the local workspace are reflected in the LMS container
validate-lms-volume
:
##
Validate that changes to the local workspace are reflected in the LMS container
touch
$(DEVSTACK_WORKSPACE)
/edx-platform/testfile
touch
$(DEVSTACK_WORKSPACE)
/edx-platform/testfile
docker
exec
edx.devstack.lms
ls
/edx/app/edxapp/edx-platform/testfile
docker
exec
edx.devstack.lms
ls
/edx/app/edxapp/edx-platform/testfile
...
...
README.rst
View file @
e65c5244
...
@@ -407,17 +407,24 @@ use Firefox instead, prefix the test command with
...
@@ -407,17 +407,24 @@ use Firefox instead, prefix the test command with
Running End-to-End Tests
Running End-to-End Tests
------------------------
------------------------
To run the end-to-end tests for edx-platform, start a shell for the e2e
To run the base set of end-to-end tests for edx-platform, run the following
container and run the tests via paver:
make target:
.. code:: sh
make e2e-tests
If you want to use some of the other testing options described in the
`edx-e2e-tests README`_, you can instead start a shell for the e2e container
and run the tests manually via paver:
.. code:: sh
.. code:: sh
make e2e-shell
make e2e-shell
paver e2e_test --exclude="whitelabel\|enterprise"
paver e2e_test --exclude="whitelabel\|enterprise"
Additional testing options are available as described in the
The browser running the tests can be seen and interacted with via VNC as
`edx-e2e-tests README`_. The browser running the tests can be seen and
described above (Chrome is used by default).
interacted with via VNC as described above (Chrome is used by default).
Troubleshooting: General Tips
Troubleshooting: General Tips
-----------------------------
-----------------------------
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment