CPSC 480-010 Software Engineering (SE) Fall 2024

Week 11 Class 20 Tue Nov 05 Posted: Nov 05

Announcements

• Project 3: Code Analysis TDD Remember the deadlines

• Exercise 43: Project 3 Feedback 1

  In the branch feedback I posted a report, Report1.md. I generate this report from your code and commits. It displays the parts of the files of interest, computes complexity, and builds and runs every commit.

  Just a clarification: if you receive a 10 / 10 on this exercise, it does not mean you get 100% on that part of the project. It means that you followed the procedure. See the feedback (in the Grades) if I noticed any other issues.

  If I pointed out issues in the Brightspace feedback, you can fix those in separate commits, using the commit message that starts with "Fix".

  Most of the future due dates changed from midnight to 10 pm. See the project for details.

  General Comments:

  • The build directory must not be in the repository
  • Indentation is a fixed indentation size: 4, 8, 12, 16, … or 8,16,24,…. Even ChatGPT thinks so. Do not indent 4 then 2 spaces. Fix this immediately. And, if you do so in the future, it is a 0 for that exercise and that part of the project.
  • Each rule must have a separate test. Make the test the simplest that you can to test the feature.
  • Keep in mind the rule about a single attribute output, unit.addAttribute(), for every unique attribute.
  • The commit message should not mention the test. In a TDD process, we assume the test with every commit that adds functionality.
  • Follow the exact code formatting and style
  • Perform refactoring as part of the test and implementation of every commit
  • Treat each rule implementation (and its corresponding commit) as the last commit you will make to this repository. There is no "cleanup" stage that is not part of a TDD commit.

  • Think before every commit:

    • ✓ Added a new test to the test file
    • ✓ Added implementation to get that test to pass
    • ✓ All tests still pass
    • ✓ Refactored the code given the refactoring guidelines
    • ✓ Style of the added tests and implementation follow the coding style of the existing code
    • ✓ Did not add any incorrect files. For Project TDD, this means adding no files.

Class

• Guide: Issues with Code Coverage
• Git Commit Messages
• HFSD Chapter 9

• Exercise 44: HFSD Chapter 9 Crossword

  We did not complete the material in HFSD Chapter 9, so this crossword will be due after the next class.

• Exercise 45: Team DIP & Mock Objects II

Unless stated otherwise, all exercises are due by 3 pm on Wed Nov 06