Adding titlePath in bridge to handle reporting of test failures

[MiguelCastillo]

This code changes resolve an issue where tests that fail report

  1 failing

Fatal error: test.titlePath is not a function

After these changes I get the expected trace.

  1 failing

  1) Fetch Test Suite
       When loading modules by name
         When fetching a single module called `like`
           then then result is an object:
     expected [ Array(1) ] to be an object
  AssertionError
  assert
  an
  chainableMethodWrapper
  
  runHandler@http://localhost:54232/node_modules/spromise/dist/spromise.min.js:1:5831
  http://localhost:54232/node_modules/spromise/dist/spromise.min.js:1:5718
  c@http://localhost:54232/node_modules/spromise/dist/spromise.min.js:1:5178
  _runTask@http://localhost:54232/node_modules/spromise/dist/spromise.min.js:1:6923
  http://localhost:54232/node_modules/spromise/dist/spromise.min.js:1:6881

This fixes #6

[BYK]

LGTM!

Do you know why this wasn't an issue earlier?

[BYK]

@tail can you rerun the tests to make sure they pass?

[Spongman]

what's the holdup? can we get this on npm already?

[rejas]

Would like to see this released too. Any help needed @BYK ?

[BYK]

@rejas you need to ping @tail or @thekashifmalik for that :)

[rejas]

Pinging @tail and @thekashifmalik asking them if they need help releasing this...

[rejas]

Hello @tail and @thekashifmalik if you read this, please provide an update of this plugin to npm. Or if you dont have time for that, consider granting the rights for that to another person. Thx in advance.

[rejas]

hi again @BYK seems like the two have not been active on github for several weeks, is there any other way to move this issue forward?

[BYK]

I have pinged then from another channel and they said they should have time next week to push this 😉

[rejas]

Any news from them?

[MiguelCastillo]

@tail @thekashifmalik - all of us here know that it is really difficult to find time for open source projects that we have volunteered to do in our spare time. I personally really appreciate that y'all have stepped up to take this on. But given the current rate of responses to publish this to npm it seems prudent (and only fair to the community) to add a few folks in here as collaborator in NPM so that we can at least publish from a fork if y'all dont have time to continue maintenance of this project. Please! ❤️

[thekashifmalik]

Hey all.

Sorry about the long time-to-response. I wanted to get perms on NPM first.

I just got said permissions on the NPM repository for this project. I'll try and make a release ASAP.(probably look into it tomorrow)

[rejas]

Thx for the headsup. Not wanting to sound too pushy but would it be possible to get this #9 in the release too? Would be really helpful to have the new reelease without the need of having to install growl...

[thekashifmalik]

It says merging is blocked but let me see if it's easy to fix.

[rejas]

Somebody with review-priviliges needs to review the PR before it can get merged. I hope you do have those :-)

[thekashifmalik]

@rejas @MiguelCastillo: version 1.0.5 is now published on NPM: https://www.npmjs.com/package/grunt-mocha.

I'll make another release once I fix my permission on Github and can merge #9.

[rejas]

Thx for publishing. Git sources are not updated yet though?

[thekashifmalik]

Correcto Mundo. I gotta fix my permissions on this project before I can push to it. So silly :)

…

On Sat, Jun 16, 2018, 3:17 PM Veeck ***@***.***> wrote: Thx for publishing. Git sources are not updated yet though? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#7 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABQvtp5MUKFwLqnbhnq7u0AWzTFcs1T-ks5t9YQWgaJpZM4RRV9O> .

[thekashifmalik]

All good now.