playwright-java VS Capybara

https://playwright.dev/java/ - Playwright is nice if you want to deal with dynamic webpages. It's not lightweight as jsoup as it internally using the real browser engines (headless), but there is no such limitations like in regular parser libraries with dynamic js content.

So I'm using the playwright library for a project (https://playwright.dev/java/), and I have like 4 different methods that navigate to the same page. Problem is, whenever I try to make a separate method for navigating to that part of the page, when I return that page and try to do things with it I get this error:

I'm so lost as to what to do to resolve this. I am trying to install playwright (https://playwright.dev/java/) into my Intellij IDE and I have run into so many problems. I have already tried looking for tutorial on how to do this but can't find one that helps me. I am also not familiar with Maven. I would MUCH prefer someone voice calling with me and walking me through it while I screen share than a text step-by-step. If anybody thinks they can help me with this problem, please temporarily friend me on discord, we can call and then you can unfriend me. Thanks. My disc is Sohezee#8362

Sorry. I was in shock because every time when request like this happened we asked a question about an API and if did not get anything we just told it's not possible/sustainable and client accepted it. Never I was forced to do things like that. I never would have guessed somebody does that besides of course data scrapping or SEO bots or something like that. I can't think of other solution if you really have to do that. Btw. maybe you know but if you are scrapping JS heavy apps maybe https://playwright.dev/java/ (or for other langs) would be of greater help.

Playwright supports all 3 major evergreen browsers and has Java bindings: https://github.com/microsoft/playwright-java

Java (or Kotlin): https://github.com/microsoft/playwright-java

Cuba takes help from a lot of other technologies to bring the best of everything. For example, the responses in Cuba are the optimized version of the Rack responses. The templates are integrated via Tilt and testing via Cutest and Capybara.

I am going to use a browser based testing tool called Playwright (But you could use Capybara, or Selenium WebDriver etc.).

Even as a much smaller team, building Heii On-Call [0] as a lightweight alerting/monitoring/on-call rotations SaaS based on Ruby on Rails has basically been a pleasure!

And as the article highlights, perhaps the key reason for smooth deployments and upgrades is that the CI testing story is so, so good: RSpec [1] plus Capybara [2] for us. That means we have decently extensive tests of just about all behavior. The few small Rails and Ruby upgrades we've done have gone quite smoothly and confidently, with usually just a few non-Rails gem dependencies needing to be manually updated as well.

The "microservices" story is where we've pulled in the Crystal programming language [3] to great effect. After dabbling with Go and Rust, we've found that Crystal is truly a breath of fresh air. Crystal powers the parts of Heii On-Call that need to be fast and low-RAM, specifically the inbound API https://api.heiioncall.com/ and the outbound HTTP(S) prober background processes. I've ported some shared utility classes from Ruby to Crystal almost completely by just copy-and-pasting ___.rb to ___.cr; porting the tests for those classes was far more onerous than porting the class code itself. (Perhaps another point of evidence toward the superiority of RoR's testing story...)

The front-end story is nice but just a bit weaker. Using Hotwire / Turbo successfully, but I have an open PR to fix a fairly obvious stale cache bug in Turbo [4] that has been sitting unloved for nearly a month, despite other users reporting the same issue. I'm hopeful that it will get merged in the next release, but definitely less active than the backend side.

For me, the key conclusion is that the excellent Ruby on Rails testing story is what enables everything to go a lot more smoothly and have such a strong foundation. I'd be curious if any GitHubbers can talk more about whether they too are using Rspec+Capybara or something else? Are there internal guidelines for test coverage?

[0] https://heiioncall.com/

[1] https://rspec.info/

[2] https://github.com/teamcapybara/capybara

[3] https://crystal-lang.org/

[4] https://github.com/hotwired/turbo/pull/895

Engineering at Aha! focuses on using and improving the Capybara test framework. We have added many helpers and additional functionality to make working with Capybara easy. Testing at mobile widths is another chance to improve our testing tooling. Here is the incremental approach that we used to add mobile testing helpers.

Since the Capybara library drives the underlying tests, Minitest also has the same syntax.

We can write component tests with any language or framework, but the most popular ones are probably Cucumber and Capybara.

The nice thing about partial templates is that templates are unit-testable with View specs (or similarly in Minitest) and the rendered output can even be verified using Capybara matchers.

To piggyback: This would be a type of browser test, so you would want to use something like Cypress (https://github.com/testdouble/cypress-rails) or Capybara (https://github.com/teamcapybara/capybara). RSpec has a good integration with Capybara. Cypress is JS-based so it will require some additional config.

When you write a system test (or, as we prefer, a system spec) with Ruby on Rails, you're exercising the whole stack from the point of view of the user. So, naturally, you have to do things like make sure that certain elements are on the page and work as you expect when you click on then, type in them, and drag them around. Capybara works exceedingly well for this, giving you a lovely API for querying HTML.