DEV Community


Discussion on: 10 More Mistakes you probably also made in your coding task for a new job Part 2

spettifer profile image
Steve Pettifer

If tests are specified and you have written them (some people don't and that's an instant fail), then for the love of all that is good, make sure they actually run. I have reviewed code tests in which there are failing tests and that test was instantly rejected as a result.

Also, don't write tests for the sake of it: Your tests should be usefully exercising your code, and test cases should be things such as boundaries and edge cases not just the same test run a few hundred times with slightly differing values that would never cause a different outcome.

I've seen this kind of thing in code tests submitted for mid-senior positions.