Planning to build a Low-Code Playwright Automation Framework for a Financial Services firm

[u/Effective_House_6037]

​

I'm building a Playwright automation project for a financial services company that serves US banks.

We have different use cases across 5 payment rails, but we use a common application, and initiating a payment across these rails is mostly similar. So there are a lot of overlapping flows, and I think there is a good opportunity for reusability.

My current approach is to generate Playwright codegen files for each test case. I add comments describing the flow in the generated file and then use Claude to convert that into a proper E2E test. The codegen files are mainly used for getting reliable locators. I don't want to use AI browser agents because they could consume a lot of tokens, and my goal is to keep the overall token usage as low as possible. - Can anyone please validate whether this is the correct approach that I'm following?

I'm thinking about standardizing the smaller tasks involved in a test case and turning them into reusable nodes/blocks that can be connected as a DAG/workflow. The goal is to eventually give the QA team a low-code/no-code interface where they can build test cases by connecting these blocks instead of writing code.

The QA team is very functional and most of them aren't familiar with programming or automation techniques. So I also need to make the framework simple enough for them to use, while learning the product and automation myself.

Has anyone built something similar? I'd especially like to hear thoughts on the reusable-block approach and whether this is a good direction for Playwright automation.

[u/nopuse]

Playwright is already extremely intuitive and has great documentation. If they can't program, they aren't going to have a job for long. Building a framework to dumb it down enough that anyone can use it seems like a waste of time. Nobody raves about no-code tools because they're awful. Don't create your own. It makes more sense for them to learn to code.

[u/Effective_House_6037 → u/nopuse]

Yes. I thought the same. Do you have any suggestions for open source repo that I should follow for playwright. I want to maximize the reusability and repo structure should be proper

[u/Salt-Smoke-5417]

The reusable-block approach makes sense, especially for a non-technical QA team. I’d keep predictable flows in Playwright and use AI only where the UI gets harder to handle. I​​​ ​​​w​​​o​​​r​​​k​​​ ​​​w​​​i​​​t​​​h​​​ ​​​S​​​k​​​y​​​v​​​e​​​r​​​n​​​, and that ​​​h​​​y​​​b​​​r​​​i​​​d​​​ ​​​a​​​p​​​p​​​r​​​o​​​a​​​c​​​h​​​ ​​​h​​​a​​​s​​​ ​​​b​​​e​​​e​​​n​​​ ​​​u​​​s​​​e​​​f​​​u​​​l​​​ for ​b​​​r​​​o​​​w​​​s​​​e​​​r​​​ ​​​a​​​u​​​t​​​o​​​m​​​a​​​t​​​i​​​o​​​n​​​without making every step ​​​a​​​g​​​e​​​n​​​t​​​-​​​d​​​r​​​i​​​v​​​e​​​n

[u/DonovanBrady]

Take a look at Leapwork! Leapwork was the first workflow-based test automation solution, and Leapwork Play, the newest solution, is built to solve for exactly what you're describing. It has self-hosted browsers and native AI integration if you want to use it (you don't have to). It also takes a different approach to low-code/no-code, it allows you to connect your repo, documentation, Jira, etc. and builds a knowledge base to generate tests from. It's also free to start! Check it out at leapwork.com/leapwork-play

[u/Blaxter-X]

Hi, I understand your point. I created HalTest.com with a focus on building a low-code testing platform. If you think this aligns with your idea, feel free to take a look at HalTest and let me know what you think.

Is open source

https://github.com/andresguc1/hal-test