This week, I want to focus on one of the most important parts of the interview process; the code challenge. Whether you are working on a whiteboard...
For further actions, you may consider blocking this person and/or reporting abuse
In this case it would be better served to write tests and validate code is working the way you intended via assertions.
Yes and no.
Writing tests only really check that the entire function is working as intended. They're nice to have since it can show that you know how to test and that your code works.
The problem is:
You need a way of debugging specific lines are wrong so you know what you need to fix -- The simplest (and best) method is
console.logas Sofia suggests.Writing tests will save time in the long run. Writing them before you write the implementation is preferred.
If your code is structured properly (aka small functions/classes responsible for singular things) unit tests will tell you at exactly which point your test is failing.
While I agree in a general sense, this article is about coding during an interview -- there is no "long-run" if you only get an hour to solve the problem. If you're spending a significant amount of time writing tests, you're not spending that time answering the question.
Wonderful so helpful! Thanks