Goal:

• Find unhanded NullPointerException and deal with it
• Preform fuzz testing
• Preform integration testing
• Continue BDD

Obligations

• Software Engineer (AJ Granowski & Joe Jagiella)

  • Builds code of high quality that runs behind the-scenes.
  • Holds code walkthrough of his/her new code before inclusion into master branch
  • Uses behavior-driven development to develop the nominal control logic (aka "happy paths").
  • Adds JavaDocs/C# XML API documentation to new methods so other team members know how to invoke the code.
  • Writes unit tests
    • NEW: write fuzz testing code.
    • Using the JUnit/Visual Studio parameterized tests format where appropriate.
    • Using mocking to replace code not under test.
  • Minimum requirements:
    • Use BDD.
    • Designs the system to be unit testable.
    • Control logic must not call or reference any GUI code.
    • Must each write at least 50 LOC.

• Software Engineer in Test (Tyler Duffy)

  • Builds quality into the system.
  • Develops automated product metrics to improve quality.
    • Reports overall non-GUI code coverage and identifies major weakpoints.
  • Uses test-driven development to add error handling to both the control logic and the GUI.
  • Uses behavior-driven development to add error handling to both the control logic and the GUI.
  • Refactors code to improve its quality.
  • Writes integration test equivalents of the unit tests
    • NEW: using an order of integration to integrate the new code (one of: top/down, bottom/up, sandwich, as appropriate).
  • Sets development best-practices.
  • Minimum requirements:
    • NEW: use BDD.
    • Must write at least 25 LOC.

• Test Engineer (Dalton Bush)

  • Performs system and exploratory testing.
    • NEW: using fuzz testing.
  • Performs code inspections of last week's work
  • Builds the GUI and required event listeners.
  • Helps the Software Engineers design their code to be used by a GUI.
  • Minimum requirements:
    • GUI code must not contain control logic - instead call your teammates' code.
    • Must write at least 25 LOC.

Deliverables

• End-to-end implementation of next major feature, committed to your GitLab.
• README describing who did what.
  • Each member is solely responsible for describing what he or she did.
  • Use the above framework to describe what you did.
• Test results according to either GitLab or Visual Studio.

Everything else you need to do can be found here.