The website in question: https://www.maybank2u.com.my/home/m2u/common/login.do
I have been using Chrome to scrap some data from my account, but recently it stopped working - mainly due to the difference in behaviour when the LOGIN button is clicked.
The website is heavily driven by obfuscated javascript (is this even a good practice?). If you try to log in manually, i.e. after you fill in the username and click LOGIN, it will load a little and show you a security picture verification.
However, when I try to automate it, the website is stuck with the loading animation and the security picture never shows.
Here are some other setups that I have tried:
Here are my questions:
Side question: 3. Is this some kind of anti-automation mechanism from Chrome? Or the website itself?
Link to similar case: https://discord.com/channels/807756831384403968/1158628253192425593
This thread is trying to answer question "What is causing the variability in behaviour when trying to automate data scraping from a banking website, and how can it be avoided? Is it an anti-automation mechanism from the website or the browser?"
I've worked on few sites that will alternate the login page or other things as a cheap form of captcha, A human would never think twice what is needed and have to troubles... Automation on the other hand will get tripped up... I'd be curious about any end user agreements you clicked on "I agree not to use automation tools to access the site..." Can't think of any site going to much trouble unless you agreed to the terms of service to use their site... What site are you hitting?
https://www.maybank2u.com.my/home/m2u/common/login.do
I don't think there's anything about automation on their terms and conditions https://www.maybank2u.com.my/WebBank/Terms_and_Conditions_of_Maybank2u_Online_Banking_Services-EN.pdf
Rayrun is a community for QA engineers. I am constantly looking for new ways to add value to people learning Playwright and other browser automation frameworks. If you have feedback, email [email protected].