3.2.a) As DEVELOPERS, we want to RESTRUCTURE OUR PROJECT and CREATE TEST PROJECTS so that THE CHIRP APP AND CSV DATABASE ARE THOROUGHLY TESTED.

[JaSNOHo]

Acceptance criteria:

• Restructure the project so that the Chirp application and the CSV database library are under a src/ directory.
  • Use git mv to move files and directories while restructuring.
• Create XUnit .NET test projects in a test/ directory at the root of the project.
  • One test project should test the Chirp CLI app.
  • A second test project should test the CSV database library.
• Make the test projects depend on their respective systems under test (SUT):
  • Add a reference from each test project to the appropriate system under test (Chirp CLI or CSV database) using the dotnet add reference command.
• Unit Tests:
  • Add unit tests for the Chirp CLI app.
  • Add tests for suitable functionality, e.g., conversion of UNIX timestamps to user-readable times.
• Integration Tests:
  • Add integration tests for the CSV database library to verify it functions as expected.
  • For example, add a test case that verifies an entry can be retrieved from the database after being stored.
• End-to-End Tests:
  • Add two end-to-end tests for the Chirp CLI app.
    • Test that running chirp read 10 with example data from chirp_cli_db.csv produces the expected output.
    • Test that running chirp cheep "Hello!!!" stores the respective values in the database.