Cake O'clock project is given as a lesson too early in the process

I am on the old Web Developer career path and have reached the Testing category of lessons. One of the first things given is a project called Cake O’clock. It asks the student to start writing code that hasn’t been taught at all up to that point. Very confusing and frustrating.
I noticed that it is also one of the first things given in the ‘Learn JavaScript Unit Testing’ modules outside of the career path I am on.
In order to move forward, I skipped the project and went straight through the ‘Write good tests with Mocha’ and ‘Learn test-driven development with Mocha’. These are the lessons that a student should start with.
The ‘Why Test’ module should not even have a project included at all, since it teaches no Mocha coding lessons. The Project could go at the end of the last module of TDD.


Just thought I’d mention it to keep other students from getting overwhelmed with this module structure.
Great website, though. Thoroughly enjoying my journey to learn Web Development!
Thanks

I’ve noticed this as well. I ended up taking a gander at the Test Driven Development project video and it assumes that we already know chai. Not sure if this was an intentional thing for them to do.

i’ll take your advice and skip this section and go straight to “Write good test with Mocha”

Same issue with the career path Back-End Developer. This should be fixed by Codecademy!

Just ran into the same issue.

I ran into the same issue on the front-end engineer path. Absolutely agree and skipped the project for now.

Yeah… I know it gives a bit of anxiety skipping a project. But, you will want to skip right to the next lessons after it. Once you get those items done with Mocha and all of the TDD lessons, you can go back and pick up the skipped project with the necessary training to complete it without confusion.

Hey Folks,
We recently (about a week ago) added some lines to this project explaining that the idea behind it is to get familiar with the process of testing itself before learning all the nitty-gritty details of it. If you still feel the project is too hard to understand though, I’d be really interested to hear the specifics and how it could be improved.

2 Likes

yes, I’ve had the same issue.

Good day,

This is just my two cents, but perhaps have a module before the actual project which takes you into writing tests, similar to the “writing good tests with Mocha” with the exception of it being based on the Node.js assertion library and not Mocha.

That way when we reach the project, we have an idea as to how one would actually write a test, instead of just seeing the code.

Same here. I just came across it in Frontend Career Path.

I agree. not enough information to even really get started with this one. https://jasmine.github.io/1.3/introduction.html – some good information here, but still not really enough. I’m hoping that the advice above (skip this practical for now) will work. lets hope codecademy can resolve this issue, which seems to be a lesson order problem.

I know it causes a little anxiety to leave something left undone like that. But, just go through all of the TDD modules after it.
By the time you go back to the cake module, it will make sense and you’ll complete it without the confusion.