Overview: Low code testing relies heavily on complete UI
end-to-end testing. It needs to be fast, flexible, quick to correct,
scale-able, highly configurable and BrowserStack's low code test tool is in
beta and definitely on the right path - for me, it needs a few features.
I ran my testing against customised apps created on three platforms:
- Mendix low code,
- Microsoft's Blazer hosted on Azure Web App, and
- Canvas app within Power Platform.
Tip: I've looked and use BrowserStack for many years and it has moved from being an device emulators infrastructure testing provider to a full ALM testing platform. The low code Browser stack has a recorder to capture steps.
Where does Low Code fit into Browser Stack:
 |
| Image1. Low code automation works well as part of the full BrowserStack Platform or just using the product by itself. |
Pros of the Low Code BrowserStack Product:
- The local recording feature is easy to set up and use
- Seamless integration with the cloud version running on
BrowserStack's infrastructure
- Logical layout of UI, little to no training required
- UI validation using the DOM or, more importantly, screenshots using
BrowserStack's AI verification (required further review) has the potential
to self-heal as in the screen changes, but the validation can be smart
enough to understand it is just an updated screen (example a single colour
in the page and the position of the name is moved).
- SDK is available to work with the full BrowserStack platform.
- Not Low code specific but BrowserStack generally has the new phones included in their offering within days of being release.
Cons:
- Provide a webhook or allow for a REST client call as a step (I'd
want to log directly from the test run into Azure Monitor)
- More run options, I'm sure it's already on the road map, but the
ability to run every hour for continuous monitoring.
- Refresh tokens on a schedule (allows you to not use MFA such as SMS
codes or Authenticator).
- Make it clear if the run is from the local or the browser, and keep
the historical logs for both together.
- Export results - I could not find this, but it would help compare
step performance.
- I use DevOps, I'm unlikely to take the whole BrowserStack platform unless i need the emulators which is what BrowserStack was originally famous for.
Summary: This is an excellent tool for testing; the low code product was still in beta when I reviewed it. It is a nice tool and has the potential to disrupt the market. I feel Playwright is a better point solution and integrates to CI/ALM platforms.
Other:
 |
| Image 2. Emulate a Samsung Galaxy phone on Android using the Chrome browser. Thought: I like BrowserStack's reporting, clean and simple on tests and easy to get the history. |
