Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Seeding Report: Restoring Functionality of End-to-End Tests #577

Open
FutzMonitor opened this issue Nov 5, 2022 · 1 comment
Open

Seeding Report: Restoring Functionality of End-to-End Tests #577

FutzMonitor opened this issue Nov 5, 2022 · 1 comment
Labels
Reserved Issue created and reserved for use in a course. testing Issues related to tests.

Comments

@FutzMonitor
Copy link
Collaborator

FutzMonitor commented Nov 5, 2022

Current Behavior

  1. Change into the farmdata2_modules directory on your command line
  2. Run the ./test_runner.bash command and follow the GUI instructions until you can the e2e test for the Seeding Report.
  3. Your test should fail and look something like this:

image

Desired Behavior

This issue should preferably be addressed after #570 has been closed. That way there's a complete e2e test that works with the new table instead of having a fix here and then having to fix it again once the table has been fixed.

Due to the vnc changes, we have updated to a newer version of Cypress that is not backwards compatible with the older version we were using with the virtual machines. As a result, many of the e2e tests have ceased functioning as expected. The aim of this issue is to learn and replace/fix the problematic methods that are causing the e2e test to fail. In particular, this issue aims to address the failed functioning of the e2e test for the Seeding Report.

@braughtg braughtg added the testing Issues related to tests. label Nov 6, 2022
@braughtg braughtg added the Reserved Issue created and reserved for use in a course. label Jan 16, 2023
@FutzMonitor
Copy link
Collaborator Author

FutzMonitor commented Feb 21, 2023

It would be worthwhile to incorporate the changes detailed in issue #566 into this issue. They're not necessary to complete the issue but doing so would provide a complete testing file using all the methods provided by the project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Reserved Issue created and reserved for use in a course. testing Issues related to tests.
Projects
None yet
Development

No branches or pull requests

2 participants