But I find a itchy problem still remains. It’s great to know that I can write test code that can open Chrome with predefined Profile. In Katalon Studio, in test case script, you can write Groovy code to open Chrome browser as this:ĬhromeOptions chromeProfile = new ChromeOptions() ĬhromeProfile.addArguments("user-data-dir=" + "C:\\Users\\thanhto\\AppData\\Local\\Google\\Chrome\\User Data\\") ĬhromeProfile.addArguments("profile-directory=Profile 2").The association of new_chrome_profile and Profile 2 was determined by Chrome when new_chrome_profile was added. For example, the Profile new_chrome_profile is found associated with the C:\users\osusername\AppData\Local\Google\Chrome\User Data\Profile 2 folder. In Chrome UI, you can identify the Profile path, a folder, where all of cached data is stored.In Chrome UI, you can create a new Profile with name new_chrome_profile.Thanh To, a Katalon Developer, replied to aguggella in another post Open Browser with Custom Profile. But how can I achieve it? How to open Chrome with predefined profile If I could somehow let Katalon Studio to start Chrome with the same Profile ‘Katalon user’, then the test will run without requiring manual intervention. Let me assume, I opened Chrome with a Profile ‘Katalon user’ and logged-in Salesforce applition. Therefore Salesforce application sends a new OTP. Why? Whenever I start test script, Katalon opens a new browser with no cached data. Problem arises here: I want to automate testing the Salesforce application using Katalon Studio, but I can not. I will not be asked to repeat login operation. As long as I use the same Profile of Browser without clearing cached data, the original OTP is retained in the cache. I need to open browser manually and login to the Salesforce application once. I have Salesforce application which will send OTP (one time password) to the client’s browser on the following occasions: (1) first time of logging-in, (2) at the second logging-in and later when the browser does not present credential information associated with the original OTP because the browser’s cache is cleared or empty I would quote the paragraphs with a bit of rewording: The originator aguggella gave us a good explanation what his/her problem is. A post in the Katalon Forum Run Automation in the Active browser raised an interesting question.
0 kommentar(er)
