-
-
Notifications
You must be signed in to change notification settings - Fork 516
Improved devcontainer setup with e2e test mini infra #2672
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
base: master
Are you sure you want to change the base?
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #2672 +/- ##
==========================================
+ Coverage 97.39% 97.41% +0.01%
==========================================
Files 135 135
Lines 5229 5229
==========================================
+ Hits 5093 5094 +1
+ Misses 136 135 -1
🚀 New features to boost your workflow:
|
9c29d73
to
1830579
Compare
76a9bbf
to
e4724c2
Compare
This enables using top-level dir as a place to run rake tasks etc. too without warnings about duped gems in Gemfiles.
7037553
to
269df71
Compare
}, | ||
define: { | ||
__RAILS_API_URL__: JSON.stringify(process.env.SENTRY_E2E_RAILS_APP_URL || 'http://localhost:4000') | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bug: Vite Environment Variable Prefix Issue
The Svelte app uses import.meta.env.SENTRY_DSN_JS
, but this environment variable is not exposed to client-side code by Vite. Vite only exposes variables prefixed with VITE_
by default, causing the Sentry DSN to be undefined. This can be fixed by renaming the variable to VITE_SENTRY_DSN_JS
or explicitly defining it in vite.config.js
.
This reworks our devcontainer setup so that it uses pre-built base images grabbed from ghcr.io and enables running e2e tests easily both on CI and locally.
There's a top level setup now in the root dir under
spec
where we can write high-level cross-gem e2e tests.This is a solid foundation for building even more conveniences around development/debugging/testing in the future 🙂
To run e2e tests locally you can simply do:
#skip-changelog