All geek questions in one place

GUI Automation Testing - Window Issues

At present, our company is creating a tool for automating GUI automation for compact framework applications. At first we looked for a lot of tools, but none of them were right for us.

Using this tool, you can record test files and group them together with test sets. For each test suite, an application is created that launches the application under the test and simulates user input.

In general, the tool works just fine, but since we use window handles to enter user input for modeling, you cannot do so many things. For example, we cannot get the name of the control (we just get the title).

Another problem with using window handles is checking for changes. At the moment, we are simulating a click on a control and depending on the result, we know that the application has passed to the next step.

Is there any other (simpler) way to perform such actions (for example, a message queue or something else)?

+3
source share
5 answers

GUI , , . TestComplete, , Borland VCL WinForms. Windows Presentation Foundation, build.

+1

! - (, Win32) Windows, .

. , , HWND , . , , . , " " , , .

, , , , API Win32.

, , , script. , , , , script. script.

( , , ..), script . , , , , , . , ( , ), .

(EDIT: QA -, : , , , script)

!

+2

- : Managed Spy. .NET, ManagedSpyLib.

ManagedSpyLib allows programmatic access to the Windows Forms controls of another process. To do this, it uses Window Hooks and memory mapping files.

Thanks to everyone who helped me get to this solution!

0
source

Managed Spy does not provide a solution for compact frame applications.

Jamo Solutions (www.jamosolutions.com) meets the requirements for testing automation on mobile devices, including compact .net framework applications.

0
source

Source: https://habr.com/ru/post/1696468/

More articles:


All Articles