Testing loopback routes with supertest, mocha, and data models

Question

Testing loopback routes with supertest, mocha, and data models

In a recent discussion on the deprecation of loopback-testing posted on Google groups, there was a query about demonstrating testing without using loopback-testing. The solution proposed in the conversation suggested utilizing supertest instead.

After experimenting with Mocha, supertest, and models sourced from app.js, I encountered an issue. While running a test file independently yielded successful results, integrating it with another test file caused unexpected failures in the first test file. This behavior left me puzzled.

Could my approach to using models be incorrect based on the example below?

describe('/Student', function () {

    var server = require('../server/server')
    var loopback = require('loopback')
    var supertest = require('supertest')
    var request = require('supertest')(server)

    var dataSource = server.dataSource('db', {adapter: 'memory'})

    var Student = dataSource.define('Student', {
        'id': Number,
        'points': Number
    });

    beforeEach(function () {
        Student.updateOrCreate({id: 1, points: 5000});
    })


    it('Post a new student', function (done) {
        request.post('/api/Students').send({points: 5000}).expect(200, done)

    })


})

node.js mocha.js loopbackjs supertest

Answer 1

Answer №1

After receiving feedback from jakerella on the previous answer, I made changes to the code above to avoid having to redefine models from scratch in the code (thank you jakerella!)

With the following code, I am able to execute all tests from various models as a single suite using npm test with no failures.

Given my focus is only on individual orders... listening and closing were unnecessary. It appears that testing overall instances of created models would necessitate their use.

describe('/Student', function () {

    var server = require('../server/server')
    var request = require('supertest')(server)
    var expect = require('expect.js')

    var Student 

    before(function() {
        Student = server.models.Student    
    })

    beforeEach(function (done) {
        Student.upsert({id: 1, points: 5000}, function() { done() })
    })    

    it('Post a new student', function (done) {
        request.post('/api/Students').send({points: 5000}).expect(200, done)
     })
})

Answer 2

After receiving feedback from jakerella on the previous answer, I made changes to the code above to avoid having to redefine models from scratch in the code (thank you jakerella!)

With the following code, I am able to execute all tests from various models as a single suite using npm test with no failures.

Given my focus is only on individual orders... listening and closing were unnecessary. It appears that testing overall instances of created models would necessitate their use.

describe('/Student', function () {

    var server = require('../server/server')
    var request = require('supertest')(server)
    var expect = require('expect.js')

    var Student 

    before(function() {
        Student = server.models.Student    
    })

    beforeEach(function (done) {
        Student.upsert({id: 1, points: 5000}, function() { done() })
    })    

    it('Post a new student', function (done) {
        request.post('/api/Students').send({points: 5000}).expect(200, done)
     })
})

Answer 3

Answer №2

Let's address an issue in your code snippet. Initially, there was a problem with the undefined dataSource variable. Additionally, you redefined the Student in your test cases. My suggestion is to utilize the LoopBack application and models that are already defined (usually located in common/models/). For testing purposes, consider implementing a basic structure similar to the code snippet below (using mocha and chai). Pay attention to the use of beforeEach and afterEach functions to initiate and terminate the server operation.

var assert = require('chai').assert,
    superagent = require('superagent'),
    app = require('../server/server');

describe('Person model', function() {
  var server;

  beforeEach(function(done) {
    server = app.listen(done);
  });

  afterEach(function(done) {
    server.close(done);
  });

  it('should successfully login and logout from the live server', function(done) {
    superagent
      .post('http://localhost:3000/api/People/login')
      .send({ email: '<a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="2c464344426c484349024f4341">[email protected]</a>', password: 'foobar' })
      .set('Accept', 'application/json')
      .set('Content-Type', 'application/json')
      .end(function(err, loginRes) {
        if (err) { return done(err); }

          assert.equal(loginRes.status, 200);
          assert.ok(loginRes.body);
          assert.equal(loginRes.body.userId, 1);
        }
      });
  });
});

Answer 4

Let's address an issue in your code snippet. Initially, there was a problem with the undefined dataSource variable. Additionally, you redefined the Student in your test cases. My suggestion is to utilize the LoopBack application and models that are already defined (usually located in common/models/). For testing purposes, consider implementing a basic structure similar to the code snippet below (using mocha and chai). Pay attention to the use of beforeEach and afterEach functions to initiate and terminate the server operation.

var assert = require('chai').assert,
    superagent = require('superagent'),
    app = require('../server/server');

describe('Person model', function() {
  var server;

  beforeEach(function(done) {
    server = app.listen(done);
  });

  afterEach(function(done) {
    server.close(done);
  });

  it('should successfully login and logout from the live server', function(done) {
    superagent
      .post('http://localhost:3000/api/People/login')
      .send({ email: '<a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="2c464344426c484349024f4341">[email protected]</a>', password: 'foobar' })
      .set('Accept', 'application/json')
      .set('Content-Type', 'application/json')
      .end(function(err, loginRes) {
        if (err) { return done(err); }

          assert.equal(loginRes.status, 200);
          assert.ok(loginRes.body);
          assert.equal(loginRes.body.userId, 1);
        }
      });
  });
});

Testing loopback routes with supertest, mocha, and data models

Answer №1

Answer №2

Similar questions

Tips for adding multiple entries to a TransactionWould you like to know

Issues with calculating SUM in MySQL within a Node.js Express application using EJS template

Tips for extracting dynamically loaded content from a website using Node.js and Selenium?

Express tutorial: Implementing view engine for routing

Installing and running Node.js within a tomcat server

dealing with the same express routes

What is the method to display a value in an input field using ExpressJS?

What is the method to extract a specific portion of a file in Node.js?

Postgres Rows Reflecting Added Property Always Display as Undefined

The Express generator automatically generates Pug files in the view folder

NPM Error: Module 'balanced-match' Not Found

The contents of req.body resemble an empty {}

Errors encountered when using npm in conjunction with Java

Digital Asset Ledger Project now has Node.js integrations available

What is the best way to manage errors on my server to ensure it remains stable and never crashes?

What are the steps to install an outdated version of Node.js on a Windows computer?

Troubleshooting: How to resolve the issue of "Error [ERR_HTTP_HEADERS_SENT]: Unable to set headers after they have been sent to the client"

Serve the JS files in Express separately

Is it necessary to use next() in express routes?

Making fun of an ES6 class function