Unit testing methods and computed properties follows previous patterns shown in Unit Testing Basics because Ember.Route extends Ember.Object.

单元测试方案和计算属性与之前单元测试基础中说明的相同，因为Ember.Route集成自Ember.Object。

Testing routes can be done both via integration or unit tests. Integration tests will likely provide better coverage for routes because routes are typically used to perform transitions and load data, both of which are tested more easily in full context rather than isolation.

路由测试可以通过集成测试或者单元测试来进行。集成测试对路由的测试具有更好地覆盖性，因为路由通常用来执行过渡和数据加载，这些测试在完整上下文中更加容易测试，而独立上下文则没有那么容易。

That being said, sometimes it is important to unit test your routes. For example, let’s say we’d like to have an alert that can be triggered from anywhere within our application. The alert function displayAlert should be put into the ApplicationRoute because all actions and events bubble up to it from sub-routes, controllers and views.

不过有时候路由的单元测试也是非常重要的。例如，希望应用可以在任意地方都能触发一个警告。警告函数displayAlert应该被定义在ApplicationRoute中，因为所有操作或者事件都会从子路由、控制器和视图冒泡到该路由。

  1. App.ApplicationRoute = Em.Route.extend({
  2.   actions: {
  3.     displayAlert: function(text) {
  4.       this._displayAlert(text);
  5.     }
  6.   },
  8.   _displayAlert: function(text) {
  9.     alert(text);
  10.   }
  11. });

This is made possible by using moduleFor.

这使得使用moduleFor成为了可能。

In this route we’ve separated our concerns: The action displayAlert contains the code that is called when the action is received, and the private function _displayAlert performs the work. While not necessarily obvious here because of the small size of the functions, separating code into smaller chunks (or “concerns”), allows it to be more readily isolated for testing, which in turn allows you to catch bugs more easily.

在这个路由中，首先分离关注点：操作displayAlert包含了在收到操作时将调用的代码，而私有方法_displayAlert执行操作。当然可能这里代码这么简单，没有必要这么设计，但是将关注点进行分离，可以使得对于测试来说具有更好地可读性，这也有利于发现漏洞。

Here is an example of how to unit test this route:

下面是如何对路由进行测试的示例：

  2. moduleFor('route:application', 'Unit: route/application', {
  3.   setup: function() {
  4.     originalAlert = window.alert; // store a reference to the window.alert
  5.   },
  6.   teardown: function() {
  7.     window.alert = originalAlert; // restore original functions
  8.   }
  9. });
  11. test('Alert is called on displayAlert', function() {
  12.   expect(1);
  14.   // with moduleFor, the subject returns an instance of the route
  15.   var route = this.subject(),
  16.       expectedText = 'foo';
  18.   // stub window.alert to perform a qunit test
  19.   window.alert = function(text) {
  20.     equal(text, expectedText, 'expected ' + text + ' to be ' + expectedText);
  21.   }
  23.   // call the _displayAlert function which triggers the qunit test above
  24.   route._displayAlert(expectedText);
  25. });

Live Example

在线示例

Custom Test Helpers

自定义测试助手