Is RAMP the right automatic scanning software for me? When should I use Bot Actions?
RAMP's automatic scanning works for most sites, but here are some reasons it may not.
Is the page content readily available and publically available?
- Yes: Great! We foresee no issues, and RAMP should work without configuration.
- Sometimes: Age restrictions, interstitials like cookie banners and ads likely will require the use of Bot Actions to select age, remove cookie banners, close ads, and so forth.
- No: If it's content not publically available some configuration might be required. Please move to next question.
Do you use browser-based HTTP authentication to protect the non-public content?
- Yes: While Bot Actions won't be right for you, HTTP Authentication within RAMP will - get in touch.
- No: Please move to next question.
Do you have testing infrastructure already set up for this application? (Selenium, Cypress, Playwright, etc)
- Yes: We recommend integrating axe-core with your existing tests for automatic scanning.
- No: Please move to next question.
Does your login require multiple steps? (captcha, mfa codes)
- Yes: RAMP cannot currently run automatic scanning on your site.
- No: Please move to next question.
Does your login redirect users to a different domain? This includes subdomains, third party sites, etc.
- Yes: RAMP cannot currently run automatic scanning on your site.
- No: You can configure Bot Actions to submit simple login form with test credentials
Is your content an application workflows (ie highly dynamic applications where "pages" aren't really applicable) ?
- Yes: We do not recommend using RAMP Automated Monitoring.