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.

Sign up for GitHub

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

Jump to bottom

Unit tests for recorder.py #51

Open
aecay opened this issue Aug 15, 2019 · 1 comment
Open

Unit tests for recorder.py #51

aecay opened this issue Aug 15, 2019 · 1 comment
Labels
tests issues tracking the unit (and other) test coverage in the project
Projects
Test coverage swarm

Comments

@aecay
Copy link
Collaborator

aecay commented Aug 15, 2019

No description provided.

@aecay aecay added the tests issues tracking the unit (and other) test coverage in the project label Aug 15, 2019
@aecay aecay added this to To do in Test coverage swarm via automation Aug 15, 2019
@DavAnnunz
Copy link
Collaborator

New unit tests for the recorder had been written in #67 covering the 81% of the relative file.
Writing them I notice there are 2 if statement with out an else section. Should we add them to warn the user on why the message has not been recorded?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
tests issues tracking the unit (and other) test coverage in the project
Projects
Test coverage swarm
  
To do
Milestone
No milestone
Development

No branches or pull requests
2 participants
@aecay @DavAnnunz