qunit

working in ember-cli testing. After all tests passed it returns extra two test with errors. Uncaught Error: Assertion Failed: calling set on destroyed object Source : '../dist/assets/vendor.js:13269' this is one unit test configuration import Ember from "ember"; import { test,moduleFor } from 'ember-qunit'; import startApp from '../helpers/start-app'; var App; module('An Integration test',{ setup:function(){ App=startApp(); }, teardown: function() { Ember.run(App, 'destroy'); } }); Huafu This is either because in the result of a promise or any other deferred code you do not check the destroy

We are trying to implement QUnit JavaScript tests for a JS-heavy web app. We are struggling to find a way to successfully test methods that involve jQuery AJAX requests. For example, we have the following constructor function (obviously this is a very simplistic example): var X = function() { this.fire = function() { $.ajax("someURL.php", { data: { userId: "james" }, dataType: "json", success: function(data) { //Do stuff } }); }; }; var myX = new X(); myX.fire(); We are trying to find a way to test the fire method, preferably with a stubbed URL instead of the real someURL.php . The only

On the server side we have Rspec/Cucumber for BDD development (ruby) vowsjs (node.js) Is there a BDD frameworks to use on web browsers (not qUnit or YUI test since these are only for TDD)? Check out jasmine describe("Jasmine", function() { it("makes testing JavaScript awesome!", function() { expect(yourCode).toBeLotsBetter(); }); }); http://pivotal.github.com/jasmine/ https://github.com/pivotal/jasmine Should_be ( sic ) very familiar to a ruby person You could also look at Yadda . Rather than being a standalone test framework like CucumberJS, it enables to use a Gherkin like syntax from other

What are the main differences between these two testing frameworks? I am a totally new to Test Driven Development and starting from the very beginning. QUnit is very easy to get started with, as you only need to include two files and a little bit of markup, then you can start writing tests. Jasmine strength, afaik is its BDD-style syntax, if that is something that you prefer (probably not a selling point for you) and tight integration into Ruby/Rails tools. In the end both get the job done. I recommend to start with QUnit. Once you're feeling comfortable, try Jasmine and check if the BDD style

Sorry if this is obvious, but is there a notOK or equivalent function in QUnit, if we want to assert that a method returns false? I can't see a way to negate OK in the documentation . I tried: !ok... but that didn't work. You could use: ok(!method_expected_to_be_false) According to the documentation : The most basic assertion in QUnit, ok() requires just one argument. If the argument evaluates to true, the assertion passes; otherwise, it fails. You can verify that a method return a false value by writing an expression which evaluates to a true value in the case the method returns false , and

Specs: Ember version: 1.13.8 node: 0.10.33 npm: 2.13.4 I have import Alias from "../../../services/alias"; .... moduleFor("controller:test", "Controller: test", { integration: true, beforeEach: function() { this.register('service:alias', Alias, {singleton: true}); this.inject.service('alias', { as: 'alias' }); this.advanceReadiness(); }, }); ... test('Alias Alias Alias ', function(assert) { var controller = this.subject(); //sample function controller.send("test"); assert.equal(true, controller.alias.get("alias"), "alias should be true"); }); (Using 'alias' as example because I'm not allow to