Skip to content

Have tests wait for app content#499

Merged
labkey-tchad merged 4 commits intodevelopfrom
fb_waitForAppContent
Oct 14, 2020
Merged

Have tests wait for app content#499
labkey-tchad merged 4 commits intodevelopfrom
fb_waitForAppContent

Conversation

@labkey-tchad
Copy link
Copy Markdown
Member

Rationale

Now that error pages are a special single-page app, tests need to know how to wait for them to load. Several tests have been failing because an expected error wasn't present soon enough. Waiting for such errors on a case-by-case basis isn't a viable solution because we need to notice them when they aren't expected (especially in the Crawler).

Changes

  • If a single page app container is present after a page load, wait for it to contain something.

@labkey-tchad labkey-tchad requested review from a team, labkey-ankurj, labkey-chrisj, labkey-danield, labkey-nicka and labkey-sweta and removed request for a team October 13, 2020 23:42
Copy link
Copy Markdown
Contributor

@labkey-ankurj labkey-ankurj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good, I was adding waits in fbs for the cases.
Thanks,
Ankur

Copy link
Copy Markdown
Contributor

@labkey-chrisj labkey-chrisj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It may be worth wrapping an error page up into its own page class eventually, but this is good

@labkey-tchad labkey-tchad merged commit 2b836f0 into develop Oct 14, 2020
@labkey-tchad labkey-tchad deleted the fb_waitForAppContent branch October 14, 2020 17:02
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.

4 participants