Monitoring via playwright tests #3371

Open
opened 2026-02-28 03:27:14 -05:00 by deekerman · 15 comments
Owner

Originally created by @kaystrobach on GitHub (May 30, 2024).

🏷️ Feature Request Type

New monitor

🔖 Feature description

As a user i want to run playwright tests with kuma in order to check more complex szenarios.

this is also available in other monitoring solutions:

✔️ Solution

In browser playwright tests. It’s ok, to copy them in a textarea, the best solution would be to connect a git repo to get the tests.

Alternatives

None, without switching products or having a middleware to run tests.

📝 Additional Context

No response

Originally created by @kaystrobach on GitHub (May 30, 2024). ### 📑 I have found these related issues/pull requests - https://github.com/louislam/uptime-kuma/issues/3056 ### 🏷️ Feature Request Type New monitor ### 🔖 Feature description As a user i want to run playwright tests with kuma in order to check more complex szenarios. this is also available in other monitoring solutions: * https://x.com/shakalandy/status/1701112612170223709?s=46&t=U8zjU-fWbJNNX4kMhADeBA * https://x.com/betterstackhq/status/1762496057148158211?s=46&t=U8zjU-fWbJNNX4kMhADeBA ### ✔️ Solution In browser playwright tests. It’s ok, to copy them in a textarea, the best solution would be to connect a git repo to get the tests. ### ❓ Alternatives None, without switching products or having a middleware to run tests. ### 📝 Additional Context _No response_
Author
Owner

@CommanderStorm commented on GitHub (May 30, 2024):

I think what you are asking about (especially given the asked git integration) is likely better served by a CI-piepeline

@CommanderStorm commented on GitHub (May 30, 2024): I think what you are asking about (especially given the asked git integration) is likely better served by a CI-piepeline
Author
Owner

@kaystrobach commented on GitHub (May 30, 2024):

Agree. Git is completely optional. Main use case is very simple tests, like login to idm, open service.

The ci pipeline runs anyway. But can not run every minute etc.

other uptime checkers start to integrate these simple test case implementations to have better insights.

@kaystrobach commented on GitHub (May 30, 2024): Agree. Git is completely optional. Main use case is very simple tests, like login to idm, open service. The ci pipeline runs anyway. But can not run every minute etc. other uptime checkers start to integrate these simple test case implementations to have better insights.
Author
Owner

@kaystrobach commented on GitHub (Jun 3, 2024):

related #3056

@kaystrobach commented on GitHub (Jun 3, 2024): related #3056
Author
Owner

@kaystrobach commented on GitHub (Jun 3, 2024):

If it helps i can create a short video showing the use case. Please just tell me. Thanks

@kaystrobach commented on GitHub (Jun 3, 2024): If it helps i can create a short video showing the use case. Please just tell me. Thanks
Author
Owner

@kaystrobach commented on GitHub (Jun 3, 2024):

Other similar tools implementing playwright:

@kaystrobach commented on GitHub (Jun 3, 2024): Other similar tools implementing playwright: * https://betterstack.com/docs/uptime/playwright-monitor/ * https://www.checklyhq.com/product/start-monitoring-with-playwright/
Author
Owner

@techmattr commented on GitHub (Jun 11, 2024):

I too would love to see more complex checks available. I mentioned this on Reddit and was advised it was being tracked here. Currently Uptime Kuma has very limited use cases for me as all it can do is make sure my login pages are available. If Uptime Kuma had a way to log into these sites it could validate the site is actually working. The playwright integration changedetection.io is done amazingly well and a similar feature would add so much value to Uptime Kuma.

@techmattr commented on GitHub (Jun 11, 2024): I too would love to see more complex checks available. I mentioned this on Reddit and was advised it was being tracked here. Currently Uptime Kuma has very limited use cases for me as all it can do is make sure my login pages are available. If Uptime Kuma had a way to log into these sites it could validate the site is actually working. The [playwright integration changedetection.io](https://i.imgur.com/IsmK1hJ.png) is done amazingly well and a similar feature would add so much value to Uptime Kuma.
Author
Owner

@kaystrobach commented on GitHub (Jun 11, 2024):

@louislam I have a developer set on that topic, if that is interesting for you, he can build the whole PoC and finalize it in the next weeks. Would be a thank you from the https://github.com/fucodo/ and https://github.com/4viewture/ team

@kaystrobach commented on GitHub (Jun 11, 2024): @louislam I have a developer set on that topic, if that is interesting for you, he can build the whole PoC and finalize it in the next weeks. Would be a thank you from the https://github.com/fucodo/ and https://github.com/4viewture/ team
Author
Owner

@pilulu commented on GitHub (Jul 7, 2024):

Hi,

I'm really interested in a feature like this in order to monitor small things that need a javascript.
I agree that a complex process like logging or loading multiple pages is more adapted on a CI process.
I my use case i would only be sure that all few elements on a page that need javascript rendering are loaded properly.

If it's not a git repo, i expect at least a small textarea to evaluate short playwright scenarios from probe configuration page.

@pilulu commented on GitHub (Jul 7, 2024): Hi, I'm really interested in a feature like this in order to monitor small things that need a javascript. I agree that a complex process like logging or loading multiple pages is more adapted on a CI process. I my use case i would only be sure that all few elements on a page that need javascript rendering are loaded properly. If it's not a git repo, i expect at least a small textarea to evaluate short playwright scenarios from probe configuration page.
Author
Owner

@kaystrobach commented on GitHub (Aug 6, 2024):

@louislam once I have the commitment, that this would get integrated, if implemented well, I would set a dev on that task in the next weeks, maybe for v2+?

@kaystrobach commented on GitHub (Aug 6, 2024): @louislam once I have the commitment, that this would get integrated, if implemented well, I would set a dev on that task in the next weeks, maybe for v2+?
Author
Owner

@eitchugo commented on GitHub (Sep 23, 2025):

Hi folks! I'm also interested in this, using the uptime-kuma UI to handle a user journey test on a site is much better and user-friendly than using on CI and having to setup cronjobs, etc.

Is there any plans to continue this issue? Or maybe you need any more help?

@eitchugo commented on GitHub (Sep 23, 2025): Hi folks! I'm also interested in this, using the uptime-kuma UI to handle a user journey test on a site is much better and user-friendly than using on CI and having to setup cronjobs, etc. Is there any plans to continue this issue? Or maybe you need any more help?
Author
Owner

@morla10111 commented on GitHub (Nov 19, 2025):

Me too would love to see this feature implemented.

@morla10111 commented on GitHub (Nov 19, 2025): Me too would love to see this feature implemented.
Author
Owner

@mabed-fr commented on GitHub (Nov 20, 2025):

I find this request interesting for creating robust tests.

In my case, it would be, for example, to add a product to the cart and open the cart. At first, we could limit the scenarios to 30 seconds.

What is the opinion of the managers and contributors on this feature, which is appearing in many monitoring software?

Considering that today it is very easy to record directly from the browser, we would not need an Iptime Kuma window.

@mabed-fr commented on GitHub (Nov 20, 2025): I find this request interesting for creating robust tests. In my case, it would be, for example, to add a product to the cart and open the cart. At first, we could limit the scenarios to 30 seconds. What is the opinion of the managers and contributors on this feature, which is appearing in many monitoring software? Considering that today it is very easy to record directly from the browser, we would not need an Iptime Kuma window.
Author
Owner

@kaystrobach commented on GitHub (Nov 20, 2025):

totally agree, should be used for short stories only. otherwise we can use external hooks now. with the new hooks, we are using gitlab ci to keep the state up to date

@kaystrobach commented on GitHub (Nov 20, 2025): totally agree, should be used for short stories only. otherwise we can use external hooks now. with the new hooks, we are using gitlab ci to keep the state up to date
Author
Owner

@sule26 commented on GitHub (Dec 30, 2025):

+1

@sule26 commented on GitHub (Dec 30, 2025): +1
Author
Owner

@olivernz commented on GitHub (Feb 4, 2026):

Did this end up going anywhere? Was just about to raise a feature request.

@olivernz commented on GitHub (Feb 4, 2026): Did this end up going anywhere? Was just about to raise a feature request.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/uptime-kuma#3371
No description provided.