3 ms·
I was going to say the same thing. Why are the tests so disconnected from the usability? My assumption is the tests are closer to a unit test, while browsing a
by bangaladore 1y ago
I was going to say the same thing.
Why are the tests so disconnected from the usability? My assumption is the tests are closer to a unit test, while browsing a page is essentially an E2E test, and if anything in the pipeline goes wrong (especially given that we use complex JS everywhere) the result is essentially useless.
- zdragnar 1y agoThere's not a linear relationship between the tests and usability. There are many tests for various character encodings, but viewing a web page means you're only "using" one of them, for example. As such, 90% test pass rate but low usability simply means that 10% of the tests cover a lot of very visible usability features that ladybird hasn't addressed yet.
- troupo 1y agoweb platform tests are closer to unit tests than to integration tests or to smoke tests. Many of those are also very hard to write and check for correctly, since there are tens of thousands of lines of specs, and thousands of web APIs.
- achierius 1y agoEven if they passed 100% of the tests, it's still possible they'd be too slow for practical, everyday use. Speed is not tested in these, only compatability.