SeedingInput: Create Seeding Log Canceled

[braughtg]

The Seeding Input form on the FieldKit tab is used to create new seeding logs in the database.
When the Seeding Input form is completed and the “Submit” button is clicked, the user is presented with “Confirm” and “Cancel” buttons.

This test must confirm that when the “Cancel” button is clicked:

• All of the input elements in the form remain populated with their existing values.
  • - when creating a tray seeding.
  • - when creating a direct seeding.
• - the “Submit” button is enabled.
• - no log was created in the data base.

Notes:

• The test must enter data into the form and use the “Cancel” button
• The test should not use the Seeding Report to check the contents of new logs.
• The test must use appropriate FarmOSAPI functions to:
  • Ensure that the log was not created in the database.
• 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.

---

Original issue by braughtg
Thursday Aug 17, 2023 at 18:46 GMT