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:
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:
The test1.html file is opened but looks like this:
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).
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?
We are using the latest pretty_face from github (https://github.com/cheezy/pretty_face).
Our rake file has a simple task as follows:
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:
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:
The test1.html file is opened but looks like this:
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).
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?