Rename Browser Performance Testing in code
What does this MR do?
Relates #10683 (closed) Closes #220181 (closed)
Renames code paths for Browser Performance Testing feature to be more explicit. Was only named just performance before but this now needs changed in preparation for the new Load Performance Testing feature. MR changes the paths to all have the prefix browser_performance or equivalent where possible.
With this MR the default file for the report is also renamed to browser-performance.json. However, the previous performance.json has been maintained in code to ensure compatibility and continue to work for users.
MR also updates SiteSpeed version to 13.3.0 and will now show results that haven't changed in the widget:
Updated widget screenshots
Docs and tests have also beed updated. MR will also fix #220181 (closed).
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. [ ] Tested in all supported browsers[ ] Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Database Migration Output
Migrate
== 20200707094341 AddBrowserPerformanceToPlanLimits: migrating ================
-- add_column(:plan_limits, "ci_max_artifact_size_browser_performance", :integer, {:default=>0, :null=>false})
-> 0.0030s
== 20200707094341 AddBrowserPerformanceToPlanLimits: migrated (0.0031s) =======Rollback
== 20200707094341 AddBrowserPerformanceToPlanLimits: reverting ================
-- remove_column(:plan_limits, "ci_max_artifact_size_browser_performance", :integer, {:default=>0, :null=>false})
-> 0.0016s
== 20200707094341 AddBrowserPerformanceToPlanLimits: reverted (0.0036s) =======