[00:02:20]
<H3rb3rt> Merci
[00:49:11]
<m606> > Playwright also has an add-on to record such interactions and auto-generate tests. With curl, I would need to peek much lower in the stack to know the exact endpoints, API format, field names, etc.
The add-on thing looks tempting indeed. But regarding curl, rather than diving a lot in the code base, you may just need to log in via a browser and check dev tools network tab to identify the API request and associated fields right away.
> Both approaches (curl and e2e) are valid and complimentary.
I understand your point on the visual flow (even though this could be improved on the curl implementation side if extending the list curl helpers to manage the main user flows you are referring to), but don't really get the one about complimentary. Spontaneously, it looks to me that they can both do the job of the other (with the Playwright codebase being much bigger and advanced probably), and that having both would just add up maintenance work.
[07:48:54]
<Yunohost Git/Infra notifications> [apps] Thovi98 merged [pull request #3684](https://github.com/YunoHost/apps/pull/3684) : Add Reactive Resume
[07:49:02]
<Yunohost Git/Infra notifications> [apps] Thovi98 pushed to main: Add Reactive Resume (#3684) Claude-Session: https://claude.ai/code/session_016CfRR2wt4eRsEZgEXALeQ3 Co-authored-by: He... ([3ca63bb4](https://github.com/YunoHost/apps/commit/3ca63bb42be9370f3c25876b77cfd49f40699c34))
[08:22:51]
<Yunohost Git/Infra notifications> [apps] yunohost-bot opened [pull request #3686](https://github.com/YunoHost/apps/pull/3686) : Add NextPad to wishlist
[09:37:29]
<sitegui> To clarify, when I say they are complimentary:
Playwright automates a headless browser. So naturally if the app has no web pages, playwright cannot be used, and curl will probably be more adequate. Say we're testing some app that exposes its services with FTP.
Curl connects lower in the stack and tests one endpoint in isolation. So naturally, to test user flows playwright will probably be more adequate.
[09:39:55]
<sitegui> For example in Nextcloud today, its [tests.toml](https://github.com/YunoHost-Apps/nextcloud_ynh/blob/master/tests.toml) today do not test any flow that writes data (say a file upload).
Immich do not have any test.
I'd like to contribute a simple flow test to both. While curl and playwright could be used, I have an intuition (and it's just an intuition 😄) that maintaining the test at the level of the UI instead of the endpoints will be less burdensome.
[09:43:32]
<doesnm> silly question: did all new apps are flagged as broken initially?
[09:43:33]
<orhtej2> > <@doesnm:doesnmlab.xyz> silly question: did all new apps are flagged as broken initially?
Yes, the status is updated every friday via automated pt
[09:43:33]
<orhtej2> pr
[09:43:33]
<Yunohost Git/Infra notifications> [joplin_ynh] orhtej2 merged [pull request #139](https://github.com/YunoHost-Apps/joplin_ynh/pull/139) : Upgrade to v3.7.22
[09:43:34]
<Yunohost Git/Infra notifications> [joplin_ynh] orhtej2 deleted branch ci-auto-update-3.7.22
[09:43:44]
<Yunohost Git/Infra notifications> [joplin_ynh] orhtej2 opened [pull request #140](https://github.com/YunoHost-Apps/joplin_ynh/pull/140) : Testing
[09:43:50]
<Yunohost Git/Infra notifications> [joplin_ynh] orhtej2 merged [pull request #140](https://github.com/YunoHost-Apps/joplin_ynh/pull/140) : Testing
[09:46:23]
<Thomas> > Yes, the status is updated every friday via automated pt
But the main ci is broken right now so I don't think that today's pr will be useful
[15:33:19]
<orhtej2> > <@doesnm:doesnmlab.xyz> do you need backup resources? If your CI can Proxmox instead of Incus i may provide my homelab
It's broken on code not infra level
[15:33:20]
<orhtej2> https://ci-apps.yunohost.org/ci/
[15:33:20]
<doesnm> sure
[15:33:20]
<doesnm> do you need backup resources? If your CI can Proxmox instead of Incus i may provide my homelab
[16:03:26]
<Yunohost Git/Infra notifications> [apps] yunohost-bot opened [pull request #3687](https://github.com/YunoHost/apps/pull/3687) : Update app levels according to CI results
[17:30:24]
<m606> hmm do you think that for the example you mention (test for file upload in Nextcloud) the following could be enough, or headless browser would check things than curl cannot check? https://help.nextcloud.com/t/how-to-upload-a-file-to-your-nextcloud-using-curl/94358/9
[18:39:03]
<Yunohost Git/Infra notifications> [apps] yunohost-bot opened [pull request #3688](https://github.com/YunoHost/apps/pull/3688) : Add writefreelywisp to wishlist
[23:30:17]
<quartz> Have been working on a few packages and was invited by CodeShakingSheep to ask to join the YunoHost-Apps organization so I can get them transferred and officially tested. Would someone be able to help with access?
[23:30:17]
<quartz> Food
[23:30:17]
<quartz> 🍲
[23:30:17]
<quartz> https://github.com/quartztester/opengym_ynh/issues/1
[23:30:17]
<orhtej2> > Have been working on a few packages and was invited by CodeShakingSheep to ask to join the YunoHost-Apps organization so I can get them transferred and officially tested. Would someone be able to help with access?
Open a PR akin [this one](https://github.com/YunoHost/apps/pull/3684) and we can take it from there
[23:30:18]
<Yunohost Git/Infra notifications> [ntfy_ynh] yunohost-bot opened [pull request #120](https://github.com/YunoHost-Apps/ntfy_ynh/pull/120) : Upgrade to v2.35.0
[23:45:57]
<Yunohost Git/Infra notifications> Autoupdater just ran, here are the results:
- 81 pending update PRs
- 26 new apps PRs: borgwarehouse, civicrm_drupal, davis, diagramsnet, directorylister, findmydevice, gitea-mirror, grav, headscale, homarr, invoiceninja5, jackett, leantime, mstream, n8n, nodebb, ntfy, piefed, qui, reactive-resume, rutorrent, snweb, sparkyfitness, tooljet, vvveb, wekan
- 9 failed apps updates: automad, benevalibre, digiscreen, galette, gamja, loki, lxd, projectsend, snappymail
See the full log here: https://paste.yunohost.org/raw/odegarogik
Autoupdate dashboard: https://apps.yunohost.org/dash?filter=autoupdate