Replies: 2 comments 5 replies
-
Hi @avarama. Did you try viewing the Selenium browser to see what's actually happening? Yes there are waits. Next step after just seeing what's happening with the Selenium browser would probably be to debug the Cucumber sub-process. Les us know how that goes or if you need any more pointers? |
Beta Was this translation helpful? Give feedback.
1 reply
-
Hmm, that could be a problem. There's no global wait timeout for webdriver or waits specified in Job file. Any waits should be be in: https://github.com/purpleteam-labs/purpleteam-app-scanner/blob/main/src/clients/browser.js |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Is there a way to slow down the underlying selenium interactions with the web app? I guess it is designed to wait for elements, but I'm suspecting purpleteam is timing out before my elements are drawn. Is there a configuration for the delay between steps, or any directive to specify specific waits? Thanks!
Beta Was this translation helpful? Give feedback.
All reactions