1

I have problem with Test Complete software, and WiX software. When we build installer(MSI file) from pipeline (or locally) after running installer we see two different processes (on screenshot).

When we try to detect "next" button on installer (or any other button) Test Complete detect button sometimes in 1st process, sometimes in 2nd process: 1ex.: Sys.Process("msiexec", 2).Window("MsiDialogCloseClass", "INSTALLERNAME", 1).Window("Button", "&Back", 3)

2ex.: Sys.Process("msiexec").Window("MsiDialogCloseClass", "INSTALLERNAME", 1)

That generates problem cause Test Complete in 50% test fall. It search button in 1st process when we have installer window i 2nd process...

How to change installer build to have just only one process for installation?

Documentation ow Wix did not given any clue. And - Before we migrated to Wix - we used Installshield.

1 Answer 1

0

You could either map the parent process and do not include the Index property in the NameMapping, and work from there.
How to remove index property from namemapping
Then either:
Aliases.{YourMappedNameForWixApp}.Window("MsiDialogCloseClass", "INSTALLERNAME", 1).Window("Button", "&Back", 3) or map the button from there as well.

Alternatively, if for some reason you do not want to use NameMapping, you could use FindChild from the Sys object thus:
Sys.FindChild("Name", "Window('Button', '&Back', *)", 1000)

Sign up to request clarification or add additional context in comments.

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.