Feature/scenario name in case of multiline scenario description #203

Merged
merged 2 commits into from Oct 30, 2012

Projects

None yet

2 participants

@pascalvanhecke

Hi,

I had

  File name too long - .../features/support/vcr_cassettes/feature-name/scenario_with_multiline_preamble_and_more_lines_and_more_lines_and_more_lines_and_more_lines_and_more_lines_and_more_lines_and_more_lines_and_more_lines_and_more_lines_and_more_lines_and_more_lines_and_more_lines_and_more_lines_and_more_lines_and_more_lines_and_more_lines_and_more_lines_and_more_lines_and_more_lines_and_more_lines_and_more_lines.yml (Errno::ENAMETOOLONG)

This issue is totally analogous to https://github.com/myronmarston/vcr/issues/157 and I quasi-copied the changes you did in myronmarston@034bdaf

The change in .gitignore is of course optional, but can help other users of Rubymine (and I think it's a good practice to exclude config dirs for popular editors anyway)

Thanks for your work!

Pascal Van H... added some commits Oct 29, 2012
Pascal Van Hecke Excluding Rubymine project config files from repo 126c5af
Pascal Van Hecke Only use the first line of the cuke scenario name in the cassette name.
Just like features, scenarios can have multiline preambles. When
using the :use_scenario_name option, VCR will only use the first line
of the scenario name as the directory for the cassette. This change
is modeled after commit 034bdaf
978f932
@myronmarston myronmarston merged commit 7d59ed7 into vcr:master Oct 30, 2012

1 check passed

default The Travis build passed
Details
@myronmarston
Member

Thanks!

@pascalvanhecke pascalvanhecke deleted the pascalvanhecke:feature/scenario_name_in_case_of_multiline_scenario_description branch Feb 19, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment