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

test(docs-infra): add e2e test for the contributors page #29601

Closed
wants to merge 2 commits into from

Conversation

gkalpak
Copy link
Member

@gkalpak gkalpak commented Mar 29, 2019

Previously, if the shape of data in contributors.json was incorrect, there would be a runtime error (when trying to parse the data), which would result in a blank page. The likelihood for this happening is higher after #29553, where the shape of data changed.

This commit adds some basic e2e tests that verify the page works as expected and there are contributors listed.

(This PR also includes a commit to use a smaller image for @jbedard (since it was already available) 😁)

@gkalpak gkalpak added action: merge The PR is ready for merge by the caretaker comp: docs-infra target: patch This PR is targeted for the next patch release labels Mar 29, 2019
@ngbot ngbot bot added this to the needsTriage milestone Mar 29, 2019
@mary-poppins
Copy link

You can preview d01a6bf at https://pr29601-d01a6bf.ngbuilds.io/.

Previously, if the shape of data in `contributors.json` was incorrect,
there would be a runtime error (when trying to parse the data), which
would result in a blank page. The likelihood for this happening is
higher after angular#29553, where the shape of data changed.

This commit adds some basic e2e tests that verify the page works as
expected and there are contributors listed.
@gkalpak gkalpak force-pushed the build-aio-contributors-checks branch from d01a6bf to 2230d5c Compare March 29, 2019 22:24
@mary-poppins
Copy link

You can preview 2230d5c at https://pr29601-2230d5c.ngbuilds.io/.

@gkalpak gkalpak marked this pull request as ready for review March 29, 2019 22:34
@gkalpak gkalpak requested review from a team as code owners March 29, 2019 22:34
@gkalpak gkalpak added state: blocked and removed action: merge The PR is ready for merge by the caretaker labels Mar 29, 2019
@gkalpak
Copy link
Member Author

gkalpak commented Mar 29, 2019

Blocked on #29596 (because that one must be merged first).
UPDATE: #29596 has been merged. This is now unblocked.

@gkalpak gkalpak added this to REVIEW in docs-infra Mar 30, 2019
@petebacondarwin petebacondarwin moved this from REVIEW to MERGE in docs-infra Mar 30, 2019
@gkalpak gkalpak added action: merge The PR is ready for merge by the caretaker and removed state: blocked labels Apr 1, 2019
jasonaden pushed a commit that referenced this pull request Apr 1, 2019
Previously, if the shape of data in `contributors.json` was incorrect,
there would be a runtime error (when trying to parse the data), which
would result in a blank page. The likelihood for this happening is
higher after #29553, where the shape of data changed.

This commit adds some basic e2e tests that verify the page works as
expected and there are contributors listed.

PR Close #29601
@jasonaden jasonaden closed this in cd6581e Apr 1, 2019
jasonaden pushed a commit that referenced this pull request Apr 1, 2019
Previously, if the shape of data in `contributors.json` was incorrect,
there would be a runtime error (when trying to parse the data), which
would result in a blank page. The likelihood for this happening is
higher after #29553, where the shape of data changed.

This commit adds some basic e2e tests that verify the page works as
expected and there are contributors listed.

PR Close #29601
@gkalpak gkalpak deleted the build-aio-contributors-checks branch April 1, 2019 18:37
gkalpak added a commit to gkalpak/angular that referenced this pull request Apr 1, 2019
One of the tests introduced in angular#29601 is susceptible to a kind of
WebDriver flake related to trying to click elements hidden behind fixed
positioned elements.
This commit works around the issue by clicking the elements directly
using JavaScript (instead of `WebElement#click()`).
jasonaden pushed a commit that referenced this pull request Apr 1, 2019
One of the tests introduced in #29601 is susceptible to a kind of
WebDriver flake related to trying to click elements hidden behind fixed
positioned elements.
This commit works around the issue by clicking the elements directly
using JavaScript (instead of `WebElement#click()`).

PR Close #29641
jasonaden pushed a commit that referenced this pull request Apr 1, 2019
One of the tests introduced in #29601 is susceptible to a kind of
WebDriver flake related to trying to click elements hidden behind fixed
positioned elements.
This commit works around the issue by clicking the elements directly
using JavaScript (instead of `WebElement#click()`).

PR Close #29641
wKoza pushed a commit to wKoza/angular that referenced this pull request Apr 17, 2019
wKoza pushed a commit to wKoza/angular that referenced this pull request Apr 17, 2019
Previously, if the shape of data in `contributors.json` was incorrect,
there would be a runtime error (when trying to parse the data), which
would result in a blank page. The likelihood for this happening is
higher after angular#29553, where the shape of data changed.

This commit adds some basic e2e tests that verify the page works as
expected and there are contributors listed.

PR Close angular#29601
wKoza pushed a commit to wKoza/angular that referenced this pull request Apr 17, 2019
…9641)

One of the tests introduced in angular#29601 is susceptible to a kind of
WebDriver flake related to trying to click elements hidden behind fixed
positioned elements.
This commit works around the issue by clicking the elements directly
using JavaScript (instead of `WebElement#click()`).

PR Close angular#29641
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 14, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes target: patch This PR is targeted for the next patch release
Projects
Development

Successfully merging this pull request may close these issues.

None yet

4 participants