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

test message not descriptive #25

Open
abdhalees opened this issue Nov 18, 2017 · 2 comments
Open

test message not descriptive #25

abdhalees opened this issue Nov 18, 2017 · 2 comments

Comments

@abdhalees
Copy link

As I said in #24 you specify what function your testing in the tape function.
In equal/deepEqual functions you specify what this test is testing in your function, so when it fails you will know what you were testing and don't have to look at the test and understand what you were testing.

t.deepEqual(logic.addTodo([],{description:"screen"}),[{id:1, description:"screen", done:false}], "test1: actual should be equal to expected");

@sultanassi95
Copy link
Collaborator

can u speak english :D

@abdhalees
Copy link
Author

@sultanassi95 In the test message you are saying test1: actual should be equal to expected

  1. I don't know what is test1.
  2. every test the actual should equal the expected. this message should be a description to the test.
    e.g. for this test you could write: newTodo must be added to the array
    so when it fails you will know what exactly is failing without the need to read the test file.

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

No branches or pull requests

2 participants