4 ms·
Ok, I'll bite. How do you integrate with the tested software? Do you a) run the tested software inside your VMs (if so, what's the integration API?) or b) expe
by choeger 5y ago
Ok, I'll bite. How do you integrate with the tested software?
Do you a) run the tested software inside your VMs (if so, what's the integration API?) or b) expect your clients to run it (if so, how can the client authenticate your test access?)
- ukd1 5y agoMostly b, but: a) we can, if so generally they install it as part of the testing (e.g. a client testing a chrome ext), or have us build a custom vm for them (e.g. clients with 20gb download) b) this is the common path; folks push something, ci builds it, ships to a qa env, they run us, if it passes, push to prod. For B, Auth is handled anywhere from zero auth (just fully open QA env, but usually it's SaaS so you still have to login to their app), through to http auth, limiting the IPs (https://help.rainforestqa.com/docs/which-ip-addresses-do-rainforest-tests-come-from https://help.rainforestqa.com/docs/which-ip-addresses-do-rai...), to VPN directly into their QA infra. Without pulling numbers, I'd guess 95% go the zero-auth route.