MACHIN

6/node_modules/jasmine-node/spec-requirejs-coffee/RequireCsSpec.coffee

@@ -0,0 +1,5 @@
+require [ "cs!requirecs.sut" ], (sut) ->
+  describe "RequireJs basic tests with spec and sut in CoffeeScript", ->
+    it "should load coffeescript sut", ->
+      expect(sut.name).toBe "CoffeeScript To Test"
+      expect(sut.method(2)).toBe 4

6/node_modules/jasmine-node/spec-requirejs-coffee/RequireJsSpec.coffee

@@ -0,0 +1,5 @@
+require [ "requirecs.sut" ], (sut) ->
+  describe "RequireJs basic tests with spec in CoffeeScript", ->
+    it "should load javascript sut", ->
+      expect(sut.name).toBe "CoffeeScript To Test"
+      expect(sut.method(2)).toBe 4

6/node_modules/jasmine-node/spec-requirejs-coffee/requirecs.sut.coffee

@@ -0,0 +1,3 @@
+define ->
+    name: 'CoffeeScript To Test'
+    method: (input) -> 2 * input

6/node_modules/jasmine-node/spec-requirejs-coffee/requirejs-setup.js

@@ -0,0 +1,13 @@
+/** Custom RequireJS setup file to test user-specified setup files */
+
+/* We want to minimize behavior changes between this test setup file and the
+ * default setup file to avoid breaking tests which rely on any (current or
+ * future) default behavior.  So we:
+ * - Run the normal setup file
+ * - Avoid introducing additional global variables
+ * - Avoid maintaining two copies of the setup file
+ */
+eval(require('fs').readFileSync(baseUrl + '../lib/jasmine-node/requirejs-wrapper-template.js', 'utf8'));
+
+// This is our indicator that this custom setup script has run
+var setupHasRun = true;