Kyiv Hackathon Winners: API Test Automation Based Upon Playwright

Meet Kostiantyn Serediuk, winner of the Hard Worker award.

Kyiv Hackathon Winners: API Test Automation Based Upon Playwright

You've had a chance to meet our Hackathon winners from the US and Australia. Now, we're traveling to another continent to introduce you to the winners from our Kyiv office.

Related Articles: Meet Our Hackathon Winners

Today, you'll meet Kostiantyn Serediuk, winner of the Hard Worker Award. Kostiantyn's project revolved around implementing API test automation based upon Playwright.

Before we discuss this project with Kostiantyn, let's take a moment to learn a little more about him.

Meet Kostiantyn

Software Development Engineer in Test II on the Localization Durable Team

Background: I joined BigCommerce four years ago as a member of the Translation Team that has transformed into the Localization Team. We are responsible not only for translations, but also for the store localization settings, shopper and merchant-facing emails, geo service, and more. 

Fun fact: I love hiking in the mountains, but I tried it for the first time only several years ago.

Connect with Kostiantyn on LinkedIn.

Kostiantyn's Project

Please describe your project.

The goal of the project was to implement API test automation based upon Playwright, which is an open-source, flexible and progressive framework, and to check how it could be applied to our scopes.

What inspired you to choose this project?

My main responsibility as a Quality Specialist is to check and ensure that everything is working expectedly within development and improvement of the platform. Because of this, there are a lot of testing tasks that are repeated from release to release, in particular, API functionality.

Which pain points does your project solve?

Some of the testing tasks mentioned above are solved manually on a regular basis. It is wonderful to have a system functionality that performs checks automatically. It will contribute to the solution of two typical pain points: high testing costs and developer downtime. Developers can just run auto test suite(s) by themselves. As a bonus, this will free up time to work on other equally important but more interesting tasks.

What’s your favorite part of this project? Why is it your favorite?

My favorite part was when implementation ran successfully for the first time. I believe that everyone is happy when something created from scratch starts working. It is a basis for the next steps of development and scaling up the project.

Which challenges did you face while you were developing your project?

The main challenge for me was that I did not have enough experience with API tests based upon the Playwright framework before starting the project. That's why I had to spend time and effort working and studying at the same time. 

How did you overcome these challenges?

Fortunately, my experienced colleagues and teammates helped me. Using this chance, I would like to say, "Many thanks" to them once again.

One more helpful thing was the clear documentation of the framework.

Open Roles: Explore Your Next Engineering Opportunity

What’s the one thing you’d change about this project?

If I had a chance, I would spend more time carefully planning the project to make it more flexible and universal. This would allow the implemented idea to be used in other scopes of our domain.

If an engineer wanted to create a project similar to yours, what advice would you give that person?

I suggest collaborating with others already involved and to take a look at ready-made solutions on the platform. It's possible that some of them are connected to a new idea/project and are ready to use.

What advice would you give to an engineer who is about to participate in a Hackathon?

Please double check if you have the right experience and competencies. Think about future efforts.

And remember, absence of knowledge is not a blocker — where there is a will, there is a way.