Create functional tests for catalog bookmarking

[bajiat]

Ensure the bookmark toggle button works as expected on the API catalog by writing a functional test suite. (Includes defining the expectation.)

Definition of done

Choose

We have chosen to work with Mocha.js and use the Velocity test runner. Velocity is the official tes runner for Meteor.js.

• [x] Research integration (end-to-end) testing frameworks, e.g.
  • [x] Casper.js / Slimer.js
  • [x] Nightwatch.js
  • [x] Pioneer.js
• [x] Choose an integration testing framework based on research, bonus points for the following criteria:
  • [x] JavaScript based
  • [x] Meteor integration

    Document

• [ ] Create plain text description of expected behavior in project documentation folder. Including:
  • [ ] Add bookmark
  • [ ] Remove bookmark
  • [ ] View bookmarks

    Implement

• [ ] Write the test cases to guide an automated browser through the expected functionality. Test cases should include:
  • [ ] Add bookmark
  • [ ] Remove bookmark
  • [ ] View bookmarks
• [ ] Add the test cases to /tests/client/integration.

  Test

• [ ] Ensure that the test cases are successful, i.e. they pass.

[bajiat]

@frenchbread Would you be able to take this task in addition to #327 and #76? If yes, could you estimate the size?

[mauriciovieira]

I suggest we take a look at Velocity, the official meteor package for testing.

[bajiat]

Moving this back to backlog, because there is a new testing plan proposed to Apinf. This task either to be re-used for the new plan or closed if new testing issues will be created.

[brylie]

@mauriciovieira it makes sense to use Velocity as our testing framework. Also, we chose Mocha.js in a previous task for writing our tests. Mocha.js can be used with Velocity.

[Nazarah]

closing this for the time being.