Skip to content

[Testing] Rework the Catalyst Test Runner so that it will pass in the next test as a startup argument vs navigating by keyboard #30285

@PureWeen

Description

@PureWeen

Description

Currently _IssuesUITest.cs will use private void NavigateToIssue(string issue) to navigate to an issue by interacting with the UI.

Ideally what we would do is when appium starts up the catalyst app it will just pass in the test name it wants to navigate to and then from there the runner will just go directly to the test.

One of the reasons this is tricky to fix right now is that we reset the app inside

public virtual void TestTearDown()

So we are restarting the app when the test finishes and then the app is restarting so it's ready for the next run.

What we should be doing is resetting the app when we start the next test run and passing arguments into the catalyst app so that the running catalyst app can read those arguments and just set that as the start page vs using the keyboard to navigate to the test

Metadata

Metadata

Assignees

Labels

area-testingUnit tests, device testss/triagedIssue has been reviewed

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions