Would be better to hire professional QA engineers for this. hey usually get to work by making contacts with various service providers who require app developers and website developers. These service providers then provide them with work to complete.
QA has nothing to do with this explanation. The QAs in the company that i work for usually test the hell out of the new functionality that developers like me code. A QA is so useful because thinks in every single edge that the functionality could break. I dont understand the comparison in this context.
Couldn't the very fact that a proxy is being tested "burn it" so that upon next request it is down?
Anyways, we also used the tool to see how our application held up under high load, and it was very effective in finding bottlenecks. The tool has built in reporting to show how long requests are taking, but we never used it. The logs can also store all the responses and whatnot, or custom logging.
Comments
I dont understand the comparison in this context.