-
Notifications
You must be signed in to change notification settings - Fork 2
test: Assert Android web global configuration #118
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: trunk
Are you sure you want to change the base?
Conversation
Other tasks use this anchor to avoid repetition.
plugins: &plugins | ||
- $CI_TOOLKIT_PLUGIN | ||
- $NVM_PLUGIN | ||
plugins: *plugins |
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.
This task appeared to be an outlier, where all other tasks rely upon this existing plugins anchor definition.
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.
Pull Request Overview
The PR adds comprehensive unit tests to assert the Android WebView global configuration and refines the build pipeline to include testing for the Android library.
- Added unit tests in EditorConfigurationTest.kt for validating configuration properties and JavaScript conversions of WebView global values.
- Updated the Buildkite pipeline to leverage plugin alias references and added a new step for testing the Android library.
Reviewed Changes
Copilot reviewed 2 out of 3 changed files in this pull request and generated no comments.
File | Description |
---|---|
android/Gutenberg/src/test/java/org/wordpress/gutenberg/EditorConfigurationTest.kt | Added tests for configuration and WebViewGlobal conversion functions. |
.buildkite/pipeline.yml | Refactored plugins usage and added an Android library test step. |
Files not reviewed (1)
- Makefile: Language not supported
What?
Assert Android WebView global configuration. Close CMM-283.
Why?
Avoid regressions within the regex and string manipulation.
How?
Add automated unit tests.
Testing Instructions
N/A, no user-facing changes.
Accessibility Testing Instructions
N/A, no user-facing changes.
Screenshots or screencast
N/A, no user-facing changes.