W7D5

Lists, Stacks, and Queues Lecture Notes

Assessment Prep

Empty Learning Objectives

Filled out Learning Objectives

Approaching Future Assessment Tips on VS Code Problems

1. Read the README.md CAREFULLY.

• If you have trouble with reading comprehension and making sure you get details, take notes on the important points
• Includes:
  • which files that you should be modifying
  • a brief overview of the problems
  • what you shouldn’t be doing
  • submission instructions

2. Have an node terminal open for testing little bits of code

• check your sanity and small bits of code to see if that chunk of code is working as you expect to be working

4. Read the problem statement CAREFULLY and make bulletpoints that you can use as a checklist to make sure you solve the problem the way we expect you to solve it.

• Make note of the goals of the problem
• Make note of the input to the problem (any parameters to the function? what are the inputs expected to be in the form of (like an array/string)?)
• Make note of the output to the problem and what the output should be in a form of (array/string). If output needs to be returned, make note of that, Make sure to return using the return keyword

3. Open up the spec file for side by side with the problem file and skim through the spec file to see what the problem is requiring you to do

• See how the test is testing your code
  • How is it getting the functions/classes/variables from the problem file(s)?
  • What is it looking for in the functions/classes/variables?

4. Test your code using examples!

• examples can be found in description or in the spec files BUT you may want to simplify the examples in them

5. Run the test! Use the command to run the code specified.

• Check the error messages!! Mocha shows error messages for each failed spec (If you don’t know how to do this, please ask!)

Other tips: - Walk through your code with a small, condensed example if you get stuck. You may see the problem when you walk through your code using comments to the side and replacing values. Basically, execute the code like how you expect the computer to execute it using a specific input. - Use console.log’s by guessing what should be logged first BEFORE running the code and comparing it with what’s actually logged

Format of Assessment

• You will have 2 hours to complete the assessment
• The assessment has two major sections
  1. ~20 Multiple Choice Questions
  2. VS Code Questions
  • 4 different problems in total
  • ~20 specs to pass spread across all problems