Skip to content
This repository has been archived by the owner on Aug 26, 2024. It is now read-only.

Seeding Report: Test Direct Seeding Summary Values #35

Open
5 tasks
braughtg opened this issue Jan 28, 2024 · 0 comments
Open
5 tasks

Seeding Report: Test Direct Seeding Summary Values #35

braughtg opened this issue Jan 28, 2024 · 0 comments
Labels
Good Second Issue An issue that is a little deeper than a good first issue. testing Issue related to testing FarmData2 functionality

Comments

@braughtg
Copy link
Member

When a Seeding Report that contains direct seedings is generated, a Direct Seeding Summary table appears below the table. This summary contains data that is computed from the data in the table.

This test must check that the values reported for the following quantities agree with the data in the table:

  • Total Row Feet Planted
  • Total Bed Feet Planted
  • Total Hours
  • Average Row Feet/Hour
  • Average Bed Feet/Hour

Notes:

  • The report that is tested on must contain a minimum of 3 direct seeding logs.
  • Every summary value must depend upon values in multiple logs.
  • No summary value may be zero.
  • Expected values should be hand computed from the sample data that are hard coded into the test.

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.
  • 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 11, 2023 at 04:44 GMT

@braughtg braughtg added Good Second Issue An issue that is a little deeper than a good first issue. testing Issue related to testing FarmData2 functionality labels Jan 28, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Good Second Issue An issue that is a little deeper than a good first issue. testing Issue related to testing FarmData2 functionality
Projects
None yet
Development

No branches or pull requests

1 participant