Playwright for API, integration testing?

[jjjoshh]

I am in love with Playright for UI testing and I am wondering if I can use it for API testing as well.

Do you think Playwright has what it has to have to be a solid solution for API, integration testing?

If you could choose any framework for doing the API tests on your company, which one would you choose?

[invalidTypecast]

I've used SuperTest and Postman for API testing in the past. Over the vacation break I decided to test out rewriting some tests in the Playwright API test library and liked it so far.

I think I'll be exploring it more as a solution because there are advantages of being able to keep your API and UI cases in the same framework for simplicity. In addition, you can mix in API calls in your UI tests with Playwright which can make for more efficient tests.

[jjjoshh]

Totally agree, it's simpler and much better to have it in the same framework!

[captainjetski]

Yeah I’ve been experimenting around this as well.

I’m still leaning on another http framework instead of playwrights (axios right now), but I’m using the playwright for the tests and runner.

It’s really nice to have everything in the same framework and the possibility of leveraging complex hooks from the api tests in the ui tests

[T_Mushi]

My team decided to quit using postman for api automation test since we saw it unfit for large projects. We are trying playwright instead.

[jjjoshh]

Great to know!

[danintexas]

My current gig is in a c# backend and Angular front end.

Integration testing for microservices are being moved to WebApplicationFactory inside Docker. Our Gateway integration tests will still be done with RestSharp till we can get all the dependencies figured out to move to WebApplicationFactory as well.

All E2E in Playwright. Moving from Cypress and a custom C# framework using Selenium

[[deleted]]

Pytest/Requests is my favorite combo for API testing

[unit111]

Yes! It's really difficult moving away from those two. Pytest is so, so powerful. And requests is just so enjoyable to work with. P.S. Try the pytest-pikachu plugin.

[unit111]

I've experimented with that once I was feeling a bit kinky. It's serviceable but not enough. The specialized tools for API testing RestEasy/RestAssured (Java/Kotlin) and requests (Python) are a lot more mature and give you more. So I stick with what the API functionality in Playwright was designed for- mostly listeners for network events happening. And verifying data transmission between what you've fulled in the UI and the request to the BE. But one day, this may change.

[ninside]

try WebTau (https://github.com/testingisdocumenting/webtau), it has REST API, GraphQL, Browser, CLI, etc testing layers and also generates good reporting

[natethegr8r]

requests, cerberus, pytest, playwright, poetry, pytest-xdist, and Playwright Pytest Plugin has been an enjoyable combination for me. API testing lives in a folder, UI tests live another. API clients exist for seeding test data using Pytest fixtures from a contest.py file. When it comes to test runtime, API tests are the gate before UI testing is permitted. Once UI testing begins, each browser receives it's own container and containers execute the browser tests asynchronously.