'Branch not covered'

[willin]

is it a bug or other?

[guyellis]

Are you using Babel? I've seen this show up when I have a combo of Babel transpilation and Istanbul.

[willin]

yes.

{
    "babel-plugin-transform-runtime": "^6.6.0",
    "babel-preset-es2015": "^6.6.0",
    "babel-preset-es2015-loose": "^7.0.0",
    "babel-preset-stage-1": "^6.5.0",
    "babel-register": "^6.7.2",
    "babel-runtime": "^6.6.1",
}

[guyellis]

One of the current alpha branches might address that: https://github.com/gotwarlost/istanbul/releases

[JoelOtter]

I'm still seeing this issue on v0.4.3, which I believe is later than the mentioned alpha releases.

[otbe]

I wonder if this is also the root of some uncovered branches in my current project.

Im using typescript & babel and all other branches are fine. Obviously it was covered (green "1x" on the left side).

It is the same problem?

Tried already the latest apha, but issue still exists.

[morficus]

I have a similar issue (some branches now showing as covered) and I found it curious that everyone here is using typeof (which I was as well).

After reading this I decided use instanceof instead and bam! all branches covered.

[smonusbonus]

Hmm yeah same issue here with typeof.

[AlexMiroshnikov]

A very basic and tiny sample of the same kind of misbehavior:

[tpizza]

Yet another example of the misbehavior:

[Biglr]

I have a similar problem, only that it is with commas as well:

I've got a lot of those kinds of "branch not covered" warnings all over my applications...

[AshCoolman]

typeof also giving me problems

Update Changing to 1.0.0-alpha.2 works for me

[QuentinRoy]

I believe this is because babel replaces typeof with a custom helper that branches in function of the environment (hence only one branch is executed per environment).

[savcni01]

@QuentinRoy - yes, I think you are right: Babel Transformation Example

So for @AshCoolman example for cover all branches you need to provide 2 variants of element:

element = undefined
//and
element = 'some sting'
// then
const typeOfElement = typeof(element)

will run both branches hidden at babel replacement of typeof

[QuentinRoy]

For your information, with ava, I made it work with the following config:

.babelrc

{
  "presets": ["env"],
  "env": {
    "test": {
      "plugins": [ "istanbul" ],
      "presets": [["env", { "targets": { "node": "current" } }]]
    }
  }
}

package.json

{
  // [...]
  "ava": {
    "require": [
      "babel-register"
    ]
  },
  "nyc": {
    "sourceMap": false,
    "instrument": false
  }
}

[cope]

I think this is the same problem:

I'm testing with null as well as with both valid and invalid string and object definition parameter.

Same happens in this case:

I get a 100% Branches only if I use definition = definition || '';, which is not making me happy. I like the ES6 default parameters :(

[adamreisnz]

Finding it impossible to fix this issue.

Always resulting tin the following error:

Even if using the suggested fix:

I'm running tests and passing both strings, undefined, and valid objects to the glob param.

Even when I use //istanbul ignore if it still reports it.