{"action":"closed","issue":{"url":"https://api.github.com/repos/Microsoft/nodejstools/issues/1561","repository_url":"https://api.github.com/repos/Microsoft/nodejstools","labels_url":"https://api.github.com/repos/Microsoft/nodejstools/issues/1561/labels{/name}","comments_url":"https://api.github.com/repos/Microsoft/nodejstools/issues/1561/comments","events_url":"https://api.github.com/repos/Microsoft/nodejstools/issues/1561/events","html_url":"https://github.com/Microsoft/nodejstools/issues/1561","id":226795767,"number":1561,"title":"Mocha Test id depends on the file path","user":{"login":"fforjan","id":601810,"avatar_url":"https://avatars0.githubusercontent.com/u/601810?v=4","gravatar_id":"","url":"https://api.github.com/users/fforjan","html_url":"https://github.com/fforjan","followers_url":"https://api.github.com/users/fforjan/followers","following_url":"https://api.github.com/users/fforjan/following{/other_user}","gists_url":"https://api.github.com/users/fforjan/gists{/gist_id}","starred_url":"https://api.github.com/users/fforjan/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fforjan/subscriptions","organizations_url":"https://api.github.com/users/fforjan/orgs","repos_url":"https://api.github.com/users/fforjan/repos","events_url":"https://api.github.com/users/fforjan/events{/privacy}","received_events_url":"https://api.github.com/users/fforjan/received_events","type":"User","site_admin":false},"labels":[{"id":239756351,"url":"https://api.github.com/repos/Microsoft/nodejstools/labels/test-adapter","name":"test-adapter","color":"dff0ff","default":false}],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":8,"created_at":"2017-05-06T19:02:24Z","updated_at":"2018-05-11T20:46:59Z","closed_at":"2018-05-11T20:46:59Z","author_association":"NONE","body":"When running javascript unit test via Mocha on a TFS build, TFS is not able to detect that the test was failing in a previous build and tag as failing in the current build\r\n\r\n##### Expected Behavior \r\nsame test failing in consecutive build should be detected as failing in the first build.\r\n\r\n##### Actual Behavior \r\nsame test failing in consecutive build is not detected as failed in the first build\r\n\r\n##### Steps to Reproduce\r\nMy assumption about this issue is about the test having some file path in its ID. the file path depends on the workspace location and is different between build agents:\r\nBuild A : \r\n![image](https://cloud.githubusercontent.com/assets/601810/25775121/7da1fe10-3252-11e7-8c5f-906af866697b.png)\r\n\r\nBuild A + 1\r\n![image](https://cloud.githubusercontent.com/assets/601810/25775133/017c3f16-3253-11e7-9e01-c2b3b863d30b.png)\r\n\r\nWhich seems to be related to the fully qualified name : https://github.com/Microsoft/nodejstools/blob/master/Nodejs/Product/TestAdapter/TestFrameworks/NodejsTestInfo.cs#L42\r\n\r\nOn regular C# unit tests, you can see the ID seems to not only include the file name but the class name which should be the unique ID\r\n![image](https://cloud.githubusercontent.com/assets/601810/25775160/dc9cf0ae-3253-11e7-84ae-d1e16b3bbd14.png)\r\n\r\n\r\n\r\n\r\n"}}
{"actor":{"display_login":"paulvanbrenk"}}