Include Types

2 views
Skip to first unread message

Michael Gaffney

unread,
Sep 16, 2009, 12:32:36 PM9/16/09
to jasmi...@googlegroups.com
I'm wondering if there is any plan to add / standardize the different
categories of JS files loaded via the server for a jasmine run. The
current (for jasmine itself) is:

-source [jasmine split source files]
-specs
-css

However, for other apps, I would propose the following sets of files:

-jasmine [the lib/jasmine files including css]
-source [the application's source code, recursive]
-matchers [the application's custom matchers, recursive]
-specs [the applications custom specs, recursive]

Which would map for jasmine itself to:

-jasmine - overriden to point to the jasmine source
-source - empty
-matchers - empty
-specs - the jasmine specs

And for a rails app would be:
jasmine - points to the gem or wherever the jasmine lib is
source - public/javascripts, recursive load
matchers - spec/javascript/matchers, recursive load
specs - spec/javascript/spec, recursive load

And for a WebOs App:
jasmine - points to the vendor/jasmine or into the gem itself
source - app/**/*.js, or might be overriden to read sources.json
matchers - spec/javascript/matchers
specs - spec/javascript/spec

From the development that I've done, I see this as covering most of the
scenarios that I can think of.

Sorry for all of the messages, I'm trying to keep different questions in
separate threads.

Please let me know your thoughts

-Mike

Reply all
Reply to author
Forward
0 new messages