Blog
End-to-end testing for the modern era
How testing has changed, and how to make the most of it: from your first test to tests that run on every build.
Game testing
Automated Game Testing Without an SDK: Unity, Unreal, Godot
Automated game testing without an SDK in the build: test the menus, HUD and levels of a Unity, Unreal or Godot game with real keyboard, mouse and gamepad input.
11 min read
Read the article
Visual testing
Visual Bugs Your Automated Tests Miss: How to Test What Users See
Visual bugs your automated tests miss: why toBeVisible() and isDisplayed() pass covered or unreadable elements, and how to test what users really see.
10 min read
Read the article
Desktop testing
WinAppDriver Alternatives for Apps With No Accessibility Tree
Looking for a WinAppDriver alternative?Learn how Windows desktop test automation works, and how to test apps with no accessibility tree by sight, without code.
11 min read
Read the article
AI agents
How to Test AI-Generated Code With Independent End-to-End Tests
How to test AI-generated code from Claude Code, Cursor, Copilot or Codex: why the agent's own tests miss bugs, and how independent end-to-end tests catch them.
10 min read
Read the article
AI testing
AI Test Automation Without Vendor Lock-In: Cloud, Local and MCP
AI test automation without vendor lock-in: use a cloud model with your own key, a local AI model we provide or you bring, or no AI, and let any assistant drive your tests through MCP.
11 min read
Read the article
Data privacy
Data Privacy in Test Automation: Keep Sensitive Data On-Premise
Data privacy in test automation explained: where screenshots, videos and AI prompts go, what GDPR and HIPAA require, and how local AI, a model we provide or one you bring, keeps test data in-house.
11 min read
Read the article
Test reliability
Flaky Tests and False Positives: Why Tests Fail on a Working App
Flaky tests and false positives explained: why end-to-end and visual tests fail on a working app, and how to stop them without missing real regressions.
12 min read
Read the article
Web testing
Cross-Browser Testing: One Test for Every Browser and Device
Cross-browser testing explained: what breaks between browsers and devices, how teams usually cover it, and how to record one web test and run it everywhere.
10 min read
Read the article
Design to test
Generate Tests from Figma Designs Before the Code Exists
Generate tests from Figma designs before the code exists: test-driven development for the UI, design QA without selectors, and checks that sync with the design.
10 min read
Read the article
Comparison study
Stop Coding Your Tests: How GUI Test Studio Compares to Legacy E2E Tools
GUI Test Studio side by side with Selenium, Playwright, Cypress, Katalon, mabl, Applitools Eyes and Percy: a comparison study, the problems with coded tests and their limitations, coded tests compared with GUI Test Studio topic by topic, and four positioning matrices of where each tool stands.
12 min read
Read the article
How it works
Accessibility first, vision when the app says nothing: how GUI Test Studio finds every element
Most end-to-end tests break because they cannot find an element any more.The GTS Engine + AI finds each element two ways: it asks the application through its accessibility information, and finds the element by sight when the application does not say.Why two ways to one element make a test robust, with no locator to write or maintain.
6 min read
Read the article
AI agents
Development with AI agents (ADLC): where GUI Test Studio fits
AI coding agents plan, write, test, fix and ship, with people steering: the agentic development life cycle, or ADLC.Where end-to-end testing fits in that loop, and how GUI Test Studio gives an agent a test it can create from a prompt, change in place, run headless and in parallel in any CI/CD pipeline, read as a plain-words verdict and file in Jira, until the loop closes.
9 min read
Read the article
Bug reports
Connect Jira to the Confidence Report: every failed end-to-end test becomes a Jira bug, automatically
Connect your Jira site to GUI Test Studio once and every failed end-to-end test becomes a ready-to-fix Jira issue: steps to reproduce, expected and found pictures with the change outlined, a PDF and the evidence.From the Confidence Report in one click, or from TeamCity and any CI/CD pipeline on every failed build.
8 min read
Read the article
CI/CD
Run your end-to-end tests on every build: a TeamCity example that works with any CI/CD tool
End-to-end test automation in your pipeline: add your GUI Test Studio tests to a TeamCity build in one step with gtr-cli, and read each test, the failures, the video and the pictures in TeamCity.The same command runs your GUI, functional and regression tests in Jenkins, GitHub Actions, GitLab, Azure DevOps or any script.
7 min read
Read the article
Getting started
Getting started with GUI Test Studio
Your first automated test in about ten minutes, without code: install, record, choose what to check, run it, read the report, and run it on every build.
7 min read
Read the article