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

Merge dev Version to trunk and release 1.1.0 #194

Merged
merged 153 commits into from
Jan 13, 2025
Merged

Merge dev Version to trunk and release 1.1.0 #194

merged 153 commits into from
Jan 13, 2025

Conversation

Mai-Saad
Copy link
Contributor

@Mai-Saad Mai-Saad commented Jan 13, 2025

Description

This PR to merge e2e fixes to the trunk and release e2e 1.1.0

Type of change

  • New feature (non-breaking change which adds functionality).
  • Bug fix (non-breaking change which fixes an issue).
  • Enhancement (non-breaking change which improves an existing functionality).
  • Breaking change (fix or feature that would cause existing functionality to not work as before).
  • Sub-task of #(issue number)
  • Chore
  • Release

List any new dependencies that are required for this change.

  • The config file shall be updated as per the sample-config.ts file
  • Admin 2 is needed on test env (credentials data is needed in config file to be used in test)
  • imagify key is needed in the config file to be used in the test

Risks

None

Mandatory Checklist

Code validation

  • I validated all the Acceptance Criteria. If possible, provide screenshots or videos.
  • I triggered all changed lines of code at least once without new errors/warnings/notices.
  • I implemented built-in tests to cover the new/changed code.

Code style

  • I wrote a self-explanatory code about what it does.
  • I protected entry points against unexpected inputs.
  • I did not introduce unnecessary complexity.
  • Output messages (errors, notices, logs) are explicit enough for users to understand the issue and are actionnable.

Unticked items justification

If some mandatory items are not relevant, explain why in this section.

Additional Checks

  • In the case of complex code, I wrote comments to explain it.
  • When possible, I prepared ways to observe the implemented system (logs, data, etc.).
  • I added error handling logic when using functions that could throw errors (HTTP/API request, filesystem, etc.)

MathieuLamiot and others added 30 commits July 31, 2024 16:30
…lcp-beacon-name"

This reverts commit b6606a9, reversing
changes made to 3d53029.
…-change-lcp-beacon-name""

This reverts commit ca35844.
GH action to create a release on trunk
removed the ‘after’ property from minify_css and minify_js
…ch priority feature , renamed the feature and re-organized steps
…ns and reorder steps for export after update but still need some work there
Closes #121 Add "comments" in the JSON of expected results
Khadreal and others added 26 commits January 7, 2025 17:02
Fix #177 CPCSS notice has scenario that won't work correctly now due to the login structure
…g-log-with-errors-relating-to-wpr

Closes #67: Only rename debug.log with errors relating to WPR
…it (PR #174)

* :closes: #143 add process to rename and push test files to git

* Add PAT variable to config

* Add option to initialised for empty directory

* Fix import error

* Add bash script and modify report file

* Remove unused variable, clean up report file -- #143

* Modify bash script

* Update scripts and command

* Change the default destination directory

* Modify scripts, deleted bash script --#143

* Refactor script and command, revert config modifications

* Modify command to make sure subsequent commands run

---------

Co-authored-by: Mai <[email protected]>
Closes #129 Automate the scenario that check LL isnot applied on LCP/ATF images
…-warning

Closes #183: Operation not permitted warning on dev latest commit
…s-to-be-generic-for-all-wpr-features

Closes #140: Isolate VR Tests to be generic for all WPR features
@Mai-Saad
Copy link
Contributor Author

e2e report is on the shared folder /var/shared/rocket-e2e-reports/wpr3.18_e2edev1.1.0_all
Screenshot from 2025-01-13 16-13-10

@Mai-Saad Mai-Saad requested a review from a team January 13, 2025 14:29
@Mai-Saad Mai-Saad merged commit 6a883f5 into trunk Jan 13, 2025
6 of 15 checks passed
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.

6 participants