CPSC 480-020 Software Engineering (SE) Fall 2025

Week 11 Class 20 Tue Nov 04 Posted: Nov 04

Announcements

• Special Office Hours Today 10:30 - 10:45 am, 3:15 - 4:15 pm. Make up for shortened early Office Hours.
• Project 2 Scores in Brightspace. Feedback in the branch feedback in the file Feedback.md.
• Exercises Caught up with feedback and grading for sortTDD, and the team exercises. Suggest you look at the feedback.
• Project 3: Code Analysis TDD Remember the deadlines

• Exercise 43: Project 3 Feedback 1

  The feedback for this exercise (and your first commit to Project 3: Code Analysis TDD) is in Brightspace.

  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.

  Also, further exercises for the progressive due dates will not provide feedback on the commit messages, content of the commit, etc. Only on the number of test cases, which should equate to the number of rules implemented.

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

  General Comments:

  • The commit message should not mention the test. In a TDD process, we assume the test with every commit that adds functionality.
  • 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.
  • Each test specifies the input (the settings of the fields in the request) and the output (the string returned from formatAnalysisXML()). Use of find(), or substring checking is not part of the test case. Do not make your test case have more complexity (i.e., number of conditions) than your implementation
  • Keep in mind the rule about a single attribute output, unit.addAttribute(), for every unique attribute.
  • 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

• HFSD Chapter 8
• Git Commit Messages
• HFSD Chapter 9
• Exercise 44: Team Mock Clock II

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