2df3a6ef11
* All access control logic is now in access.py * It exports a single method for general use: has_access(user, object, action) - possible actions depend on object type (e.g. 'see_exists', 'enroll', 'staff') * Removed DARK_LAUNCH feature flag--it is now the default behavior * Replaced check_course with three separate more focused functions that use has_access Minor things: * note on using pdb in testing * moved time parsing helper into timeparse.py * x_modules now have a .start attribute (None if not in metadata)
1.8 KiB
Running the CMS
One can start the CMS by running rake cms. This will run the server on localhost
port 8001.
However, the server also needs data to work from.
Installing Mongodb
Please see http://www.mongodb.org/downloads for more detailed instructions.
Ubuntu
sudo apt-get install mongodb
OSX
Use the MacPorts package mongodb or the Homebrew formula mongodb
Initializing Mongodb
Check out the course data directories that you want to work with into the
GITHUB_REPO_ROOT (by default, ../data). Then run the following command:
rake django-admin[import,cms,dev,../data]
Replace ../data with your GITHUB_REPO_ROOT if it's not the default value.
This will import all courses in your data directory into mongodb
Unit tests
This runs all the tests (long, uses collectstatic):
rake test
If if you aren't changing static files, can run rake test once, then run
rake fasttest_{lms,cms}
xmodule can be tested independently, with this:
rake test_common/lib/xmodule
To see all available rake commands, do this:
rake -T
To run a single django test class:
django-admin.py test --settings=lms.envs.test --pythonpath=. lms/djangoapps/courseware/tests/tests.py:TestViewAuth
To run a single django test:
django-admin.py test --settings=lms.envs.test --pythonpath=. lms/djangoapps/courseware/tests/tests.py:TestViewAuth.test_dark_launch
To run a single nose test file:
nosetests common/lib/xmodule/xmodule/tests/test_stringify.py
To run a single nose test:
nosetests common/lib/xmodule/xmodule/tests/test_stringify.py:test_stringify
Very handy: if you uncomment the --pdb argument in NOSE_ARGS in lms/envs/test.py, it will drop you into pdb on error. This lets you go up and down the stack and see what the values of the variables are. Check out http://docs.python.org/library/pdb.html