I am writing a s/w testing framework using ruby, it needs to be fast. The amount taking by a browser to start, then shift control to another component and closing is really slow, I was thinking, is there any equivalent fast way to do the same with the same level of confidence, I mean same level of trust/test. As i have heard/studied that the real browser testing is must, it gives the real testing environment. please suggest some faster way, but I dont want to negotiate in the quality of testing as browser gives.
One more thing I would like to know, closing a browser and again starting it for a new test is faster or using the same browser for next test is wise? in terms of times consumption.
Does your testing framework support testing in headless mode in any way? In that way (as far as I know) all of the HTTP traffic is still transmitted and tested, without the need for your testing machine to actually render the graphics in the browser.
If that's not a possibility then I'm afraid you will have to compromise either test coverage or execution speed.
Maybe the best question to ask is: why does your test needs to be so fast in the first place?