This page was machine-translated from Portuguese and may contain mistakes. Read the original
On September 26, 2023, I appeared on the Talking About Testing livestream alongside Walmyr Filho, answering questions about the “Code Battle: Cypress vs. Playwright” event that took place on July 22 as part of the Minas Testing Conference 2023.
Here’s the link to the livestream: YouTube @TalkingAboutTesting
Check out Part 1 of the conversation: https://testingwithrenata.com/portfolio/youtube-live-mtc-2023-parte-1/
Check out the answers about Playwright below:
8. (Amanda Silvaan) Which tool is best suited for testing on WhatsApp?
[Playwright] Renata: I don’t know how to answer that question.
9. I’d like to see the PW failure for Edge. Analyzing how it presents the failure is very important when developing automation.
[Playwright] Renata: I’ll show you 🙂
10. Does what’s being shown here (from Cypress) generate an exportable step-by-step execution report?
[Playwright] Renata: Reporting in Playwright is included by default, and you can customize it however you like without needing additional libraries.
11. For API-only testing, which tool is best suited? Cypress or Playwright?
[Playwright] Renata: Playwright offers very robust support for API testing. I’ve used it and really liked it. I have some slides comparing Playwright and TestCafé (with Axios): https://testingwithrenata.com/portfolio/tdc-innovation-devtest-2023/
And I have a module from the Advanced Playwright course on APIs: https://testautomationu.applitools.com/playwright-advanced/chapter3.html
12.Walmyr, this week there was a rumor going around that Cypress might shut down—is this fake, or is there any truth to it?
13. Is Cypress + Cucumber a good combination???
[Playwright] Renata: https://testingwithrenata.com/blog/test-automation/playwright-bdd-cucumber-e-a-minha-opiniao-sobre-isso/
14. Is Cypress going to die?
15. Do you believe that for the quality process to be effective, a “top-down” approach from company management is necessary?
Renata: In my opinion, it can play out in various ways. Often, management doesn’t understand quality well enough to guide the best strategies and practices. And eventually, they may end up hiring test leaders who aren’t very “good” either, since in their view, “if it works, that’s good enough.” It’s important for professionals, regardless of their level, to seek to educate their peers and leaders to improve the process as a whole. I worked on a team as a Test Leader and received several suggestions for process improvements and techniques that I hadn’t considered. Some I was able to implement, others I needed to take to higher-ups, and sometimes I got approval while other times I didn’t. In my opinion, adopting an efficient process generally takes about a year.
16. What tool do you use for automated testing?
Renata: On my last project, it was Playwright, and for the next one, I’m not sure yet because I still need to assess the team, the company’s needs, and any existing issues. If the current framework is meeting our needs and allowing the team to evolve quickly, I have no problem sticking with it.
17. How do you use Jira to track how many test cases have been created? And other fields for keeping a history of what’s been done?
Renata: For quite a while, I worked with a very informal test case process and on a team where I was the only one. For me[me julguem], Google Sheets worked fine—I’d list the test titles and some additional information, and I’d run the tests myself. No one cared how many test cases there were, and no one needed test reports. So I focused my time on testing and automation. After my team grew a bit, I started using the same document, though a bit more comprehensive, since it was based on an export from the format we used to break down the requirements, and my testing team consisted of senior testers (no one was concerned about the test results themselves anymore; we’d also reached a very high level of automation maturity by that point). On another project at a different company, where I joined late in the game, I used the same strategy (Google Sheets), but the developers who would be running the test cases needed a bit more data, so I created some simple charts to provide management with some visibility. At that time, we weren’t using Jira—we were using Asana—and Asana didn’t have any integration with test cases. We didn’t have time to evaluate a new tool or the budget to purchase one. It worked well for the developers. On a future project, I’d like to have a tool as simple as Google Sheets but with Jira’s charts; I also want to assess the team’s experience level and how test cases are executed. I’ll admit that I distanced myself quite a bit from test cases when I realized that, on the projects I was working on, it was a waste of time to keep writing lots of tests that no one would read. I support the Test Planning phase; I just think it should be optimized for the team so there’s more time for other testing activities.
18. Is there any test management tool that helps the team embrace a culture of quality?
Renata: I personally don’t believe that a specific tool is the solution for a culture of quality. I believe this stems largely from the team’s culture and the people involved. There are countless guidelines for fostering a culture of quality, but it’s really in our day-to-day work that we, as QAs, come to understand what fits and what doesn’t fit within the company’s context. In one of the projects I worked on recently, I used studies, such as DORA, to support what I was telling my peers and leaders. And little by little, they began to adopt the guidance I provided (and I was actually hired to educate the company). I share a bit more in the interview I did with Rafa Azevedo here: https://testingwithrenata.com/portfolio/interview-brazilian-qas-around-the-world-series/
