My kingdom for a way to stop this godforsaken industry from stripping Tolkien's fiction for parts.
Let's start naming things after Iain Banks ships.
Bombadil: Property-based testing for web UIs
21–30 of 112 posts
Re: Bombadil: Property-based testing for web UIs
#22My kingdom for a way to stop this godforsaken industry from stripping Tolkien's fiction for parts.
Makes me want to name a project or company Sauron in response.
Re: Bombadil: Property-based testing for web UIs
#23I'm doing propety-based test since years for frontend stuff. The hardest part is, that there is so much between the test inputs and the application under test, that I find 50% of the time problems with the frontend test frameworks/libs and not in our code.
Interesting. What kind of properties are you checking?
I use quicktheories (Java) and generate a determistic random test scenario, then I generate input values and run the tests. This way I can create tests that should fail or succeed, but differ in the steps executed and in the order with "random input".
Re: Bombadil: Property-based testing for web UIs
#24My kingdom for a way to stop this godforsaken industry from stripping Tolkien's fiction for parts.
Let's start naming things after Iain Banks ships.
I am in support. In general he was really good with names I thought, they always had an otherwordly flair while being clear to pronounce. Skaffen-Amtiskaw, Anaplian, Elethiomel...
Re: Bombadil: Property-based testing for web UIs
#25I'm doing propety-based test since years for frontend stuff. The hardest part is, that there is so much between the test inputs and the application under test, that I find 50% of the time problems with the frontend test frameworks/libs and not in our code.
Are you talking about user flows and multiple interactions that are happening and data exchange that PBT before that wasn't able to address?
PBT allows us to test more combinations without writing hundreds of tests. Yes, it's about user flow inside a single module of our gigantic application.
Re: Bombadil: Property-based testing for web UIs
#26My kingdom for a way to stop this godforsaken industry from stripping Tolkien's fiction for parts.
I'm just waiting for them to exhaust LotR and move on to Roverandom
Re: Bombadil: Property-based testing for web UIs
#27For most static UI surfaces, I probably wouldn't use it, but I can see a use case in this for testing generative UI workloads.
Re: Bombadil: Property-based testing for web UIs
#28Author here, happy to answer questions about Bombadil! :)
From a project management perspective, the 5 examples don't help me understand how/why I might switch from Playwright/Cypress to this framework. It seems like Bombadil is a much lower-level test framework focusing on DOM properties but in the "Why Bombadil?" introduction you say "maintaining suites of Playwright or Cypress tests takes a lot of work" ... I'd like if there was an example showing how this is true, perhaps a 1:1 example of Playwright vs Bombadil for testing something such as notifications clearing when I click clear. Basically, beefing up examples with real-world ones that Playwright users might have written is a good way to foster adoption.
Re: Bombadil: Property-based testing for web UIs
#29My kingdom for a way to stop this godforsaken industry from stripping Tolkien's fiction for parts.
Makes me want to name a project or company Sauron in response.
I've worked at a company that had a team call themselves Sauron before
So occasionally I got mails by "some colleague on behalf of Sauron" back then
Re: Bombadil: Property-based testing for web UIs
#30very cool! does this work? can you describe the kinds of real bugs you've caught with this?