chai

I am setting up my tests for the results to a REST endpoint that returns me an array of Mongo database objects. [{_id: 5, title: 'Blah', owner: 'Ted', description: 'something'...}, {_id: 70, title: 'GGG', owner: 'Ted', description: 'something'...}...] What I want my tests to verify is that in the return array it conatins the specific titles that should return. Nothing I do using Chai/ Chai-Things seems to work. Things like res.body.savedResults.should.include.something.that.equals({title: 'Blah'}) error out I'm assuming since the record object contains other keys and values besides just title.

No matter what my server actually returns, Chai always gives me this exception when I assert response.body: Uncaught AssertionError: expected {} to deeply equal 'test' Even though the actual server response is 'test', not {}: Here is my test: const chai = require('chai'); const chaiHttp = require('chai-http'); const server = require('./test-server'); const should = chai.should(); chai.use(chaiHttp); describe('GET /test', () => { it('it should give test result', (done) => { chai.request(server) .get('/test') .end((err, res) => { console.log(err); // outputs null console.log(res); // outputs

Chai as Promised documentation states as follows: Notice : either return or notify(done) must be used with promise assertions. And the examples on the site are as follows: return doSomethingAsync().should.eventually.equal("foo"); doSomethingAsync().should.eventually.equal("foo").notify(done); The thing is; I actually wrote a test using chai as promised without returning the promise. Like so: it('should resolve user', function () { $state.get(state).resolve.user(dataservice, { userId: testUser.id }).should.eventually.eq(testUser); $rootScope.$apply(); }); And it works perfectly fine. I am sure

From chai's api you've got code like this: .exist Asserts that the target is neither null nor undefined. var foo = 'hi' , bar = null , baz; expect(foo).to.exist; expect(bar).to.not.exist; expect(baz).to.not.exist; How does that exist part work? The expect function returns an object, then there's simply a property lookup on the "to" object. That's simply a property evaluation though isn't it? The only thing that would make sense to me is if the exist property is a getter method. What's the go? chai exposes an use method to access the chai export and it's utils . This method can be used by third

This question already has an answer here: Mocha / Chai expect.to.throw not catching thrown errors 6 answers Trying to test some code that throws an exception with Mocha/Chai, but having no luck, here's the simple code I'm trying to test: class window.VisualizationsManager test: -> throw(new Error 'Oh no') Here is my test: describe 'VisualizationsManager', -> it 'does not permit the construction of new instances', -> manager = new window.VisualizationsManager chai.expect(manager.test()).to.throw('Oh no') However, when I run the spec, the test fails and throws the exception. Failure/Error: Oh no