{"action":"created","issue":{"url":"https://api.github.com/repos/meteor/guide/issues/92","labels_url":"https://api.github.com/repos/meteor/guide/issues/92/labels{/name}","comments_url":"https://api.github.com/repos/meteor/guide/issues/92/comments","events_url":"https://api.github.com/repos/meteor/guide/issues/92/events","html_url":"https://github.com/meteor/guide/issues/92","id":116229047,"number":92,"title":"Figure out app testing story.","user":{"login":"tmeasday","id":132554,"avatar_url":"https://avatars.githubusercontent.com/u/132554?v=3","gravatar_id":"","url":"https://api.github.com/users/tmeasday","html_url":"https://github.com/tmeasday","followers_url":"https://api.github.com/users/tmeasday/followers","following_url":"https://api.github.com/users/tmeasday/following{/other_user}","gists_url":"https://api.github.com/users/tmeasday/gists{/gist_id}","starred_url":"https://api.github.com/users/tmeasday/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tmeasday/subscriptions","organizations_url":"https://api.github.com/users/tmeasday/orgs","repos_url":"https://api.github.com/users/tmeasday/repos","events_url":"https://api.github.com/users/tmeasday/events{/privacy}","received_events_url":"https://api.github.com/users/tmeasday/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":8,"created_at":"2015-11-10T23:48:17Z","updated_at":"2015-11-18T00:35:30Z","closed_at":null,"body":"Right now, the todos app is written in the package-only style, which means we can use package tests to do unit + (to some degree) integration tests. But \r\n  a) some people don’t like that style\r\n  b) with ES2015 modules that won’t be required any more.\r\n  \r\nSo at some point (maybe not v1 of the guide) we need to answer the app testing story. Velocity (and e.g. sanjo:jasmine) has a way of running in “integration mode” (I need to investigate this more). There’s also the possibility of Meteor itself running in “test mode”) (see this PR https://github.com/meteor/meteor/pull/4353).\r\n\r\nWhat is best way forward here? Do we recommend velocity (now that it is no longer maintained)? Do we try and get that PR merged? Or something else?"},"comment":{"url":"https://api.github.com/repos/meteor/guide/issues/comments/157556706","html_url":"https://github.com/meteor/guide/issues/92#issuecomment-157556706","issue_url":"https://api.github.com/repos/meteor/guide/issues/92","id":157556706,"user":{"login":"stubailo","id":448783,"avatar_url":"https://avatars.githubusercontent.com/u/448783?v=3","gravatar_id":"","url":"https://api.github.com/users/stubailo","html_url":"https://github.com/stubailo","followers_url":"https://api.github.com/users/stubailo/followers","following_url":"https://api.github.com/users/stubailo/following{/other_user}","gists_url":"https://api.github.com/users/stubailo/gists{/gist_id}","starred_url":"https://api.github.com/users/stubailo/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/stubailo/subscriptions","organizations_url":"https://api.github.com/users/stubailo/orgs","repos_url":"https://api.github.com/users/stubailo/repos","events_url":"https://api.github.com/users/stubailo/events{/privacy}","received_events_url":"https://api.github.com/users/stubailo/received_events","type":"User","site_admin":false},"created_at":"2015-11-18T00:35:30Z","updated_at":"2015-11-18T00:35:30Z","body":"> cucumber.js on it's own is kind of complicated with the whole async testing.\r\n\r\nI personally think this isn't a good reason to spend a lot of time implementing a custom Meteor-specific testing solution. There are a ton of things we can all be spending time on to improve the framework, and a lot of complicated things we could be making less complicated. I believe we need to tackle the most important problems first.\r\n\r\nI'm pretty convinced that we _need_ to do something about integration tests, since a Meteor-specific solution is unavoidable there, but I believe that end to end tests are not something that needs to be implemented for each framework individually, especially not until we solve the more serious issues.\r\n\r\nI think it is _absolutely crucial_ to have _some_ testing solution for every part of a Meteor app. IMO we should focus on these before trying to unite all of the different kinds of testing under one roof."}}