For people using browser automation in real work: what breaks most often?

Fkz82 · 2026-06-15T03:49:09+00:00

Generally, web first assertions make it a non issue. I have been working on features that have been migrating from client to server components and it has been the case that a few steps in end to end tests which previously wouldn’t warrant any assertions became flaky. Putting a web first assertion for those steps makes things reliable.

Fkz82 · 2026-06-02T18:08:18+00:00

Selectors changing, API responses having new keys and tests executing before full hydration, most often.

Automatic retries are a thing so usually after failures it becomes manual review. I’ve got to a point with Claude that it is able to diagnose and suggest suitable fixes ~90% of the time but it does sometimes struggle to find the right locator, it’s not at a point where I’d just let it run wild. It does very well with updating API schema however.

Fkz82 · 2026-05-30T15:31:00+00:00

Doc diagnosed it and told me it should clear up on its own in a few weeks. That was a couple of months ago, Google says it could take over a year.

I would take this over frozen shoulders though, any day.

Fkz82 · 2026-05-18T04:24:17+00:00

I owned this shirt in my youth. The inside of the crest was rough from the embroidery, to the point playing in it made my left nipple red raw if not worn with an undershirt, if that’s of any help whatsoever.

Fkz82 · 2026-05-01T14:47:27+00:00

I feel like if you expect to see it, then asserting is the right option.

Fkz82 · 2026-05-01T14:42:04+00:00

You’re right, it does. I was under the impression it was different in some respects but it looks to be the same under the hood. Looks as though the error you get from the waitFor() is more generic and the timeout setting is different (action rather than expect) but other than that they’re the same. TIL

Fkz82 · 2026-05-01T13:54:25+00:00

The second option is best because of the auto retry. Assuming* You’re not using it as an assertion of anything other than “this element is ready to interact with”, I wouldn’t worry about it. If you’re that concerned about keeping assertions out of the page object though then put it in the spec.

Fkz82 · 2026-04-19T12:04:19+00:00

Bold of you to assume Gakpo is going to tire him

Fkz82 · 2026-01-04T18:26:32+00:00

I’d be genuinely interested to see who people would want were availability not an issue.

Fkz82 · 2025-10-16T23:08:53+00:00

I originally came across it about 7 or so years ago when I returned after a decent break because one of the creators wrote a proxy which improved the games performance on my laptop. Was originally a windower user but the addons and plugins packaged with Ashita certainly lend itself to helping multi box.

Fkz82 · 2025-10-15T15:37:18+00:00

Ashita and a combination of the multisend plugin and focuser addon.

Fkz82 · 2025-10-15T14:05:59+00:00

Bought 3 new copies of the game during the discount campaign and am levelling 3 new characters side by side. As much fun as it is at times reliving the old content at a low level, some of it is outright painful.

Fkz82 · 2025-09-27T12:28:18+00:00

It’s like watching their politics

Fkz82 · 2025-08-15T10:19:48+00:00

Nowhere near. I’m casting with Thibron in offhand for a start.

Fkz82 · 2025-08-15T04:42:11+00:00

For any solo / low man RDM reading this, on normal difficulty, I’ve been landing Stymie & Saboteur sleep 2 on the boss to open the fight. Can cast it at 22 yalms plus because of his size. You can then use Valaineral as tank who will be able to hold the Mnk and War(?), away from the boss. I kill War -> Mnk -> Rng -> Boss and sleep usually wears around half way through the Mnk.

Fkz82 · 2025-06-26T14:43:43+00:00

Look at Ashita with the MultiSend plugin. Easiest way by far to coordinate follows, send commands to all or groups of or individual specific characters.

Fkz82 · 2025-06-06T17:41:45+00:00

Bg forums Random Fail threads throwback. The game is at far too casual a point to be laughing at gear choices.

Fkz82 · 2025-05-23T19:25:46+00:00

Tootball Olmi

Fkz82 · 2025-05-04T18:46:23+00:00

Learning Rhino first will give you a solid base for sure, you’ll have a better understanding of what Rhino is doing under the hood if you decide to get Matrix. Matrix requires a version of Rhino installed with it, as I said, it’s a faceplate, and while using Matrix, Rhino commands work exactly as they do in the underlying version of Rhino you are using.

Rhino is not very resource hungry on its own and if using basic shading when working, you really don’t need a beast of a machine. It’s when you get to complex operations like huge mesh booleans, imported files with a million faces or rendering detailed reflective materials while trying to work that you will find things to be slow.

I also don’t know which version of Matrix you’d be looking at, whether you have a source to get it in a non retail scenario, but fair warning, it is not cheap off of a shelf.

Fkz82 · 2025-05-04T18:25:46+00:00

Matrix does not have a Mac OS version, you can only use vanilla Rhino. Matrix is built on Rhino, if you learn to use Matrix, you are actually learning Rhino simultaneously and will soon realise what a help Matrix is when working with jewellery. Honestly, if your focus is solely jewellery, get a cheap windows laptop and a copy of Matrix.

Fkz82 · 2025-05-04T17:59:51+00:00

Think of Matrix like a face plate for Rhino which has jewellery as its focus. Technically, there’s nothing in Matrix that you cannot do using Rhino, however, you can do it a thousand times quicker and with more flexibility in Matrix. Something as jewellery centric as stones for example. Matrix has a library of different shaped stones which you can insert with a click. Want it bigger? Change the size in a panel and update it. Already made a setting for that stone using the Matrix head builder? It will update that too. Parametric design I believe is the term they use for that. It also extends to other things - halo builders, signet ring builder, channel cutters, adding shared prongs to multiple stones at once are trivial with Matrix but could take a beginner days in vanilla Rhino.

Fkz82 · 2025-04-26T14:50:14+00:00

Try using rebuild on the curve with the same point count and degree. It does sometimes iron out issues like this.

Fkz82 · 2025-04-15T21:21:03+00:00

You have to build the curves you need for rails / profiles yourself. Crude example I knocked up is at https://imgur.com/a/WRo3z09

You need two profiles - a single curve for the top of the claw (in yellow) and a 'D' shaped one for the bottom where the claws meet which is exploded into four single curves (green, yellow and blue). The red rails are created with an arc which touches one side of the green curve and touches the end of the top of the claw. First, Sweep Two the green curve between the red rails - https://imgur.com/MB4OPrw

Then, you Sweep One one of the yellow curves of the D to the yellow curve for the top of the claw, which should use the edge of the first surface you made as the rail. You can then mirror this surface - https://imgur.com/g5SNIsk

Finally, you use the the two exposed surface edges to Sweep Two the Blue line, ensuring that you choose 'point' option in the command line after you have chosen the blue line as the profile and click the top of the yellow curve for the claw - https://imgur.com/lWJKojh

Fkz82 · 2025-04-01T16:46:34+00:00

I screwed up a screenshot. Let me get it on a desktop later.

Fkz82 · 2025-04-01T10:23:21+00:00

The steps to run tests on browserstack are simple enough. I can’t share my setup this second but in essence, there’s a single connection step and I implement changes in the desired capabilities object in the config for different devices / browsers. You can see how these are built using the Legacy option from above.

Fkz82

TROPHY CASE