Geek Answers Handbook

Ember CLI with http-mock and challenger how to manage dummy data

I am new to Javascript in general, especially EmberJS and Ember CLI. I am trying to figure out what is the best practice for managing breadboard data as part of an Ember CLI project. I'm on 0.1.14 EmberCLI right now.

According to the Ember CLI documentation, http-mock is the preferred way to provide mock data for Ember Data models. So I use the generated http-mock and added some test data to it.

  var testData = [
  ...

  ];

  module.exports = function(app) {
    var express = require('express');
    var todosRouter = express.Router();

    todosRouter.get('/', function(req, res) {
      res.send({
        "todos": testData
      });
    });

Then I found out that http-mock did not work during integration, so I added Pretende.

  import Ember from 'ember';
  import { test } from 'ember-qunit';
  import Pretender from 'pretender';
  import startApp from '../helpers/start-app';

  var App;
  var server;

  var testData = [
    ...
    ];

  module('An Integration test', {
    setup: function() {
      App = startApp();
      server = new Pretender(function(){
        this.get('/api/todos', function(request){
           return [ 200, {"Content-Type": "application/json"},
                    JSON.stringify({'todos': testData) ];
        });
      });
    },
    teardown: function() {
      ...
    }
  });


  test('3 items loaded at startup', function() {
  ...
  });

HTTP-, , , . , ES6, http-mock CommonJS, , .

ES6,

var mockData = [
...
];


export default {
  all: mockData
};

, http-mock "". CommonJS module.export, .

:

  • , Broccoli "" ES6 CommonJS, http-mock, , . , ?
  • http-mock, Pretender ? ?

, , .

+4
1

, , Ember CLI, ember-cli-mirage, , . , , , , , .

+1

More articles:


All Articles