FlaUI VS testcontainers-dotnet

If you are looking to automate this all through the GUI of each app involved then I suggest using FlaUI or some other wrapper around UIA

FlaUI

The best open-source library for writing UIA for native Windows desktop apps is FlaUI if you find the problem space interesting. I started learning about all types of UIA when I started at a company doing QA work. Now I worked on UIA because I learned from my experience how bad UIA support is in most applications, and I am disappointed that people who are disabled have that to look forward to, not to mention that if my hands were ever crushed or some other maiming were to occur, I would be depending on UIA as well. Since that realization, I have tried to get more developers interested in UI automation and its quality, not just because of its effect on others with disabilities but because it benefits anyone in our profession to have that safety.

Alternatively if you're into dotnet, FlaUI is amazing for automation and gives you a sane environment. I moved to it when I couldn't deal with AutoIT scripts anymore and it's everything I needed. https://github.com/FlaUI/FlaUI

I would suggest taking a look at FlaUI https://github.com/FlaUI/FlaUI

What comes to mind is something like this one: https://github.com/FlaUI/FlaUI I don't think it can do the "search image on screen" part. A smooth mouse movement is only a series of mouse teleports, so that should be coded relatively easy. If you really don't know where the image is on screen and it also does not have a id to search for then it will be a little harder I guess. Like making a screenshot and putting it into some image processing library? Probably there are easier solutions out there

Is it possible to control another program via code? This link says yes and the following is the successor of what they originally recommended: https://github.com/FlaUI/FlaUI.

If you're like me and have way too many tabs open and then get lost whenever you need to access that one tab quickly again, then this software might help you. It basically uses FlaUI to search for tabs in your browser instances and allows you to open the tab within a click. No need to manually click through all your browser instances. Kinda like the launchers everyone knows, just for browser tabs.

Testcontainers

Like others said, it's better to test with an actual database. I recommend using Testcontainers (https://dotnet.testcontainers.org), you can even create multiple instances so your tests can run in parallel independently.

To launch a container in code we will use Testcontainers. Testcontainers is a library that is built on top of the .NET Docker remote API and provides a lightweight implementation to support your test environment in all circumstances. This library supports pre-defined packages for containers or you can use your .dockerfile. We will use a pre-defined package for LocalStak. LocalStack is a cloud service emulator that runs in a single container for AWS service. LocalStack supports a growing number of AWS services.

Bogus - For creating fake data Verify - Snapshot testing for .NET MELT - For testing ILogger usage Stryker - Mutation Testing for .NET TestContainers - run docker programmatically in integration tests

.NET Shop using SQL Server here, but I think something similar to what we do can apply to any stack. We use TestContainers [1] to spin up a container with SQL Server engine running on it. Then use FluentMigrator [2] to provision tables and test data to run XUnit integration tests against. This has worked remarkably well.

[1] https://dotnet.testcontainers.org/