Instructions and Lab Tests

[FreeBreadsticks]

I just wanted to make a couple notes after completing this test: 1.) Since you are given so many functions I feel a small description of what each do would be invaluable to solving the problems and debugging. It's difficult to know how to start when you aren't even sure what anything is supposed to do. Even a small gif of what the desired outcome should be can really help visualize what it's supposed to do. Giving us the ability to focus on understanding these new concepts.

2.)The instructions in the ReadMe should be reorganized. The makeDesert function should be the first thing that people work on so you can actually see what the updateStatus function is doing and what it's being passed. The rest of the tests won't pass and they don't give useful information unless makeDesert is working. Also you can't console.log anything until makeDesert is working.

3.) I had the actual program working and running in the browser. Mocha.run listed everything passing and yet the tests in the terminal still were not passing. The final solution formakeDesert is what the issue was here. It is an extremely particular and specific solution, which is fine if that's the way you want the final solution to be but please drop a hint or make a note. So instead of trying to understand why your code works but the tests don't pass you already know what path you need to take.

4.) I had total about 5 different tech coaches working on this with me. Many of the issues did not come from my lack of comprehension of this, bind, call, or apply. It came from difficulty debugging this particular lab coupled with vague instructions. I really feel it derails students from what the focus should be.

[gj]

Thanks for the feedback @FreeBreadsticks ! This lab's a known tricky one, and it's high on our to-fix list.