This is a bit weird one. I have test scenario where i need to fetch OTP via email and the process has been working fine for over 6 months when i’ve been strictly using Chromium as a browser. Recently i added firefox also into the testruns and I’m having problems with it.
I have a following keyword (extra stuff stripped away)
Open Inbox
[Documentation] Short description.
...
... Args:
... ${email}: base portion of email to use for mailinator service.
[Arguments] ${email}
VAR &{viewport_args} width=1920 height=1080
New Browser ${DEFAULT_BROWSER} headless=${True} reuse_existing=${False}
New Context
... viewport=${viewport_args}
... ignoreHTTPSErrors=${IGNORE_HTTPS_ERRORS}
New Page ${MAILINATOR_INBOX}?to=${email}
On this case, DEFAULT_BROWSER is set to firefox and MAILINATOR_INBOX is https://www.mailinator.com/v4/public/inboxes.jsp
- so far so good.
In log.html i can see following;
05:04:13.609 INFO Successfully initialized new page object and opened url: https://www.mailinator.com/v4/public/inboxes.jsp?to=XXX_MY_EMAIL_HERE_XXX
And at this point i start polling for my OTP which fails after my timeout and screenshot is taken. When the fail eventually comes and i check the screenshot;
On chromium, that GO text field would contain XXX_MY_EMAIL_HERE_XXX
.
Anyone seen this sort of thing happening ? Ofcourse it could be mailinator that it detects a headless firefox (as i cant reproduce this on desktop) but that feels bit odd of them.
Ofcourse in my case, im not testing mailinator so i can just use chrome.