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

[📖 Docs]: Mocha third party UIs #12843

Open
2 tasks done
ethanyou725 opened this issue May 8, 2024 · 6 comments
Open
2 tasks done

[📖 Docs]: Mocha third party UIs #12843

ethanyou725 opened this issue May 8, 2024 · 6 comments
Labels
Bug 🐛 help wanted Issues that are free to take by anyone interested

Comments

@ethanyou725
Copy link

Pre-check

  • I know I can edit the docs but prefer to file this issue

Describe the improvement

Unclear documentation

Description of the improvement / report

Thanks for this awesome project.
As I know, mocha could support third party UIs , and webdriverIO could have mocha integration, but could we define third party UI with webdriverio mocha framework? I read the docs https://webdriver.io/docs/frameworks/#using-mocha and https://github.com/webdriverio/webdriverio/tree/main/packages/wdio-mocha-framework#readme, but still very unclear about it.

Code of Conduct

  • I agree to follow this project's Code of Conduct
@ethanyou725 ethanyou725 added Docs 📖 Needs Triaging ⏳ No one has looked into the issue yet labels May 8, 2024
@christian-bromann
Copy link
Member

@ethanyou725 can you elaborate on why you are interested to use a 3rd party UI for Mocha?

@christian-bromann christian-bromann added Information Missing and removed Needs Triaging ⏳ No one has looked into the issue yet labels May 8, 2024
@ethanyou725
Copy link
Author

ethanyou725 commented May 9, 2024

@ethanyou725 can you elaborate on why you are interested to use a 3rd party UI for Mocha?

Thanks for your kindly reply. Because we are migrating some exist test cases (*.spec.ts) to webdriverio.

e.g.
old case:

test('test case', async () => { 
    await step('1=1', async () => {
        await expect(1).toBe(1)
    })
})

in mocha without custom ui, bdd style it must use describe and it,
and with custom ui interface, we could have the ability not change the spec file.

@christian-bromann
Copy link
Member

Have you tried to set mochaOpts.ui to tdd?

@ethanyou725
Copy link
Author

Have you tried to set mochaOpts.ui to tdd?

yes, tdd provides different function suit, it could be more convenient if support custom ui.

@christian-bromann
Copy link
Member

Actually with qunit you can run tests like this but it seems that reporters don't pick up the right test data for the reporting. Any contributions to improve this behavior would be appreciated.

@christian-bromann christian-bromann added help wanted Issues that are free to take by anyone interested Bug 🐛 and removed Information Missing Docs 📖 labels May 9, 2024
@wdio-bot
Copy link
Contributor

wdio-bot commented May 9, 2024

Thanks for reporting!

We greatly appreciate any contributions that help resolve the bug. While we understand that active contributors have their own priorities, we kindly request your assistance if you rely on this bug being fixed. We encourage you to take a look at our contribution guidelines or join our friendly Discord development server, where you can ask any questions you may have. Thank you for your support, and cheers!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug 🐛 help wanted Issues that are free to take by anyone interested
Projects
None yet
Development

No branches or pull requests

3 participants