Support a jasmine.yml file.

[jakeharding]

Investigate if the jasmine.yml will be able to replace the files.json and support test files in separate directories.

[DanielSwain]

Here is an explanation that shows Jasmine's native structure: http://bittersweetryan.github.io/jasmine-presentation/#slide-24 http://bittersweetryan.github.io/jasmine-presentation/#slide-25

I think that an ideal setup would keep the native Jasmine structure as much as possible but provide for storing tests within the individual app folders. Here would be one way to do this: Have a DJANGO_JASMINE_TESTS_DIRECTORY_NAME constant in settings.py. This variable would designate the Jasmine folder name that django_jasmine would look for in each app. Then, django_jasmine would look for the "spec" folder in each app's DJANGO_JASMINE_TESTS_DIRECTORY_NAME folder in order to find all the tests for the app. Then, it would be very useful if the django_jasmine interface, after finding all the tests, would provide a multi-select dropdown which could be used to select which tests are to be run. Ideally, the multi-select would show the tests grouped by app.

[DanielSwain]

I would also suggest changing the template name from index.html to SpecRunner.html. This keeps with the Jasmine naming conventions as much as possible and is also more explicit as far as indicating what the template is used for.

[DanielSwain]

You could disregard the comment above about multi-select. I see that the django_jasmine spec runner interface provides a clickable link which will run just one spec at a time.

[DanielSwain]

I think that the "fixtures" explanation in the ReadMe could stand a little improvement - the explanation is not in complete sentences. Also, it seems that execution of the fixturesPath() command should be optional since the Jasmine default is to find fixtures in a folder entitled "fixtures" (note that the Jasmine standard actually follows (this hierarchy): spec/javascripts/fixtures. An explanation of this default layout/behavior and the optional use of the fixturesPath() command would be helpful (see the explanation of this default layout/behavior here) along with ensuring that this default behavior is honored in django_jasmine. (I personally don't see why they have to have "fixtures" within "javascripts" and find that unhelpful.)

[DanielSwain]

It would be useful if the filename of the spec was placed as a group header above the specs within the file. It would also be nice if the "describe" was separated from each "it" with some sort of character, perhaps a colon (and if this is done, then do it in the corresponding titles of each of the <li>s in the <ul class="jasmine-symbol-summary"> ).