Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unit Testing #282

Open
AtlasMaxima-zz opened this issue Oct 24, 2018 · 2 comments
Open

Unit Testing #282

AtlasMaxima-zz opened this issue Oct 24, 2018 · 2 comments
Assignees
Labels
discuss Open for discussion

Comments

@AtlasMaxima-zz
Copy link
Collaborator

We should set up unit testing @tlyon3 @mmcky. What do you guys think?

Potential unit testing frameworks that we can use:

Some units we can do testing on:

  • Last updated and published dates
    We have been experiencing some inconsistency within these dates.
@AtlasMaxima-zz AtlasMaxima-zz added the discuss Open for discussion label Oct 24, 2018
@mmcky
Copy link
Collaborator

mmcky commented Dec 10, 2018

hey @atlasmaxima do you think this project would benefit greatly from unit testing? I can't think of other examples. Perhaps we should focus on Continuous Integration before investing in unit testing (for pushing branches to the development instance) and then extending to cover unit tests.

@AtlasMaxima-zz
Copy link
Collaborator Author

AtlasMaxima-zz commented Dec 29, 2018

@mmcky That sounds more like a plan.

Here are more examples on what we can test in the future:

  • Each component is doing what it is supposed to be doing.
  • Testing if each submission is uploaded correctly, has the correct extension, and is able to render.
  • Testing for scripts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discuss Open for discussion
Projects
None yet
Development

No branches or pull requests

3 participants