Rspec fixture file path

Our objective is to be able to run our spec tests via rake , and we tell rake where our tests are located. Our Rakefile would look like the following:.

Finally, we configure bundler and write our Gemfile. The packages we need to run our tests will be specified here. It should look like:. Now, all there is to do is to run bundle install which will download dependencies for us. And we are able to run tests with bundle exec rake. Skip to content If you have been following the rspec-puppet tutorial, it is likely that you setup your module testing using rspec-puppet-init. For the first to be true, we create an empty site. If still didn't work then it could be an issue.

Could you please check? Sorry, something went wrong. The issue is specific to request specs. JonRowe we're actually upgrading this week, coincidentally. I was just trying to give another datapoint as it seems this problem may have been around for a long time. I re-ran it inside a docker container to make sure no configuration was influencing it and got the same result:.

I get exactly the same symptoms with MiniTest. For what it's worth, in case this is blocking people, passing an absolute path does work:. Also, it's probably obvious to everybody else, but you have to explicitly put it under the params key, you can't path it through the path duh :. I submitted a PR about that I did the same than ericproulx and works! Then it loads an image file. I have debugged this issue with breakpoints everywhere and I just don't understand why it's not working in test when it works in production.

I hope I've provided enough information this bug has been driving me crazy for the past two days. Thank you! Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Asked 3 months ago.

Active 3 months ago. Viewed 74 times. I recently ran into an issue with an integration test using rspec.