Table of Contents
...
Where's the code?
ORA is broken into two separate repositories:
...
Expand |
---|
title | Deprecated - Vagrant Instructions |
---|
|
DEPRECATED - Using ORA with vagrant devstack(Note that some of this is outdated, I'm working on updating it to match the 2.0.0 release) Initial Setup These are the steps to install ORA2 into your pre-existing devstack image: Clone edx-ora2 into the src directory next to edx-platform folder No Format |
---|
cd src
git clone https://github.com/edx/edx-ora2
git clone https://github.com/edx/edx-submissions |
Install the edx-submissions and ORA2 packages into edx-platform. From devstack do the following (note ORA2 goes first so that we can uninstall its copy of edx-submissions): No Format |
---|
sudo su edxapp
pip uninstall ora2
pip install -e /edx/src/edx-ora2
pip uninstall edx-submissions
pip install -e /edx/src/edx-submissions |
To run the ORA scripts for packaging, testing etc, you should do the following: As edxapp user, run the following. No Format |
---|
sudo su edxapp
cd /edx/src/edx-ora2
# create a new virtualenv
virtualenv edx-ora2
# activate this new virtualenv
source edx-ora2/bin/activate
make install |
You can run the ORA tests as the edxapp user: No Format |
---|
cd /edx/src/edx-ora2
# activate the ORA2 virtualenv
source edx-ora2/bin/activate
make test
# run just the Python tests
make test-python
# debug the Jasmine tests in a browser
make test-js-debug |
When you run the lms do not use the full paver devstack lms or studio commands as they will cause pip to install ORA2 and submissions again. Code Block |
---|
lms runserver --settings=devstack 0.0.0.0:8000 |
After you have run all the setup commands above, when you restart your devstack do the following to execute ORA scripts: No Format |
---|
vagrant ssh
sudo su edxapp
cd /edx/src/edx-ora2
source edx-ora2/bin/activate
# now you can use make commands, such as:
make sass |
Debugging JavaScript tests- Open your browser of choice onto this URL:
http://localhost:9876/debug.html - The tests will be enumerated as they are run, and failures will be shown with stack traces
- You can now use the debug tools in the browser to diagnose the failures
- Note that you can re-run just an individual failing test by clicking on its name
|
...