./config/environment.js example about ember-app-kit HOT 7 CLOSED

ADDED THIS TO GIVE SUPPORT FOR A TEST ENVIRONMENT:

assembleTest: {
      files: [{
        expand: true,
        cwd: 'tests',
        src: ['test-helper.js', 'test-loader.js'],
        dest: 'tmp/result/tests/'
      }, {
        'expand: true,'
        'cwd: 'public','
        'src: ['**'],'
        'dest: 'tmp/result/''
      }, {
        'src: ['vendor/**/*.js', 'vendor/**/*.css'],'
        'dest: 'tmp/result/''
      }, {
        'src: ['config/environment.js', 'config/environments/test.js'],'
        'dest: 'tmp/result/''
      }
      ]
  },

Added this to grunt file:

grunt.registerTask('server:testEnv', "Build and preview a minified & production-ready version of your app.", [
                       'clean:debug',
                       'build:debug',
                       'copy:assembleTest',
                       'expressServer:dist:keepalive',
                       'watch'
]);

This worked for me locally.

Thoughts on this?

from ember-app-kit.

@agentVargas2012R i don't understand the need for assembleTest.
we already do that here

from ember-app-kit.

Hi fsmanuel,

I guess the grunt task name kinda sucks and is a bit of a misnomer.

Your post looks like it refers to including testing frameworks like testem, qunit and the harness which loads these into the ecosystem.

What my question refers to actually is more for targeted environments such as corporate enterprises where there exists more than just a Dev and prod environment. It is very common to have Dev, test , demo preprod and prod targeted domains. Each of these environments can and should have different end points typically because the desparate back end systems refer to various environments which may differ anywhere from underlying data models and versions to availability of services which all may have there own variances.

So what I did here was basically attempt to include a test.js environment config which encapsulates the properties targeted for that environment while externalizing these things to its own deployment artifact.

from ember-app-kit.

@agentVargas2012R i get that but there is a test.js environment that gets loaded in tests.

from ember-app-kit.

Great. I didn't see a way to create the artifact without running tests.

Is that possible?

from ember-app-kit.

@agentVargas2012R good point. i'm not sure how ember-cli handles that case. i don't want to introduce that feature here if it's not in ember-cli to stay upgrade compatible. if ember-cli has that feature we can make your code a PR and think about the task name.

@stefanpenner are multi environments supported in ember-cli? especially the possibility to build and run them in the server (not only for the test runner)?

from ember-app-kit.

Any update on this from you guys?

I am good on my side of things and can close this out if we do not want to pursue this route :)

Just let me know!

from ember-app-kit.