23/04/2026
Still testing your PowerBuilder or .NET apps by hand?
Most teams do. It works — right up until you ship a UI change, rename a DataWindow column, or push a new release under pressure.
Then the manual process shows its real cost: time, regressions, and a testing cycle that can't keep up.
Here's what a more practical setup looks like — without touching your existing codebase:
→ Create tests by pointing and clicking on your app objects — no scripting, no framework to build
→ Reuse test blocks across scenarios so maintenance stays manageable
→ Run on demand, on a schedule, or wired directly into Jenkins or Azure DevOps
The key difference: tests are built on application objects, not screen captures. So when your UI evolves — in PowerBuilder or .NET — your existing tests keep working.
Full DataWindow support included. Covers PowerBuilder desktop, PowerServer Web, WinForms, WPF, Angular, and more.
Worth a look if your team is still doing this manually 👇
https://ascentialtest.novalys.net/EN/lp-ascentialtest-pb-dotnet-source_li1340at.html?single