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

Seeding Input: Test Submit Button Behavior #33

Open
3 tasks
braughtg opened this issue Jan 28, 2024 · 1 comment · May be fixed by #153
Open
3 tasks

Seeding Input: Test Submit Button Behavior #33

braughtg opened this issue Jan 28, 2024 · 1 comment · May be fixed by #153
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

The tests should ensure that the “Submit” button is enabled and disabled as appropriate. The button should be:

  • - initially disabled.
  • enabled only when all required fields have valid values.
    • - for Tray Seedings
    • - for Direct Seedings
  • Note that it is not necessary to test if a seeding log is created in the database if the button is clicked. That will be checked by a separate test.

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:49 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
@longbui23
Copy link

Our team (LLM) wants to work in this ticket.

@longbui23 longbui23 linked a pull request Apr 13, 2024 that will close this issue
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

Successfully merging a pull request may close this issue.

2 participants