Check Your Submission

After all the work you’ve done, it’s important to make sure that your submission is in good shape and that you won’t lose points for silly things.

Testing

Remember: the autograder will alert you about big problems, like if your submission won't compile and/or run.

It won't tell you whether your implementation is correct or whether your tests are thorough. That's your job!

You have a chance before your submission to take a critical eye to your tests and improve them both to improve your chances of a good score for testing and to see if you can catch any bugs in your implementation. For each operation brainstorm as many publicly observable consequences of that operation that you can. Make a test case for each one!

Formatting Your Code

Remember that we now allow you to use the clang-format command:

clang-format -i *.cpp *.hpp

It will try to change your .cpp and .hpp files to better match our Google-based coding style convention (with settings taken from the provided .clang-format file).

clang-format won’t fix all cpplint errors, but it does handle lots of common cases such as missing or extra curly braces or too much/not enough whitespace.

Note: Don’t use clang-format as an excuse to write ugly code, and then hope that it will magically make your code readable!

Nobody writes perfect code even with experience with a particular style. clang-format is just a tool to help you catch some of the small oversights that inevitably happen but aren't caught by the compiler.

To Complete This Part of the Assignment

You'll know you're done with this part of the assignment when you've done all of the following:

Check your style: Run cpplint on your .cpp file, and fix any remaining problems.
Turn in code that compiles: Confirm that your code compiles on the CS 70 server with no errors or warnings.
If you make any changes, redo the last two steps!
Submit all required files: Make sure that all the required files show in the VS Code interface as being under version control, and that there aren't any modified files in your local working copy that haven't been committed/pushed.
Don't submit unnecessary files: Make sure the list of files that show in the VS Code interface as being under version control looks reasonable; that is, no superfluous files (compiled machine code, macOS .DS_STORE files, etc.) have been accidentally added to your repository.
Turn in your work: Submit your code on Gradescope by navigating to the submission page for this assignment and uploading files from your GitHub repository.
Associate all team members with submission: Each time one person uploads your files on Gradescope, click the Add Group Member button on the right-hand side of the page to ensure that all team members are associated with the submission. You will lose points if both partners are not listed on your final submission.
Check your results: Gradescope will provide feedback on your code. If there are any errors indicated, you are encouraged to fix your code and resubmit. You may submit as many times as you like.

(When logged in, completion status appears here.)

Previous Page Go to Parent Page

CS 70

Warning: Missing Prerequisites

Check Your Submission

Testing

Formatting Your Code

To Complete This Part of the Assignment

Instructor Controls