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
0
Merge Requests
0
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
Boxiang Sun
gitlab-ce
Commits
043810f7
Commit
043810f7
authored
Dec 07, 2017
by
Grzegorz Bizon
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Fix runtime QA browser and capturing screenshots
[ci skip]
parent
fc00d739
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
4 additions
and
2 deletions
+4
-2
qa/qa/runtime/browser.rb
qa/qa/runtime/browser.rb
+4
-2
No files found.
qa/qa/runtime/browser.rb
View file @
043810f7
...
@@ -6,7 +6,7 @@ require 'selenium-webdriver'
...
@@ -6,7 +6,7 @@ require 'selenium-webdriver'
module
QA
module
QA
module
Runtime
module
Runtime
class
Browser
class
Browser
include
Scenario
::
Actable
include
QA
::
Scenario
::
Actable
def
initialize
def
initialize
self
.
class
.
configure!
self
.
class
.
configure!
...
@@ -63,9 +63,11 @@ module QA
...
@@ -63,9 +63,11 @@ module QA
block
.
call
if
block_given?
block
.
call
if
block_given?
rescue
rescue
raise
if
block
.
nil?
# RSpec examples will take care of screenshots on their own
# RSpec examples will take care of screenshots on their own
#
#
unless
block
.
binding
.
receiver
.
class
<
RSpec
::
Core
::
ExampleGroup
unless
block
.
binding
.
receiver
.
is_a?
(
RSpec
::
Core
::
ExampleGroup
)
Capybara
::
Screenshot
.
screenshot_and_save_page
Capybara
::
Screenshot
.
screenshot_and_save_page
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