TessDataDir = ‘D:\Dev\tools\tessdata.ocr’ <- this host the Eng data dictionary (eng.traineddata)Ĭode to perform simple OCR, where imageFile is individual full-path-filename that you snapped earlier that you can perform a loop scan to stop when the TEXT you looking for found. Since Tess4j v4alpha, the whitelist seems broken thus, left out from here.īasically variables, you can assign via Katalon Profiles: You need Tess4j (tess4j-4.0.1.jar, in my case) for the basic OCR as here I not involving yet OpenCV (see another topic created today). Mobile.takeScreenshot(filename, FailureHandling.STOP_ON_FAILURE) ‘.png’] as String, FailureHandling.STOP_ON_FAILURE) ScrSnapDir = path to store snapshots as you would need to clear this prior snapshot, sorta like working directory for OCR. Sorry guys was not on this forum here the sample code that works on basic OCR:įirst you make use Katalon API to capture some pictures/snapshots:
If not, then you might consider adding a lay() of a second and try printing the screen again to see if the test check is firing before the toast appears.
I would check that XML to see if the toast shows up there. If you tap on it, you’ll see all of the XML for the screen on the right-hand pane. When the test runs, you should see an entry in the Log Viewer for “Statement - log.logInfo(driver.getPageSource())” that shows the start of the XML for the screen. Then in the code for your test, add the following right after the toast is expected to appear: AppiumDriver driver = MobileDriverFactory.getDriver() Import io.appium.java_client.AppiumDriver You should be able to do that by putting the following import statements at the top of your test case: import .logging.KeywordLogger If you want to see some more detail about exactly what Appium/Katalon detects on the screen you can log out the XML contents of the screen. I wonder if you could log out what Appium thinks is on the screen at the time when the toast appears. You should be able to see in your logs the automationName property of Desired Capabilities whether uiautomator 2 is being used. I didn’t have to do anything special to set that up, though, it seemed to be the default. Note that my tests are using “uiautomator2”, which I think is what’s required for capturing the toasts. Tip: after the article is written, the directory can be generated automatically.Hi able to capture the toast message on an Android emulator using API v27.
0 kommentar(er)
