Code Monkey home page Code Monkey logo

Comments (4)

marcioj avatar marcioj commented on May 22, 2024

Hi @samselikoff, sorry for that.

I got lastest version of the project, and could not reproduce this problem. Can you point out the specific test that fails when including not in the assertion?

Also, I must say that running ember test will not run the *-test-node.js tests. This is why I added mocha tests/**/*-test-node.js in the test script, so you need to run npm test to consider all the tests.

This is also how travis is configured.

from ember-cli-mirage.

samselikoff avatar samselikoff commented on May 22, 2024

ahhh, ok that could have been it. I had forgotten to change pretender to mirage here:

2c51833

I wonder if it would have failed if I ran npm test? Did we need mocha because we can't use qunit in node?

from ember-cli-mirage.

marcioj avatar marcioj commented on May 22, 2024

I wonder if it would have failed if I ran npm test?

Probably not, because the tests in addon-tree-test-node.js just verify whether the excludePretenderDir method is called or not. This is a sample. So, before your commit excludePretenderDir was still being called, but with the old name pretender and the tests probably would pass. Some alternatives that comes to my mind is:

  • Create a method called miracleRootPath which would return <module-prefix>/mirage/, and unit test it, so we prevent these issues in the future.

or

  • Do a ember build in a tmp dir and check if it contents contain references of miracle code. Probably a regex checking for amd defines containing the miracle word. Not sure if this is the better way though.

Did we need mocha because we can't use qunit in node?

I just used mocha as a personal preference, but I agree that is strange to have two tests frameworks in the project. A quick search showed to me this qunit node runner. Should we give it a try? If so I can update the existing tests.

from ember-cli-mirage.

samselikoff avatar samselikoff commented on May 22, 2024

I see, thanks for explaining :) Let's not worry about it, eventually I want to extract the core pieces of this library into a separate Mirage project that has nothing to do with Ember. Then we could have a nicer setup and perhaps use mocha for all the tests.

Seems like for now, the ember build step + checking the tmp dir would be really nice.

from ember-cli-mirage.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.