CPSC 480-020 Software Engineering (SE) Fall 2024

Week 10 Class 19 Thu Oct 31 Posted: Oct 31

After Class

• 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".

• Attribute

For the Attribute assignment, I made a fix to the assignment repository. Your repositories are forks of the assignment repository.

The fix is to the testRun.sh and testRunEmpty.sh files. When run by themselves, it works fine. But when you use the make test-run and make test-run-empty, it always fails.

If you created your repository after I made this change, you will have the fix. However, if you created it before the change you will need the fix.

To get this fix, sync with the fork on GitHub. You will have to do a git pull in your cloned repository to get the changes.

• gh

  

  All of your Attribute repositories are forks of UACPSC/cpsc-480-se-fall-2024-attribute-Attribute-1 as you can view in GitHub. The GitHub command-line program, gh, and/or git has a default repository for many of its commands. This default is not your repository, but the original UACPSC/cpsc-480-se-fall-2024-attribute-Attribute-1. This is not the behavior that we want.

  To change use the command:

  and select your repository for the default.

Announcements

• Renumbering We renumbered a couple of exercises that shared the same number.
• Guide: Issues with Code Coverage
• Project 3: Code Analysis TDD

Class

• Exercise 41: Attribute

  Use the Refactoring Guidelines from Project 3 to improve the attribute.cpp file. Each improvement must be in a separate commit with a valid commit message. There are two targets for testing to help sure you do not change the behavior of the code: make test-run and make test-run-empty.

  Make sure to run both tests and that the tests pass after any change and especially before the commit.

  Example: attribute-020

  GitHub Classroom invitation link is in Brightspace.

• HFSD Chapter 8
• Exercise 39: HFSD Chapter 8 Crossword
• Exercise 42: Team Mock Clock

Unless stated otherwise, all exercises are due by 3 pm on Monday, Nov 4.