Test Coverage

[nickmcintyre]

@JithinKS97 I'm making good progress on #17 in a separate branch and propose we work on testing in parallel. Making changes without tests is scary–the app still seems to work properly up to this point, but I'm not certain I haven't broken anything. Future development should probably begin with tests.

We could use a tool like Istanbul to track test coverage while working toward 100%. meteor-coverage seems like a good starting point.

[JithinKS97]

Great to hear!!! I have written some client side and server side test cases. (See the read me for running it). But definitely we need more test cases. May be we think of testing the app in a much more systematic and planned manner. I will work on this as soon as my exams are over which will be after 12th.

[ashneeldas2]

In terms of testing client side, including failure of components to render, I'm thinking of using mocha/chai/enzyme, and potentially sinon. Does anyone have any thoughts/suggestions on other libraries/assertion libraries that might work well?

Here's an article about the benefits of using these libraries.

[JithinKS97]

I have written some test cases for CreateLessonplan.js, you can find the file in imports/ui/pages/CreateLessonplan.test.js. There I used enzyme and chai. In server side also, I used chai. For running the test, the command is npm run full-test

[JithinKS97]

Added almost all test cases for CreateLessonplan.jsx, now planning to begin testing Request.jsx. Here are the test cases that I'm planning to write - The test cases can be found in Request.test.js.

• Editing of title and description
• Addition and deletion of slide
• Editing the title of slide
• Adding and deleting comments
• Replying to comments
• Adding simulation
• Editing the simulation
• Rendering comment form only if user is a member
• Showing edit only for owners - slides, comment, simulation