I have noticed that the plus packages have their e2e tests in different locations.
It would be good to unify that in the same package structure, this will facilitate running tests and contributions from external devs.
In general, tests should be:
in package_name/test -> dart and widget tests.
in package_name/example/test_driver -> flutter driver e2e tests.
Current location of all e2e tests:
android_alarm_manager_plus/example/test_driver/ ✔️android_intent_plus/example/test_driver/ ✔️battery_plus/test/ ❌connectivity_plus/example/test_driver/test/ ❌device_info_plus/example/test_driver/ ✔️package_info_plus/example/test_driver/ ✔️sensors_plus/example/test_driver/test/ ❌share_plus/example/test_driver/test/ ❌
Proposal:
Unify the package structure and move all e2e packages to package_name/example/test_driver
I have noticed that the plus packages have their e2e tests in different locations.
It would be good to unify that in the same package structure, this will facilitate running tests and contributions from external devs.
In general, tests should be:
in
package_name/test-> dart and widget tests.in
package_name/example/test_driver-> flutter driver e2e tests.Current location of all e2e tests:
android_alarm_manager_plus/example/test_driver/✔️android_intent_plus/example/test_driver/✔️battery_plus/test/❌connectivity_plus/example/test_driver/test/❌device_info_plus/example/test_driver/✔️package_info_plus/example/test_driver/✔️sensors_plus/example/test_driver/test/❌share_plus/example/test_driver/test/❌Proposal:
Unify the package structure and move all e2e packages to
package_name/example/test_driver