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

run e2e tests over https #2253

Open
wants to merge 6 commits into
base: next
Choose a base branch
from
Open

run e2e tests over https #2253

wants to merge 6 commits into from

Conversation

djskinner
Copy link
Contributor

@djskinner djskinner commented Nov 14, 2024

Goal

Get the browser e2e tests running over https so we can test functionality that requires a secure context.

Design/Changeset

  • Set the new --https flag on maze runner
  • Update the test fixtures to use the new docs endpoint being served from /docs
  • Do not use https for the following: ie11, safari16, ios10

Testing

e2e tests passing locally and on CI

@djskinner djskinner changed the title Https run e2e tests over https Nov 14, 2024
Copy link

github-actions bot commented Nov 14, 2024

@bugsnag/browser bundle size diff

Minified Minfied + Gzipped
Before 45.89 kB 13.78 kB
After 45.89 kB 13.78 kB
± No change No change

code coverage diff

<temporarily disabled>

Generated by 🚫 dangerJS against 07d479c

test/browser/features/support/env.rb Outdated Show resolved Hide resolved
test/browser/features/support/env.rb Outdated Show resolved Hide resolved
test/browser/features/support/env.rb Outdated Show resolved Hide resolved
Comment on lines +172 to +174
#
# BrowserStack non-https tests
#
Copy link
Contributor Author

Choose a reason for hiding this comment

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

not sure if there's a DRYer way of doing this rather than duplicating most of the previous section? A parameterized matrix, perhaps?

Copy link
Contributor

Choose a reason for hiding this comment

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

I don't think so unfortunately, the Buildkite YAML schema is quite limited when it comes to any kind of commonality or logic between steps.

@djskinner djskinner marked this pull request as ready for review November 15, 2024 16:54
Copy link
Contributor

@twometresteve twometresteve left a comment

Choose a reason for hiding this comment

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

Nice one - thanks.

Comment on lines +172 to +174
#
# BrowserStack non-https tests
#
Copy link
Contributor

Choose a reason for hiding this comment

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

I don't think so unfortunately, the Buildkite YAML schema is quite limited when it comes to any kind of commonality or logic between steps.

Copy link
Contributor

Choose a reason for hiding this comment

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

We're just removing Gemfile.locks from Git these days to reduce dependabot warnings - but you could just do that on your next PR to avoid another build.

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