mercredi 19 juillet 2017

Why does my Ember component integration test pass when I run it in isolation, but fail when I run the full suite?

I have a simple, bare-bones integration test for a component which depends on an i18n service (which the test injects). The component itself is a simple select dropdown from ember-select-list, with a default value of Select Language. Here's the test:

import { moduleForComponent, test } from 'ember-qunit';
import hbs from 'htmlbars-inline-precompile';

moduleForComponent('language-select', 'Integration | Component | language select', {
  integration: true,
  beforeEach() {
    this.inject.service('i18n');
  }
});

test('it renders', function(assert) {
  this.render(hbs``);

  assert.equal(this.$().text().trim().includes('Select Language'), true);
});

When I attempt to just run this one test file (i.e. ember test -f "language-select"), the output I see indicates that only linting tests were performed:

[ hospitalrun-frontend ] $ ember test -f "language-select"
WARNING: Node v7.5.0 is not tested against Ember CLI on your platform. We recommend that you use the most-recent "Active LTS" version of Node.js.
cleaning up...
Built project successfully. Stored in "/Users/richie.thomas/Desktop/Workspace/OpenSource/hospitalrun-frontend/tmp/core_object-tests_dist-5MT1adu7.tmp".
ok 1 PhantomJS 2.1 - ESLint - acceptance/language-select-test.js: should pass ESLint
ok 2 PhantomJS 2.1 - ESLint - components/language-select.js: should pass ESLint
ok 3 PhantomJS 2.1 - TemplateLint - hospitalrun/templates/components/language-select.hbs: should pass TemplateLint
ok 4 PhantomJS 2.1 - ESLint - integration/components/language-select-test.js: should pass ESLint

1..4
# tests 4
# pass  4
# skip  0
# fail  0

# ok

However when I run a plain ember test, I see that this test fails because I am apparently injecting the i18n service incorrectly:

not ok 488 PhantomJS 2.1 - Integration | Component | language select: it renders
---
    actual: >
        null
    expected: >
        null
    stack: >
        http://localhost:7357/assets/hospitalrun.js:4090:18
        get@http://localhost:7357/assets/vendor.js:35757:32
        get@http://localhost:7357/assets/vendor.js:40664:22
        compute@http://localhost:7357/assets/vendor.js:33758:29
        value@http://localhost:7357/assets/vendor.js:33625:52
        value@http://localhost:7357/assets/vendor.js:65639:37
        value@http://localhost:7357/assets/vendor.js:33512:34
        create@http://localhost:7357/assets/vendor.js:31495:53
        evaluate@http://localhost:7357/assets/vendor.js:66320:43
        execute@http://localhost:7357/assets/vendor.js:72898:36
        render@http://localhost:7357/assets/vendor.js:72472:30
        render@http://localhost:7357/assets/vendor.js:30793:52
        runInTransaction@http://localhost:7357/assets/vendor.js:41756:28
        _renderRoots@http://localhost:7357/assets/vendor.js:31058:64
        _renderRootsTransaction@http://localhost:7357/assets/vendor.js:31096:26
        _renderRoot@http://localhost:7357/assets/vendor.js:31017:35
        _appendDefinition@http://localhost:7357/assets/vendor.js:30930:23
        appendOutletView@http://localhost:7357/assets/vendor.js:30913:29
        invoke@http://localhost:7357/assets/vendor.js:19795:19
        flush@http://localhost:7357/assets/vendor.js:19865:15
        flush@http://localhost:7357/assets/vendor.js:19989:20
        end@http://localhost:7357/assets/vendor.js:20059:28
        run@http://localhost:7357/assets/vendor.js:20182:19
        run@http://localhost:7357/assets/vendor.js:40972:32
        render@http://localhost:7357/assets/test-support.js:20665:30
        http://localhost:7357/assets/tests.js:15398:16
        runTest@http://localhost:7357/assets/test-support.js:3859:34
        run@http://localhost:7357/assets/test-support.js:3845:13
        http://localhost:7357/assets/test-support.js:4037:15
        advance@http://localhost:7357/assets/test-support.js:3522:26
        begin@http://localhost:7357/assets/test-support.js:5213:27
        http://localhost:7357/assets/test-support.js:4407:11
    message: >
        Died on test #1 http://localhost:7357/assets/tests.js:15392:24
        exports@http://localhost:7357/assets/vendor.js:123:37
        requireModule@http://localhost:7357/assets/vendor.js:38:25
        require@http://localhost:7357/assets/test-support.js:19547:14
        loadModules@http://localhost:7357/assets/test-support.js:19539:21
        load@http://localhost:7357/assets/test-support.js:19569:33
        http://localhost:7357/assets/test-support.js:7584:22: undefined is not an object (evaluating 'i18n.get')
    Log: |
...

I don't see anything in the documentation here about the filter flag affecting the type of tests that are run (i.e. lint vs non-lint tests).

I'm happy to post a separate question about how to properly inject the i18n service, but my question here is:

Why does adding the filter flag result in only filtering tests being run?




Aucun commentaire:

Enregistrer un commentaire