Seattle EmberJS Meetup April: Ember-Testing and Integration Testing in Ember
Table of Contents
- Seattle EmberJS Meetup April
- Ember-Testing
- Ember Project from Scratch
- Ember Rails Starter Kit
- Using example using git clone
- Abstracting out the routes with support for hbs routes
- Create the store
- Create the fixture
- Set the context of the template
- Provide some of the base controllers and feeds.
- Add in a new view of a particular feed
- Provide a model that defines the underlying object
- Also supports belongs to relationship
- Use setupController for initialization
- Outcome
Seattle EmberJS Meetup April
Ember-Testing
Examples
- https://github.com/jnicklas/capybara
- Selenium
Most issues come from async
This is stil something that is only provided based on polling.
// Define end for async
Integration tests in Ember
Based on QUnit
- Start with setup
- provide teardown
module('/conversations', { 'setup': function() {}, 'teardown': function() {} })
Outcome
Running inside an app assumes full stack is Ember.
Ember Project from Scratch
Ember Rails Starter Kit
This just creates an application and a minimal template.
- one template (handlebars)
- one JavaScript
Using example using git clone
This allows a fast build of all core templates rather than forcing past and testing.
Abstracting out the routes with support for hbs routes
Create the store
Create the fixture
Set the context of the template
Uses a nomenclature of feedroute: extending from Ember.Routes.
Provide some of the base controllers and feeds.
Add in a new view of a particular feed
This requires that we create a new router entry for viewing a particular feed.
A resource has a route. The path also supports the standard routing definition.
The resource would need a supporting template.
Provide a model that defines the underlying object
Also supports belongs to relationship
Use setupController for initialization
Outcome
Looks at escaping by default: {{{}}}; the amount of time spent in building new application in decomposition and the generation of new routes and linking when contrasted with the effort traditionally devoted in Spring applications is apparent. There linking and web work is usually more work than persistence and storage.