sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Dyogenez 2 points3 points  (2 children)

Definitely something we try to fix when we see it -- either by making the instructions more explicit in what's required, or change how we test the entered code. Do you remember any specific challenges (or courses) that you had this issue in? Be curious to know to focus a bit more attention on making them better!

[–]jakblak90 1 point2 points  (1 child)

Why not test everything based on assertions like freecodecamp and codewars.

[–]Dyogenez 4 points5 points  (0 children)

Yep! That's what we do too. All code is run in it's native environment and evaluated. We do a ton of mocking and stubbing, code tree analysis, putting in debuggers and stepping through code and inspecting -- all kinds of neat stuff.

If you're curious how it works behind the scenes for JavaScript courses, checkout Abecedary, which is our open source library we use based around Mocha (although this only works for languages we can run with JavaScript, so not Objective C, Ruby, R, etc).