Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
2710482f
Commit
2710482f
authored
Jun 02, 2021
by
drew cimino
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Fix a test
parent
2796a6d6
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
2 additions
and
2 deletions
+2
-2
doc/user/project/merge_requests/browser_performance_testing.md
...ser/project/merge_requests/browser_performance_testing.md
+1
-1
ee/spec/lib/gitlab/ci/templates/Verify/browser_performance_testing_gitlab_ci_yaml_spec.rb
...Verify/browser_performance_testing_gitlab_ci_yaml_spec.rb
+1
-1
No files found.
doc/user/project/merge_requests/browser_performance_testing.md
View file @
2710482f
...
...
@@ -40,7 +40,7 @@ Consider the following workflow:
## How browser performance testing works
First, define a job in your
`.gitlab-ci.yml`
file that generates the
[
Browser Performance report artifact
](
../../../ci/yaml/README.md#artifactsreportsbrowserperformance
)
.
[
Browser Performance report artifact
](
../../../ci/yaml/README.md#artifactsreportsbrowser
_
performance
)
.
GitLab then checks this report, compares key performance metrics for each page
between the source and target branches, and shows the information in the merge request.
...
...
ee/spec/lib/gitlab/ci/templates/Verify/browser_performance_testing_gitlab_ci_yaml_spec.rb
View file @
2710482f
...
...
@@ -42,7 +42,7 @@ RSpec.describe 'Verify/Browser-Performance.gitlab-ci.yml' do
shared_examples_for
'browser_performance job on tag or branch'
do
it
'by default'
do
expect
(
build_names
).
to
include
(
'performance'
)
expect
(
build_names
).
to
include
(
'
browser_
performance'
)
end
end
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment