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

Ktor server and client listeners #80

Open
1 of 3 tasks
jmflaherty opened this issue May 21, 2023 · 0 comments
Open
1 of 3 tasks

Ktor server and client listeners #80

jmflaherty opened this issue May 21, 2023 · 0 comments

Comments

@jmflaherty
Copy link

I'm submitting a ...

  • bug report
  • feature request
  • support request => Please do not submit support request here, see note at the top of this template.

What is the current behavior?

Allure only reports stacktrace errors and failed assertions by not having a listener to plug into either Ktor server or client.

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

n/a

What is the expected behavior?

Having Ktor plug-ins for both server and client to log traffic and embed it into reports generated by Allure.

What is the motivation / use case for changing the behavior?

Tools like Rest Assured are OK for simpler projects, but they lack flexibility and performance. As an alternative, OkHttp and Retrofit are used. But Ktor is increasingly popular as the default Kotlin way of handling network traffic, providing an even better development experience, maintainability, and performance.

The only thing keeping Ktor from being a useful testing tool is the lack of integration with a reporter.

Please tell us about your environment:

Allure version 2.22.0
Test framework [email protected] and [email protected]
Allure integration [email protected]
Generate report using [email protected]

Other information

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

1 participant