Conversation
nirlipo
left a comment
There was a problem hiding this comment.
Thanks for the PR!
Besides the comments in the files, I have 2 more questions:
- Should we move the test folder out of app?
- Can you group the input files into different folders?
Thanks!
server/app/unit_test/README.md
Outdated
| Ran 8 tests in 1.967s | ||
|
|
||
| OK | ||
| ``` |
There was a problem hiding this comment.
When it runs, can it give you some output messages of the tests it passed?
Why didn't we use django.tests?
* Move the unit test folder out of the app folder * Created a folder to takes all the expected output files for comparing with the output * Added failure message to indicate the errors * Added comments for the test cases Resolves #43
|
Hi @nirlipo , sorry for the late response, I was focusing on the planning-as-service project and forgot to check the messages here. I've made a few changes to the unit test branch according to your comments. For the django.test, we found the document says
From a functional point of view, using Django.test is the same as using the Python unittest module directly. So we think just using the Python unittest module would be more light and easy to use, and won't cause any potential conflict with the existing features. |
nirlipo
left a comment
There was a problem hiding this comment.
Thanks for the changes. Please update the output in the Readme and we are ready to merge!
* Added error message and exception message parts in the README.md Resolves #43
|
Please let me know how to include this on the travis pipeline! |
Added unit test feature to the project