Skip to content

Rename Browser Performance Testing in code

Grant Young requested to merge gy-rename-browser-performance-widget into master

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

browser_performance_testing

Screenshot_2020-06-18_at_13.10.01

Docs and tests have also beed updated. MR will also fix #220181 (closed).

Does this MR meet the acceptance criteria?

Conformity

Availability and Testing

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) =======
Edited by Grant Young

Merge request reports

Loading