Integration Testing docs are very basic and don't cover common real-world scenarios

[bartekpacia]

I feel like Integration Testing documentation (link 1, link 2) is not good enough. It doesn't mention how limited the integration_test package is:

• unable to interact with native UI (Document how to write UI tests that interact with native UI elements #36024, Document how to write UI tests that interact with native UI elements #36024)
• no sharding on CI ([integration_test] Enable sharding of integration test suites #101296)
• slow iteration time (Building all integration test targets into a single application binary #115751)

New Flutter developers thus may think that integration_test "the best" of testing and that everybody does that, while in reality it's rarely the case because of the problems above.

As far as I'm aware the Flutter team doesn't have plans nor throughput to improve the integration_test plugin, but maybe these docs could link to other popular testing frameworks made by the community, including:

• https://github.com/leancodepl/patrol
• https://github.com/appium/appium (with appium-flutter-driver)
• https://github.com/mobile-dev-inc/maestro

along with a short description (possible also including a list of objective advantages and disadvantages).

[bartekpacia]

The docs could also mention Semantics.identifier as a recommended way to expose widgets for accessibility-based UI testing.