Final Code and Test Suite
(due at end of semester, as individual Canvas assignments submission)

• P4A.1 Final Code
  • description of the required build and test environment (e.g. base system, packages to be installed)
  • working, auto-buildable implementations for all of your modules
  • working, fully automated implementations for all of your test cases
  • descriptions of any changes (and updated specs/designs) since P3
  • table of contents, describing which files (in the repo) comprise which components
• P4A.2 Test Execution Results
  • output from a completely automated test suite run, clearly showing the passage of all test cases.
• P4B (in parallel with P4A)
  • consider which components/modules should be:
    • implemented with Pair Programming
    • implemented with Test Driven Development
    • submitted for Code Review
• P4C Moving Forward
  • you will be asked to, on a clean machine, do:
    • a clone of your repo(s)
    • a complete build (at least of your component)
    • a run (and pass) of your automated (component) unit-test suite
    Create your build and test scripts with this demo in mind.