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

openReportInBrowser: true does not open report in browser #5

Closed
FlippieCoetser opened this issue Jul 23, 2018 · 6 comments
Closed

openReportInBrowser: true does not open report in browser #5

FlippieCoetser opened this issue Jul 23, 2018 · 6 comments
Assignees
Labels
bug Something isn't working Fix with PR

Comments

@FlippieCoetser
Copy link

Actual:
Background:
Given openReportInBrowser is set to true in wdio.conf.js

Scenario:
When I run all cucumber tests
And a report is produced
Then the report is not opened in the browser

Expected:
Background:
Given openReportInBrowser is set to true in wdio.conf.js

Scenario:
When I run all cucumber tests
And a report is produced
Then the report should open in the browser

Platform: Windows 10

@FlippieCoetser
Copy link
Author

@wswebcreation it looks like more of the settings applied in the wdio.conf.js does not work. metaData fails. pageTitle, reportName and displayDuration succeeds.

@wswebcreation
Copy link
Owner

Tnx for checking, I was to excited to release that I didn't gave myself time to create proper testcases.

I'll dive into it an fix it a.s.a.p., unless you want to add a PR ;-)

@wswebcreation wswebcreation added the bug Something isn't working label Jul 23, 2018
@wswebcreation wswebcreation self-assigned this Jul 23, 2018
@wswebcreation
Copy link
Owner

🤔

    reporterOptions: {
        htmlReporter: {
            jsonFolder: '.tmp/new/',
            reportFolder: '.tmp/multiple-cucumber-html-reporter/',
            displayDuration: true,
            openReportInBrowser: true,
            saveCollectedJSON: true,
            disableLog: true,
            pageTitle: 'pageTitle',
            reportName: 'reportName',
            pageFooter: '<div><h1>Custom footer</h1></div>',
            customData: {
                title: 'Run info',
                data: [
                    {label: 'Project', value: 'Custom project'},
                    {label: 'Release', value: '1.2.3'},
                    {label: 'Cycle', value: 'B11221.34321'},
                    {label: 'Execution Start Time', value: 'Nov 19th 2017, 02:31 PM EST'},
                    {label: 'Execution End Time', value: 'Nov 19th 2017, 02:56 PM EST'}
                ]
            }
        }
    },

Results in opening the browser and creating this report

image

The only thing I now see that doesn't work is metadata. Is there more that doesn't work?

@FlippieCoetser
Copy link
Author

Metadata was the only other setting that did not work. I will do more testing and when I find something I will open a new ticket. Soon I will also have a Dev environment ready then I can help with PR.

@wswebcreation
Copy link
Owner

Ok, tnx, I think I need to remove the metadata options because all gets defaulted by this module already. Will check it later this week

@wswebcreation
Copy link
Owner

I've removed the metadata and released a new version. All options should now be working. I'm going to close it for now. If you see an other issue please let me know

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Fix with PR
Projects
None yet
Development

No branches or pull requests

2 participants