Seeding Report: Test Seeding Log(s) Deleted

[braughtg]

The Seeding Report allows logs to be deleted. To delete a log, the checkbox in the leftmost column of the table is checked and the “Delete” button (the trashcan at the top right of the table) is clicked. Multiple rows can be deleted by checking multiple rows before clicking the “Delete” button.

This test should ensure:

• That a single row can be deleted:
  • - the row is removed from the table.
  • - the corresponding log in the database has also been deleted.
• That multiple rows can be deleted:
  • - all of the selected rows are removed from the table.
  • - all of the corresponding logs in the database have also been deleted.
• That if the delete is canceled then:
  • - the rows are not removed from the table
  • - the corresponding logs are not removed from the database.

Notes:

• The test must use appropriate FarmOSAPI functions to:
  • Create new logs that will be deleted by the test.
  • Check that deleted logs no longer exist in the database.
  • Delete any new logs that were created and not deleted by a test.
  • If you find that you have scrambled the database you can always reset to the default sample database running the command setDB sample in a Terminal in the development environment.

Resources:

• The examples in the dbtest sub-tab of the FD2 Example tab will be helpful. These should be studied and understood before beginning coding for this issue.
• The source for the examples can be found in farmdat2/farmdata2_modules/fd2_example/dbtest.

Additional Information:

Some additional notes relevant to this issue:

• The .spec.js file containing your test should be stored in an appropriate location and have a short but descriptive name. Use the locations and an naming from the "Good First issues" as examples.
• The .spec.js file should include a comment at the top that describes what the file as a whole is testing.
• The message for the describe should describe in a short phrase what the file is testing.
• After logging in and visiting the desired page the beforeEach method should call cy.waitForPage(). This will ensure that the page is fully loaded (e.g. that all the Maps used by the page are loaded) before performing any tests.
• It is not necessary to include a separate it for each of the things to be tested.
  • You should decide how to divide the things being tested into its so that each it tests a cohesive set of things.
  • The message for each it should describe in a short phrase what the it is testing.
• The .spec.js files in the farmdata2/farmdata2_modules/fd2_example/ sub-tabs (e.g. ui, api) may provide some helpful examples.
• Information about the data contained in the sample database can be found in the "The Sample Database" section of the docker/sampleDB/README.md file.

[balemae]

Team 2 will like to work on this