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

Improve error output message #111

Closed
emragins opened this issue Jun 16, 2016 · 1 comment
Closed

Improve error output message #111

emragins opened this issue Jun 16, 2016 · 1 comment

Comments

@emragins
Copy link

emragins commented Jun 16, 2016

TypeError: 'undefined' is not a function (evaluating '_.all(expectedArgs, function(expectedArg, i) {
          return argumentMatchesExpectation(expectedArg, actualArgs[i]);
        })')

My test runner (wallaby) gives me a stack trace, too, which is wrong. I have no idea where this is happening in my code. All I can tell is something's undefined somewhere......

PS
I'm a total novice to testdouble.js and I'm relatively new to JS testing in general. I really like the philosophy of testdouble since already it's forced me to clean up a couple lazy decisions in my code.

@searls
Copy link
Member

searls commented Jun 16, 2016

I am sorry but I don't think this is enough to go on. I think I need you to help us by providing the project or—much better still—a reproducible example. Until then I don't think we're going to have the time to try to reproduce it without more info.

@searls searls closed this as completed Jun 16, 2016
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