Stuck in building...

[MWallin]

When I activate the extension nothing happens except the text building... keeps rolling over and over.

The npm script that is refered in setting works manually. When I look at output for the extension there is none.

Any help would be super nice!

[prashaantt]

That's interesting, can you show me what the script looks like?

[MWallin]

Sure thing!

"test": "mocha **/*.test.js"

I am totally new to testing so might it be something wrong with my tests? I am following a tuturial wich uses mocha and expect.

[prashaantt]

That looks pretty standard. Can you try removing some tests to prove that at least the thing works for one test?

The best guess I can make is that there's probably an infinite loop in some test that's not letting the process to exit.

[MWallin]

No luck I'm afraid.

This is the file I'm writing tests for

"use strict"

// *****************************************************************************
// *****************************************************************************
// Functions here

function add ( a, b ) {

  return a + b

}

function square ( a ) {

  return a * a

}



// *****************************************************************************
// *****************************************************************************
// Exports

module.exports = {

  add,
  square

}

And these are the tests I'm trying to write...

"use strict"

// *****************************************************************************
// *****************************************************************************
// Requires

const expect = require( "expect" )



// *****************************************************************************
// *****************************************************************************
// File to be tested

const utils = require( "./utils" )



// *****************************************************************************
// *****************************************************************************
// Tests

// Add function
it( "Should add two numbers", () => {

  const result = utils.add( 33, 11 )

  expect( result ).toBeA( "number" ).toBe( 44 )

})


// Square function
it( "Should square 1 number", () => {

  const result = utils.square( 6 )

  expect( result ).toBeA( "number" ).toBe( 36 )

})

Could I have set some configuration wrong? These are my settings on top of the default...

  //NodeTDD
  "nodeTdd.reporter": null,
  "nodeTdd.buildOnCreate": true,
  "nodeTdd.verbose": true,
  "nodeTdd.glob": "**/*.test.js",
  "nodeTdd.buildOnActivation": true

[prashaantt]

"nodeTdd.glob": "**/*.test.js" — you'll want to watch changes to source files too, not just the tests.

"nodeTdd.buildOnCreate": true — it doesn't look like it applies in this case but if your tests have any side effect of creating files that match the glob, they will get watched too, perhaps leading to an infinite build loop.

I don't see any other issues and your code works for me as expected. What OS are you on? Are you able to stop the build process? If not, try killing it from the terminal to confirm if it's not a bad process from the past that's just refusing to die.

[prashaantt]

I don't know your OS but I just released a new version that may potentially fix an issue on Windows as a side-effect.

[MWallin]

I'm on Windows 10 Pro and the updated version didn't exactly fix the issue, it did however bring some error messages.

I did a reboot to make sure no bad processes were running. And now when I'm tryig to stop the build process I get:

Running the contributed command:'nodeTdd.stopBuild' failed.

And then this when I try do deactivate.

Running the contributed command:'nodeTdd.deactivate' failed.

No other output however and no error when starting build.

Is there anything else I might do to help resolve this?

[prashaantt]

Whoa that's a bug — this has got to do with the differences between how Windows and POSIX systems handle processes. I just tried a fix, would you mind testing this vsix out for me? Here are the instructions on how to do it.

[MWallin]

Sorry to be that guy, but one step forward, one step backwards...

Succesfull installation and no error messages this time around. However, the original problem with building not completing is still there. And there is no way for me to stop the build process either, and again no output at all.

Are there any logging on my machine that might help you or anything else I might do?

I've waited for the build to complete now for a couple of minutes, should that be enough or am I impatient?

[prashaantt]

Do you mind pushing your project somewhere on GitHub so we can rule out any config issues? The npm-debug.log is generated only for test failures for non-standard script names (i.e. other than test) so we have nothing else to go by.

The build for 2-odd tests should finish in milliseconds.

[prashaantt]

By the way, even if the build doesn't stop you should be able to still see some text output from the tests if you open the output view (View > Output) and select the TDD Extension from the dropdown.

[MWallin]

I had some extra files like eslint config and stuff like that originally but stripped them out, without change however. Here is the current project: https://github.com/MWallin/Test_basics

Testing works fine from the console.

There is no output at all from TDD, see printscreen. No change if I deactivate and activate.

[prashaantt]

It would have been cool if you pushed your entire workspace as it is, including the .vscode folder where you are possibly overriding the default nodeTdd settings and any other js files that may be also present. I'm a little curious also to see how you're using the other test script with nodemon in it, if at all — nodemon is a long-running process and will not work right with this extension.

But as things stand, your project works perfectly on my Mac. :/

[MWallin]

Sorry for that, thought the basic example would be easier to debug. Here is the complete workspace: https://github.com/MWallin/Test_basics2

Lots of files in there thats not really necessary, I use the same basic scaffold for every new project, perhaps a bad practice, but easier to copy the config than redo from scratch each time...

The other testscript is a trick from the course I'm taking. Basically it does what you extension does but in a separate console window, when it detects a change in any file it reruns the npm test script. That way works but I thought it a bit clumpsy and found this extension.

I don't have nodemon running while trying you extension so that should'nt be the source of the problem.

If you can't figure it out now I thank you for the effort so far! Really nice of you trying to help me!

[prashaantt]

Nope, still can't figure out a thing. I'm going to leave a note about potential issues on Windows with this extension and hope you or someone else can debug it for us :) Thanks.