PuppeteerSharp VS FlaUI

We often need to automate tasks or test applications as developers or testers. In such cases, there is usually limited time for manual testing, making PuppeteerSharp an ideal tool for task automation.

PuppeteerSharp

Otherwise, any pdf to hml chromium based solution hosted via docker, like gotenberg](https://github.com/gotenberg/gotenberg) or browserless.io(which is free if you create open source). Generating pdfs from html directly in .NET was always a pain. Wkhtml (and wrappers that use it) uses WebKit and comes with a load of issues of its own, similar to running and styling anything in Safari. Using chromium based engine saves a lot of time as it's the most popular way of doing it these days. You can also use puppeteer-sharp with local chromium if you host your app on something that allows it(f.e. not Azure Functions).

Puppeteer Sharp is a port of the popular Headless Chrome NodeJS API built by Google. Puppeteer Sharp was written in C# and released in 2017 by Darío Kondratiuk to offer the same functionality to .NET developers.

there is a dotnet package for using headless chrome: https://www.puppeteersharp.com/ its a port of the nodejs package of the same name

For the actual conversion of html to pdf we use PuppeteerSharp (https://www.puppeteersharp.com ) but you need browserless for that, which requires an api key (don’t know the pricing)

The README in the GitHub site has been good enough for me: https://github.com/hardkoded/puppeteer-sharp

Iv'e been using https://github.com/hardkoded/puppeteer-sharp for html to pdf conversion for quite some time with success. (in both .net framework and .net core)

Just generate HTML and use https://github.com/hardkoded/puppeteer-sharp to produce a PDF from headless Chrome.

The website is called FlaUI, and they even have a GitHub repository that looks legit.

After one of the disastrous releases, where changes in one area unexpectedly broke another, it became clear that UI automation tests were necessary. Although there were unit tests for some components, they did not check the functionality of the entire application. Manually testing all the functionality of each release would be too time-consuming, and besides, humans (at least I) are lazy and can make mistakes. If it can be automated, then it should be automated. The first tests were built using the TestStack.White library. Now, since this library is no longer supported, there is a smooth migration to the FlaUI library.

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