jztan

Thanks for the feedback! We may change the home page a bit, but actually our platform is self-service to a high degree. The majority of our functionality is not paywalled so I apologize if it came across that way immediately.

SOTA on lots of PDF tasks with weights released

Curious if anyone strongly prefers "keyboard" or "pyautogui"?

I once worked at a company with 1000 UI tests. Every PR tests would fail because certain backend failures would cause flaky behavior. Then, we started mocking response, and of course they no longer failed. They also no longer caught real bugs anymore. Does that give you some nuance?

First of all, I didn't make this, let me be clear, and I don't work for the company Mobile.dev.

I've been looking for a replacement for Appium because the documentation for that site is absolutely garbage. Maestro boils everything down to YAML and runs its own test server so that you don't have to worry about connecting to the device drivers. It's missing an API but who needs an API when the CLI is so beautiful.

Does anyone know of anything on par with this that I should try? So far this has knocked my socks off.

Great suggestion! We will include ML-based corrections for individual developer mode very soon. For others, even a sign post is helpful. The translation point is a great one that we are also excited to work on.

We will have AI-suggested corrections in the near future! There are a lot of applications for AI here around structure and understandability of an app for the accessible user. We also plan to increase rule coverage to as many WCAG rules (78 total) as possible, starting with the most common offenders.

Hi! Sharing a product after many iterations on its UX (with more rule coverage coming soon).

I stumbled upon this problem when the company I was at faced an accessibility lawsuit and needed engineers to fix them. Though there were accessibility champions, I fell into the category of average engineer who had very little experience with correcting/testing these tickets.

With jargony documentation of accessibility guidelines and bad descriptions from audit, it was very frustrating to work with. I could not easily fix them without seeking help.

My friend Michael and I started working on this problem and are excited to launch:

https://www.testparty.co

TestParty’s first product is a VSCode extension called Pregame. It scans your code inside the IDE and provides code suggestions for accessibility violations. In your side bar, you will see why it fails/passes guidelines and gives you some accessibility training in-context. The link below is the direct link to the VSCode Extension:

https://marketplace.visualstudio.com/items?itemName=TestPart...

Would love for you to try it out and provide feedback. If you would like to chat, my email is jasonzhetan116@gmail.com