{"action":"reopened","issue":{"url":"https://api.github.com/repos/meteor-velocity/velocity/issues/263","labels_url":"https://api.github.com/repos/meteor-velocity/velocity/issues/263/labels{/name}","comments_url":"https://api.github.com/repos/meteor-velocity/velocity/issues/263/comments","events_url":"https://api.github.com/repos/meteor-velocity/velocity/issues/263/events","html_url":"https://github.com/meteor-velocity/velocity/issues/263","id":59409092,"number":263,"title":"The stack trace of tests-proxy wrapped tests don't directly show where the test fails","user":{"login":"Sanjo","id":727955,"avatar_url":"https://avatars.githubusercontent.com/u/727955?v=3","gravatar_id":"","url":"https://api.github.com/users/Sanjo","html_url":"https://github.com/Sanjo","followers_url":"https://api.github.com/users/Sanjo/followers","following_url":"https://api.github.com/users/Sanjo/following{/other_user}","gists_url":"https://api.github.com/users/Sanjo/gists{/gist_id}","starred_url":"https://api.github.com/users/Sanjo/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Sanjo/subscriptions","organizations_url":"https://api.github.com/users/Sanjo/orgs","repos_url":"https://api.github.com/users/Sanjo/repos","events_url":"https://api.github.com/users/Sanjo/events{/privacy}","received_events_url":"https://api.github.com/users/Sanjo/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":7,"created_at":"2015-03-01T17:47:33Z","updated_at":"2015-04-23T19:57:34Z","closed_at":null,"body":"#### From keyscores:\r\n\r\n@sanjo I do see a report in html-reporter. But it's not what I call a stack trace. I have no idea what script, function, or line that is causing the failure.\r\nI'll give you an example: where would you start debugging given the html-reporter result below?\r\n\r\nError: Expected 1 to equal 0.\r\nat stack (http://localhost:49399/packages/sanjo_jasmine.js?6c8e0ce3908e66d0de626b7c10139a1ad3351d76:1956:17)\r\nat buildExpectationResult (http://localhost:49399/packages/sanjo_jasmine.js?6c8e0ce3908e66d0de626b7c10139a1ad3351d76:1926:14)\r\nat Spec.Env.expectationResultFactory (http://localhost:49399/packages/sanjo_jasmine.js?6c8e0ce3908e66d0de626b7c10139a1ad3351d76:1048:18)\r\nat Spec.addExpectationResult (http://localhost:49399/packages/sanjo_jasmine.js?6c8e0ce3908e66d0de626b7c10139a1ad3351d76:808:34)\r\nat Expectation.addExpectationResult (http://localhost:49399/packages/sanjo_jasmine.js?6c8e0ce3908e66d0de626b7c10139a1ad3351d76:992:21)\r\nat Expectation.toEqual (http://localhost:49399/packages/sanjo_jasmine.js?6c8e0ce3908e66d0de626b7c10139a1ad3351d76:1880:12)\r\nat http://localhost:49399/packages/velocity_test-proxy.js?d59197a9e14569d0670d31595b1f7bc39526feed:55:41\r\n\r\n...it's just not as productive as I've come to expect from Meteor\r\n\r\n\r\n\r\n#### My answer:\r\n\r\nYeah, that is from the tests-proxy package approach that will be replaced in the next time. Then you can see the direct line where it fails for integration tests.\r\n\r\nWith the current stack trace you need to:\r\n1. Open http://localhost:49399/packages/velocity_test-proxy.js?d59197a9e14569d0670d31595b1f7bc39526feed:55:41 (the URL is from the last line of the stack trace) in the browser.\r\n2. Right click -> Show source (I assume Chrome but should work in other browser too)\r\n3. Now you see the line numbers and you can go to line 55. That's the line where the test fails."}}