CPSC 480-020 Software Engineering (SE) Fall 2024

Week 10 Class 18 Tue Oct 29 Posted: Oct 29

Announcements

• Exercise 34: AddTest

  • Never include .cpp files. That does not fix the build
  • Do not put function definitions in .hpp files, especially when they already exist in the .cpp file. That breaks the build
  • When someone shows you where to put the test cases, and carefully explains it to you, follow what they say or All of your code will be thrown out

Class

• Exercise 38: AddTest II

  Add another test to your add-test-* repository.

  Before you start, accept the pull request to setup your repository for this and future tests. The pull request removes the individual test files. All tests are now only in testAdd.cpp.

  Make sure to pay attention to the feedback from Exercise 34: AddTest. Note that I will not be as lenient on this excercise.

  If you never did this, then you have to do Exercise 34 first.

• Test Directory Structure Comparison

• Exercise 37: sortTDD

  Code along in class (or later on) to the sortTDD example. The GitHub Classroom link is in Brightspace.

  The TDD workflow for this code is:

  1. Add a single new test case for a single specific rule in the test program sortTest.cpp
  2. Successfully compile and build
  3. Run the test program and verify that the test case fails (red)
  4. Add the implementation only for the new test case in the file sort.cpp
  5. Successfully compile and build
  6. Run the test program and verify that all tests pass, including the new test case (green)
  7. Refactor the test and the added code
  8. Successfully compile and build
  9. Run the test program and verify that all tests still pass, including the new test case (refactor)
  10. Commit with a commit message about the added functionality

  Class example: sort-tdd-020

  The starting code already had a commit (you won't see this) for the first pass through the TDD workflow:

• HFSD Chapter 8

• Exercise 39: HFSD Chapter 8 Crossword

  Delayed until after next class.

• Exercise 40: Team Code Coverage II

  Finish up the Exercise 36: Team Code Coverage.

  As with almost all Team exercises, you must upload your work by the end of class.

Unless stated otherwise, all exercises are due by 3 pm on Wed Oct 30