You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 11, 2024. It is now read-only.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Tests that when a log is deleted, the checkbox in the leftmost column of the table is checked and the "Delete" button is clicked. It also tests that the log is removed from the database and row is removed from the table. This also checks that Seeding Report can remove multiple rows and if the delete is canceled, the rows and corresponding logs are not removed.
FarmData2 is a Free Cultural Work and all accepted contributions are licensed as described in the LICENSE.md file. This requires that the contributor holds the rights to do so. By submitting this pull request I certify that I satisfy the terms of the Developer Certificate of Origin for its contents.
Question: How can we check the database after the removal of a log?
Description:
We are testing whether the Deleted logs are removed from the database. After creating a new log and deleting it, we couldn't utilize the supporting resources listed in ticket #32 (dbtest is absent) as a reference to test the action's performance on the database.
Resource: farmdata2/farmdata2_modules/fd2_example/dbtest
Inquiry:
Could anyone please provide insight or alternative resources that we can use to effectively verify that the log is removed from the database?
We have completed the tests that check whether clicking the delete button removes the wanted row(s) from the table. We also checked that the corresponding row is not removed when we cancel the delete action.
However, we're currently unable to validate whether the associated log(s) in the database are also removed or if the database retains its original state after canceling the delete action. Furthermore, since the delete button keeps disappearing when the page is reloaded, our tests don't have a consistent result.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
None yet
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pull Request Description
Tests that when a log is deleted, the checkbox in the leftmost column of the table is checked and the "Delete" button is clicked. It also tests that the log is removed from the database and row is removed from the table. This also checks that Seeding Report can remove multiple rows and if the delete is canceled, the rows and corresponding logs are not removed.
Closes #32
Licensing Certification
FarmData2 is a Free Cultural Work and all accepted contributions are licensed as described in the LICENSE.md file. This requires that the contributor holds the rights to do so. By submitting this pull request I certify that I satisfy the terms of the Developer Certificate of Origin for its contents.