Automating My Notepad API with Playwright for Java

Recently I decided to automate my Notepad REST API using Playwright for Java.

Normally, for API testing projects, I mostly used REST Assured. Since REST Assured is very popular in Java API automation, it was the tool I was most comfortable with.

This time, I wanted to try something different and see how Playwright performs for API testing.

The main reason I chose Playwright was because I liked the idea of using a single framework for both API and UI automation in the future instead of separating everything into different tools.

The project currently covers 53 API test cases including CRUD operations, negative scenarios, pagination testing, boundary validations, and end-to-end note lifecycle flows.

For the tech stack, I used: - Playwright for Java - JUnit 5 - AssertJ - Jackson - Maven - Allure Reports

One thing I noticed while working on this project is that Playwright API testing feels much cleaner and simpler than I expected.

Coming from REST Assured, I initially thought I would miss some flexibility, but Playwright’s request handling and response validation actually felt very straightforward.

I also liked how naturally the framework can later expand into UI automation without changing the ecosystem completely.

This project helped me improve both my API testing mindset and backend understanding at the same time.

As I continue learning backend development and automation, I enjoy trying different tools and understanding their strengths instead of limiting myself to only one framework.