Databases
StackOverflow2013
Postsdbo
POgrunt watch kicks off tests but no tests are run
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POgrunt watch kicks off tests but no tests are run
    primarykey
    data
    text
    <p>I've got a grunt task that runs correctly the first time (runs stylus, transpiles the coffee, runs the tests). But when the <code>watch</code> task kicks off it runs the <code>mochaTest:all</code> task but no tests get run. </p> <p>Config: </p> <pre><code>grunt.initConfig watch: coffee: files: ['app/assets/src/coffee/**/*.coffee', 'app/assets/src/coffee/*.coffee', 'app/webserver.coffee'] tasks: ['coffee:dev', 'replace', 'mochaTest:all'] options: nospawn: true test: files: ['test/calc/*.coffee', 'test/*.coffee'] tasks: ['test'] options: nospawn: true stylus: files: 'app/assets/src/styl/**/*.styl' tasks: 'stylus:dev' mochaTest: all: src: [ 'test/calc/*.coffee', 'test/*.coffee'] options: reporter: 'nyan' timeout: 1000 ... grunt.registerTask "test", [ "mochaTest"] </code></pre> <p>Running the test directly: </p> <pre><code>$ grunt 'mochaTest' Running "mochaTest:all" (mochaTest) task ... 264 passing (10 seconds) </code></pre> <p>Ok, so that's working. But when the watch is triggered, no tests are run: </p> <pre><code>Waiting... OK &gt;&gt; File "test/dataLayer-test.coffee" changed. Running "mochaTest:all" (mochaTest) task 0 passing (1 ms) </code></pre> <p>No tests got run. I must have something configured wrong. What's the problem here? Is it a bug? </p> <p>Versions: </p> <pre><code>$ npm list | grep grunt ├─┬ grunt@0.4.1 ├── grunt-contrib-coffee@0.7.0 ├── grunt-contrib-stylus@0.5.0 ├─┬ grunt-contrib-watch@0.5.1 ├─┬ grunt-mocha-test@0.6.3 ├── grunt-text-replace@0.3.2 </code></pre> <p>Edit: per Gilad's suggestion, no difference though: </p> <pre><code>grunt watch --verbose --debug ... Running "mochaTest:all" (mochaTest) task [D] Task source: /home/dev/projects/alpha/node_modules/grunt-mocha-test/tasks/mocha.js Verifying property mochaTest.all exists in config...OK Files: test/calc/calc-test.coffee, ... 264 passing (9 seconds) 5 pending &gt;&gt; File "test/ui-formulaEditor-test.coffee" changed. Running "mochaTest:all" (mochaTest) task [D] Task source: /home/dev/projects/alpha/node_modules/grunt-mocha-test/tasks/mocha.js Verifying property mochaTest.all exists in config...OK Files: test/calc/calc-test.coffee, ... 0 passing (2 ms) ... </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USjcollum
    1. USjcollum
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COrun `grunt watch --verbose --debug`. It seems to me like mochaTest running from watch isn't getting the right parameters. Also - nospawn is an old parameter. use spawn.
      singulars
      1. POgrunt watch kicks off tests but no tests are run
      1. USGilad Peleg
    2. CO@GiladPeleg no change, updated question
      singulars
      1. POgrunt watch kicks off tests but no tests are run
      1. USjcollum
    3. COspawn: false or nospawn: true means the watch will run tasks within the same context. I recommend the default, spawn your tasks especially with test suites.
      singulars
      1. POgrunt watch kicks off tests but no tests are run
      1. USKyle Robinson Young
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload