Seeding Report: Test Direct Seeding Summary Table

[braughtg]

The tests should generate seeding reports as appropriate to check that the Direct Seeding Summary Table at the bottom of the report:

• - exists and is visible when “All” or “Direct Seedings” is selected in the seeding type filter.
• - does not exists or is not visible when “Tray Seedings” is selected in the seeding type filter.
• - displays a message if “All” or “Direct Seedings” is selected but there are no direct seedings in the date range used to generate the report.

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.
• These tests should utilize logs that are in the sample database. 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.

---

Original issue by braughtg
Tuesday Apr 04, 2023 at 16:48 GMT