Have Capybara screenshots saved to feature folder
When running tests with Capybara I'd like to save screenshots of failed steps to a feature specific folder. My current Capybara save path looks like:
Capybara::save_path = "./screenshots"
What I would want would be for it to save like
Capybara::save_path = "./screenshots/<feature_name>
I'm using Cucumber for my testing framework
ruby automated-tests cucumber capybara
add a comment |
When running tests with Capybara I'd like to save screenshots of failed steps to a feature specific folder. My current Capybara save path looks like:
Capybara::save_path = "./screenshots"
What I would want would be for it to save like
Capybara::save_path = "./screenshots/<feature_name>
I'm using Cucumber for my testing framework
ruby automated-tests cucumber capybara
How do you wish to determine the "feature_name"? What testing framework are you using?
– Tom Lord
Nov 15 '18 at 10:30
Sorry, forgot to mention, updated the question with details of the testing framework
– Psycrow
Nov 15 '18 at 10:41
add a comment |
When running tests with Capybara I'd like to save screenshots of failed steps to a feature specific folder. My current Capybara save path looks like:
Capybara::save_path = "./screenshots"
What I would want would be for it to save like
Capybara::save_path = "./screenshots/<feature_name>
I'm using Cucumber for my testing framework
ruby automated-tests cucumber capybara
When running tests with Capybara I'd like to save screenshots of failed steps to a feature specific folder. My current Capybara save path looks like:
Capybara::save_path = "./screenshots"
What I would want would be for it to save like
Capybara::save_path = "./screenshots/<feature_name>
I'm using Cucumber for my testing framework
ruby automated-tests cucumber capybara
ruby automated-tests cucumber capybara
edited Nov 15 '18 at 10:41
Psycrow
asked Nov 15 '18 at 10:17
PsycrowPsycrow
1063
1063
How do you wish to determine the "feature_name"? What testing framework are you using?
– Tom Lord
Nov 15 '18 at 10:30
Sorry, forgot to mention, updated the question with details of the testing framework
– Psycrow
Nov 15 '18 at 10:41
add a comment |
How do you wish to determine the "feature_name"? What testing framework are you using?
– Tom Lord
Nov 15 '18 at 10:30
Sorry, forgot to mention, updated the question with details of the testing framework
– Psycrow
Nov 15 '18 at 10:41
How do you wish to determine the "feature_name"? What testing framework are you using?
– Tom Lord
Nov 15 '18 at 10:30
How do you wish to determine the "feature_name"? What testing framework are you using?
– Tom Lord
Nov 15 '18 at 10:30
Sorry, forgot to mention, updated the question with details of the testing framework
– Psycrow
Nov 15 '18 at 10:41
Sorry, forgot to mention, updated the question with details of the testing framework
– Psycrow
Nov 15 '18 at 10:41
add a comment |
2 Answers
2
active
oldest
votes
The way to write a parameter inside a path is the following one:
Capybara::save_path = "./screenshots/#feature_name"
add a comment |
I worked out how to do it:
Capybara::save_path = "./screenshots"
Capybara::Screenshot.register_filename_prefix_formatter(:cucumber) do |example|
"/#example.feature.name.gsub(' ', '-').gsub(/^.*/spec//,'')/screenshot_#example.name.gsub(' ', '-').gsub(/^.*/spec//,'')"
end
That results in nicely formatted screenshots where they are stored asscreenshots/<feature>/<scenario>_2018-01-01
Note: this requires thecapybara-screenshot
gem
– Thomas Walpole
Nov 15 '18 at 16:25
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53317142%2fhave-capybara-screenshots-saved-to-feature-folder%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
The way to write a parameter inside a path is the following one:
Capybara::save_path = "./screenshots/#feature_name"
add a comment |
The way to write a parameter inside a path is the following one:
Capybara::save_path = "./screenshots/#feature_name"
add a comment |
The way to write a parameter inside a path is the following one:
Capybara::save_path = "./screenshots/#feature_name"
The way to write a parameter inside a path is the following one:
Capybara::save_path = "./screenshots/#feature_name"
answered Nov 15 '18 at 10:35
rcarbarcarba
1067
1067
add a comment |
add a comment |
I worked out how to do it:
Capybara::save_path = "./screenshots"
Capybara::Screenshot.register_filename_prefix_formatter(:cucumber) do |example|
"/#example.feature.name.gsub(' ', '-').gsub(/^.*/spec//,'')/screenshot_#example.name.gsub(' ', '-').gsub(/^.*/spec//,'')"
end
That results in nicely formatted screenshots where they are stored asscreenshots/<feature>/<scenario>_2018-01-01
Note: this requires thecapybara-screenshot
gem
– Thomas Walpole
Nov 15 '18 at 16:25
add a comment |
I worked out how to do it:
Capybara::save_path = "./screenshots"
Capybara::Screenshot.register_filename_prefix_formatter(:cucumber) do |example|
"/#example.feature.name.gsub(' ', '-').gsub(/^.*/spec//,'')/screenshot_#example.name.gsub(' ', '-').gsub(/^.*/spec//,'')"
end
That results in nicely formatted screenshots where they are stored asscreenshots/<feature>/<scenario>_2018-01-01
Note: this requires thecapybara-screenshot
gem
– Thomas Walpole
Nov 15 '18 at 16:25
add a comment |
I worked out how to do it:
Capybara::save_path = "./screenshots"
Capybara::Screenshot.register_filename_prefix_formatter(:cucumber) do |example|
"/#example.feature.name.gsub(' ', '-').gsub(/^.*/spec//,'')/screenshot_#example.name.gsub(' ', '-').gsub(/^.*/spec//,'')"
end
That results in nicely formatted screenshots where they are stored asscreenshots/<feature>/<scenario>_2018-01-01
I worked out how to do it:
Capybara::save_path = "./screenshots"
Capybara::Screenshot.register_filename_prefix_formatter(:cucumber) do |example|
"/#example.feature.name.gsub(' ', '-').gsub(/^.*/spec//,'')/screenshot_#example.name.gsub(' ', '-').gsub(/^.*/spec//,'')"
end
That results in nicely formatted screenshots where they are stored asscreenshots/<feature>/<scenario>_2018-01-01
answered Nov 15 '18 at 12:07
PsycrowPsycrow
1063
1063
Note: this requires thecapybara-screenshot
gem
– Thomas Walpole
Nov 15 '18 at 16:25
add a comment |
Note: this requires thecapybara-screenshot
gem
– Thomas Walpole
Nov 15 '18 at 16:25
Note: this requires the
capybara-screenshot
gem– Thomas Walpole
Nov 15 '18 at 16:25
Note: this requires the
capybara-screenshot
gem– Thomas Walpole
Nov 15 '18 at 16:25
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53317142%2fhave-capybara-screenshots-saved-to-feature-folder%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
How do you wish to determine the "feature_name"? What testing framework are you using?
– Tom Lord
Nov 15 '18 at 10:30
Sorry, forgot to mention, updated the question with details of the testing framework
– Psycrow
Nov 15 '18 at 10:41