<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body>A new request with request id 11649 has been created by koha-devel-request@lists.koha-community.org. Short info on the request is : <br><br>Title : Koha-devel Digest, Vol 196, Issue 17<br>Category : <br>Description : <div>Send Koha-devel mailing list submissions to<br> koha-devel@lists.koha-community.org<br><br>To subscribe or unsubscribe via the World Wide Web, visit<br> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>or, via email, send a message with subject or body 'help' to<br> koha-devel-request@lists.koha-community.org<br><br>You can reach the person managing the list at<br> koha-devel-owner@lists.koha-community.org<br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of Koha-devel digest..."<br><br><br>Today's Topics:<br><br> 1. Re: I played with Cypress (and ERM and Vue)<br> (Victor Grousset/tuxayo)<br> 2. Re: I played with Cypress (and ERM and Vue) (Jonathan Druart)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Wed, 23 Mar 2022 02:58:04 +0100<br>From: Victor Grousset/tuxayo <victor@tuxayo.net><br>To: 'Jonathan Druart' <jonathan.druart@bugs.koha-community.org><br>Cc: 'koha-devel' <koha-devel@lists.koha-community.org><br>Subject: Re: [Koha-devel] I played with Cypress (and ERM and Vue)<br>Message-ID: <9fdac965-cf66-b759-2c99-4f435f95744f@tuxayo.net><br>Content-Type: text/plain; charset=UTF-8; format=flowed<br><br>Hi :)<br><br>Nice to hear that. How was coding UI tests compared to Selenium?<br>And the API tests compared to the current way?<br>It's good that Cypress provides an alternative to both.<br><br>The Cypress section of this comparison with Puppeteer, Selenium, and <br>Playwright was not impressive compared to Puppeteer and Playwright.<br>https://www.testim.io/blog/puppeteer-selenium-playwright-cypress-how-to-choose/<br><br>And it seems some parts of Koha (with pop up windows) wouldn't be <br>testable with Cypress :o<br>https://docs.cypress.io/guides/references/trade-offs#Multiple-tabs<br>and I think the workaround wouldn't work for us since our pop ups are <br>used to fill a field in the calling window: <br>https://github.com/cypress-io/cypress-example-recipes/tree/master/examples/testing-dom__tab-handling-links<br><br>Also about iframes, with Firefox, Cypress can't at all interact inside <br>them. Could that be an issue if one day we want to use Cypress in Koha? <br>Given that Koha has a few minor iframes.<br><br>But it's the only Selenium alternative in the 3 to have a community <br>development. As opposed to Puppeteer and Playwright being developed >95% <br>by Google and Microsoft respectively. So who knows if one of the two has <br>so much success that Google or Microsoft drops their efforts on <br>maintaining the other one. Or one looses traction. It's not the first <br>time they would drop support to a project[1] and Firefox support should <br>be expected to always be precarious. (it's still experimental for Puppeteer)<br>On the other hand it's libre/open source so we can hope on the long term <br>there will always be a community to do the minimal maintenance. Hard to <br>say about Firefox support though.<br><br>[1] There is some dev stuff the following lists. Not enough to be <br>certain of the risks. (So I'm might be spreading FUD due to GAFAM <br>allergy) But enough to be wary about projects whose top committers are <br>from a single company. Which totally have the right to change their <br>priorities, no issues with that.<br>https://killedbygoogle.com/<br>https://killedbymicrosoft.info/<br><br><br>Cheers,<br><br>-- <br>Victor Grousset/tuxayo<br><br><br>------------------------------<br><br>Message: 2<br>Date: Wed, 23 Mar 2022 10:46:41 +0100<br>From: Jonathan Druart <jonathan.druart@bugs.koha-community.org><br>To: "Victor Grousset/tuxayo" <victor@tuxayo.net><br>Cc: koha-devel <koha-devel@lists.koha-community.org><br>Subject: Re: [Koha-devel] I played with Cypress (and ERM and Vue)<br>Message-ID:<br> <CAJzKNY6qyqM13aqR0Fj2NHw3ZUkJXur7zEduS3_DF1jtTfFarg@mail.gmail.com><br>Content-Type: text/plain; charset="UTF-8"<br><br>> Nice to hear that. How was coding UI tests compared to Selenium?<br><br>It's easier to write and easier to debug (given the screenshot and the<br>ability to inspect the DOM after each test).<br><br>> And the API tests compared to the current way?<br><br>Please have a look at the patch, or at least the very succinct commit<br>messages "We are mocking the REST API routes responses", so they are<br>not tested with Cypress in this patch. If we are not mocking the<br>routes, they won't replace the existing tests as it will become<br>end-to-end integration tests. Both will be useful.<br><br>> ... was not impressive compared to Puppeteer and Playwright.<br><br>Yes, there is always another alternative, but no code to show me the comparison.<br><br>> I think the workaround wouldn't work for us since our pop up are<br>> used to fill a field in the calling window<br><br>Yes, I know, there is a TODO in the code. I was planning to have a<br>modal instead, which would be nice, but that was too many changes.<br>If it's the only problem, it should not block us from choosing<br>Cypress. We don't have many pop-ups, and I don't think we are already<br>testing them anyway.<br><br>Le mer. 23 mars 2022 à 02:58, Victor Grousset/tuxayo<br><victor@tuxayo.net> a écrit :<br>><br>> Hi :)<br>><br>> Nice to hear that. How was coding UI tests compared to Selenium?<br>> And the API tests compared to the current way?<br>> It's good that Cypress provides an alternative to both.<br>><br>> The Cypress section of this comparison with Puppeteer, Selenium, and<br>> Playwright was not impressive compared to Puppeteer and Playwright.<br>> https://www.testim.io/blog/puppeteer-selenium-playwright-cypress-how-to-choose/<br>><br>> And it seems some parts of Koha (with pop up windows) wouldn't be<br>> testable with Cypress :o<br>> https://docs.cypress.io/guides/references/trade-offs#Multiple-tabs<br>> and I think the workaround wouldn't work for us since our pop ups are<br>> used to fill a field in the calling window:<br>> https://github.com/cypress-io/cypress-example-recipes/tree/master/examples/testing-dom__tab-handling-links<br>><br>> Also about iframes, with Firefox, Cypress can't at all interact inside<br>> them. Could that be an issue if one day we want to use Cypress in Koha?<br>> Given that Koha has a few minor iframes.<br>><br>> But it's the only Selenium alternative in the 3 to have a community<br>> development. As opposed to Puppeteer and Playwright being developed >95%<br>> by Google and Microsoft respectively. So who knows if one of the two has<br>> so much success that Google or Microsoft drops their efforts on<br>> maintaining the other one. Or one looses traction. It's not the first<br>> time they would drop support to a project[1] and Firefox support should<br>> be expected to always be precarious. (it's still experimental for Puppeteer)<br>> On the other hand it's libre/open source so we can hope on the long term<br>> there will always be a community to do the minimal maintenance. Hard to<br>> say about Firefox support though.<br>><br>> [1] There is some dev stuff the following lists. Not enough to be<br>> certain of the risks. (So I'm might be spreading FUD due to GAFAM<br>> allergy) But enough to be wary about projects whose top committers are<br>> from a single company. Which totally have the right to change their<br>> priorities, no issues with that.<br>> https://killedbygoogle.com/<br>> https://killedbymicrosoft.info/<br>><br>><br>> Cheers,<br>><br>> --<br>> Victor Grousset/tuxayo<br><br><br>------------------------------<br><br>Subject: Digest Footer<br><br>_______________________________________________<br>Koha-devel mailing list<br>Koha-devel@lists.koha-community.org<br>https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>website : https://www.koha-community.org/<br>git : https://git.koha-community.org/<br>bugs : https://bugs.koha-community.org/<br><br><br>------------------------------<br><br>End of Koha-devel Digest, Vol 196, Issue 17<br>*******************************************<br></div><br><br>NOTE: You are receiving this mail because, the Requester/Technician wanted you to get notified on this request creation.<br></body></html>