| ▲ | jrochkind1 5 hours ago | |
I'm not totally following the part about the simulator(s), probably because I haven't actually done mobile development before. > When simulator interaction is needed, the CLI can connect to them via a remote mode and drive the UI via commands without having to inspect the layout or the accessibility tree. This enables blazing-fast performance and E2E tests. I think I'm not following. Don't you still need to test the accessibility tree and layout in the actual layer the user will interact with? | ||
| ▲ | azuanrb 3 hours ago | parent | next [-] | |
It’s a reasonable tradeoff. Shopify uses Rails, and there’s been a long history of discussion around E2E testing in the Rails community. In recent Rails releases, system tests, or E2E tests, are no longer enabled by default. The short version is that they’re significantly slower and more brittle. Basecamp also removed most of their E2E tests. I don’t know what Shopify does internally, but my guess is that they’ve taken some of those lessons and are trying to apply the same thinking to mobile development too. https://guides.rubyonrails.org/testing.html?#when-to-use-sys... | ||
| ▲ | raspo 4 hours ago | parent | prev [-] | |
I have done some iOS development and still couldn't follow what the article was saying about the simulator. I'm actually quite interested in it, because (in my experience at least) verifying that the UI works as expected is quite painful with current LLMs and the developer tools available. They talk about building a CLI and keeping business logic isolated, ok fine, but do they still run the simulator and take screenshots to verify their work?! | ||