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

await select in edit mode #2114

Conversation

labkey-chrisj
Copy link
Contributor

Rationale

Recently, BiologicsSampleTimelineTest.testEditSampleDetailCausesTimelineEvent has failed in 24.7 because the 'status' select was not found (but was present in the after-failure screenshot) when the test attempted to edit a sample's status in order to verify that doing so would cause a timeline event.

This change backports the fix for this intermittent failure from develop; the test will now await the select as it does in develop

Related Pull Requests

n/a

Changes

one-line backport from develop

@labkey-chrisj labkey-chrisj requested a review from a team October 28, 2024 16:22
@labkey-chrisj labkey-chrisj self-assigned this Oct 28, 2024
@labkey-chrisj labkey-chrisj requested review from labkey-danield and removed request for a team October 28, 2024 16:22
Copy link

ERROR: Branch doesn't match LabKey naming scheme: 24_7_fb_detailTableEditWaitForSelect
A branch intended for develop should be named something like fb_24_7_fb_detailTableEditWaitForSelect

@labkey-chrisj labkey-chrisj changed the base branch from develop to release24.7-SNAPSHOT October 28, 2024 16:26
@labkey-chrisj labkey-chrisj deleted the 24_7_fb_detailTableEditWaitForSelect branch October 29, 2024 17:28
@labkey-chrisj
Copy link
Contributor Author

Unfortunately, this PR's remote branch didn't match TeamCity's naming pattern and thus didn't get a build check (which is required). So, deleting this branch, pushing the same change to a branch that will get a build check

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants