For bug reports and questions, please use the in-app chat or support@mabl.com.
As a QE, I want pseudo login unde your Mabl account(subaccount type) so that I can multiple tasks and not mess up with the current session and do recording/scripting at the same time while a journey is currently running on a separate tab or window. Audit for sub-account will still fal under the main account or can be designed as [main account -pseudo account1} format. eg: gerald.habal@careerbuilder.com-pseudo account1
Thanks Anton. The mabl CLI is definitely an option though it takes away the visual friendliness of mabls when running the test using the usual option via UI. This can be a "soon" feature but will definitely very helpful - able to mutitask at the same enjoy the visual user-friendliness of using Mabl
Attachments Open full size
Gerald, I can definitely see the challenge of editing and validating multiple tests locally. The easiest workflow today will be to save changes to a test on a mabl branch, trigger a cloud run for that test, and start working on a different test until the cloud of the previous test completes. An alternative to this will be to use the mabl CLI to trigger multiple test runs from different terminal windows, which will open a separate Chrome instance for each test run. The CLI now includes a preview of the upcoming
--headless
mode support with thetests run-alpha <id> --headless
command. Can you please give the CLI option a try and let us know what you think?Attachments Open full size