-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Migrate legacy UI tests to Appium #20245
Copy link
Copy link
Closed
Labels
Taskneither bug nor feature but something that needs to be done in support of eitherneither bug nor feature but something that needs to be done in support of eitherarea-testingUnit tests, device testsUnit tests, device testsfixed-in-8.0.80fixed-in-9.0.0-rc.1.24453.9testing-legacy-ui-testsIssues/PRs that are associated with transitioning our legacy UI Tests to AppiumIssues/PRs that are associated with transitioning our legacy UI Tests to Appium
Milestone
Metadata
Metadata
Assignees
Labels
Taskneither bug nor feature but something that needs to be done in support of eitherneither bug nor feature but something that needs to be done in support of eitherarea-testingUnit tests, device testsUnit tests, device testsfixed-in-8.0.80fixed-in-9.0.0-rc.1.24453.9testing-legacy-ui-testsIssues/PRs that are associated with transitioning our legacy UI Tests to AppiumIssues/PRs that are associated with transitioning our legacy UI Tests to Appium
Type
Fields
Give feedbackNo fields configured for issues without a type.
Projects
Status
Done
To be more aligned with our current/new UI tests, we want to migrate our legacy tests also to Appium. Below are the (rough) steps outlined to achieve that.
This would basically be a complete replica of our current appium testing because that already models the gallery (we could probably generalize out this library a bit). Would it make sense to just split up our current Appium tests? Test Explorer doesn't really work very well with our single project concept. We could then just put them all into the current runner and just into a different category.
maui/src/Compatibility/ControlGallery/src/Issues.Shared at main · dotnet/maui (github.com)