-
Notifications
You must be signed in to change notification settings - Fork 4
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
Introduce receptionist and staff tests #138
base: arch_01
Are you sure you want to change the base?
Conversation
namespace receptionist | ||
{ | ||
|
||
class ReceptionistMock : public iReceptionist |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think, that Mocks should reside in "tests" module, not in backend. It does not need to be included in production code in my opinion, as it is part of "testing" world.
The best option in my opinion is to create folder "Mocks" or "utils/mocks" in "tests" module
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought about it also but wasn't sure. In different projects I followed this approach, so I added it here also. Will move it to utils/mocks under the test module (will need help haha :) )
Thanks @mBialczak for Code Review. |
Thanks @mBialczak for Code Review. |
1 similar comment
Thanks @mBialczak for Code Review. |
In this pull request:
Receptionist class was introduced.
Doctor Factory was created.
Doctor Mock was created.
Receptionist Mock was created.
Staff tests were introduced with getters for Doctor and Receptionist in Staff class.