Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pretty_face feature html unable to reference stock images (passed failed, etc) #48

Open
taji opened this issue Feb 9, 2016 · 3 comments

Comments

@taji
Copy link

taji commented Feb 9, 2016

We are using the latest pretty_face from github (https://github.com/cheezy/pretty_face).

Our rake file has a simple task as follows:

namespace :test_rake_results do
  Cucumber::Rake::Task.new(:test_c) do |task|
    task.cucumber_opts = "--format PrettyFace::Formatter::Html --out index.html"
  end
end

task :demo_c => ['test_rake_results:test_c']

When we execute the task, the index.html file is created in the root of the project as expected. Also, the test1.html file is created in the feature folder alongside the original test1.feature file:

image

When opened in a browser, the index.html file looks as expected. The passed, failed, etc images appear. However, when we click on a feature link at the bottom of the page as so:

image

The test1.html file is opened but looks like this:

image

Looking at the source of the test1.html file, we are seeing that the links to the images are referenced from the location of the test1.html file itself rather than from the location of the index.html file (one folder up).

image

Also, from the test1.html file the back button is not linking to the index.html file as expected. This is the same issue.

Is this a bug, or is there a configuration option or setup approach we are missing?

@dmorgan3405
Copy link

Hey @taji, it looks like this is a bug.

Are you running test on a windows box?

@taji
Copy link
Author

taji commented Mar 1, 2016

Yes, right now windows 8.1

@taji
Copy link
Author

taji commented Apr 6, 2016

Just a note for Cheezy Morgan: We pulled down the latest from the main branch on the github project site and were able to reproduce the problem. Can you provide a timeline as to when this issue will be addressed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants