Running Browser tests using Uno.UiTest outside of development code

[Tree55Topz]

I'm submitting a...

Sample app request
Documentation issue or request

Current behavior

Uno.UiTest has documentation regarding how to create tests inside of the same solution where host code lies, but in a lot of cases, UI Automation developers are a part of QA and create their test code elsewhere in a solution outside of development

Expected behavior

If this is possible, have examples of how you could have a standalone Uno.UiTest solution to execute browser based tests

Sorry if this is not allowed, I tried asking a question on the Stackoverflow forum but no response and my team has invested a lot of time in using Selenium to create tests against our uno brower version.

The original SO post --> https://stackoverflow.com/questions/69976830/running-browser-tests-using-uno-uitest-outside-of-development-code

[jeromelaban]

For now, we are providing support for running tests from within visual studio, using the command line, or using automated tests.

You can derive some scripts to do this from here: https://github.com/unoplatform/Uno.UITest/blob/master/build/scripts/wasm-uitest.sh

GitHub

Uno.UITest/wasm-uitest.sh at master · unoplatform/Uno.UITest

Unified UI Testing Framework for Uno Platform based applications - Uno.UITest/wasm-uitest.sh at master · unoplatform/Uno.UITest

[Tree55Topz]

@jeromelaban thats not quite what I am asking. I am wondering if its possible to create a test solution that exists outside of the actual uno/host code for the app. In most cases, UI tests are created by the QA automation team and not the developers.

So I am wondering if the actual test code like identifying elements, creating test scripts, cleanup in between test cases - if all of that can be in its own VS project using the page object model design

[jeromelaban]

You can setup your environment to use an already deployed application, there's no explicit dependency between the UI Tests projects and the app project itself. Change this to point to the appropriate location:

Uno.UITest/src/Sample/Sample.UITests/Constants.cs

Line 12 in 3adc7f2

public readonly static string WebAssemblyDefaultUri = "http://localhost:54490/";

[Tree55Topz]

@jeromelaban ok thank you - we will have to test it out. Do you know of any reason why just using Selenium would be a bad idea? We already have built up a decent amount of selenium code to test the Uno version of our app and the biggest challenge is just identifying elements as the HTML code that gets generated is quite ugly and complex.

[jeromelaban]

You can use selenium directly, but it won't change anything with the naming of elements. You can name elements with what is documented in the readme of this repository.