centaurustech / course-builder

Automatically exported from code.google.com/p/course-builder
0 stars 0 forks source link

Multiple courses fail unit tests in 1.3.1 #31

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Short version: tools.verify.run_example_activity_tests() assumes that the 
assets folder will stay put, where as the Wiki says you can move around.

What steps will reproduce the problem?

Attempting to follow these intructions 
https://code.google.com/p/course-builder/wiki/RunMultipleCourses

1. Create a '/courses' folder
2. Create a '/courses/a' folder
3. Move '/assets', '/views', 'data', and '/course.yaml' within '/courses/a'
4. Make copy of '/courses/a' at '/courses/b'
5. Add this line 'GCB_COURSES_CONFIG: 'course:/coursea:/courses/a, 
course:/courseb:/' to the app.yaml's 'env_variables' section
6. Start the dev server
7. Visit http://localhost:8080/coursea

What is the expected output? What do you see instead?

When using commit 4aefd57868adb8dde74446b264e833fd7d3ec330 I was able to view 
the two distinct (though otherwise identical) courses at 
http://localhost:8080/coursea and http://localhost:8080/courseb but using 1.3.1 
from the Downloads page, I get this error:

...
  File "/Applications/GoogleAppEngineLauncher.app/Contents/Resources/GoogleAppEngine-default.bundle/Contents/Resources/google_appengine/google/appengine/tools/dev_appserver_import_hook.py", line 1577, in LoadModuleRestricted
    description)
  File "/Users/david/work/prolearn/coursebuilder/tools/verify.py", line 1595, in <module>
    run_all_unit_tests()
  File "/Users/david/work/prolearn/coursebuilder/tools/verify.py", line 1592, in run_all_unit_tests
    run_example_activity_tests()
  File "/Users/david/work/prolearn/coursebuilder/tools/verify.py", line 1580, in run_example_activity_tests
    raise Exception('Missing file: %s', fname)
Exception: ('Missing file: %s', 
'<APPPATH>/tools/../assets/js/activity-examples.js')

This is the bottom of the stack trace and it seems pretty evident what the 
problem is: the assets folder is not where it expects it to be.

What version of the product are you using? On what operating system?
1.3.1, OS X Snow Leopard

Original issue reported on code.google.com by da...@aptwebapps.com on 25 Mar 2013 at 3:49

GoogleCodeExporter commented 9 years ago

Original comment by r...@google.com on 2 Feb 2015 at 11:15