Mutation range inconsistent with mutation-testing-schema?

[Aimless321]

I have been locally running MSP using stryker-js (stryker-mutator/stryker-js#5086).
While testing I noticed that it's currently not working if i pass the a result from discover into mutationTest.

For example turning this mutant:

{
  "files": {
    "src/utils/file-utils.ts": {
      "language": "typescript",
      "source": "some code",
      "mutants": [
        {
          "id": "2",
          "location": {
            "start": {
              "line": 8,
              "column": 32
            },
            "end": {
              "line": 8,
              "column": 64
            }
          },
          "mutatorName": "ObjectLiteral",
          "replacement": "{}",
        }
      ]
    }
  }
}

Into src/utils/file-utils.ts:8:32-8:64 and passing it to mutationTest doesn't test any mutants.

Could this be caused by the mutation-testing-schema location to have an exclusive end, and the MSP an inclusive?

[jaspervdveen]

Good catch! I believe this originated from the StrykerJS mutate config option, where it is inclusive. https://stryker-mutator.io/docs/stryker-js/configuration/#mutate-string
It think we need to change MSP to align the location with the MTE location.