10. Our application works on multiple environments. Can you simulate all of them?
Ans. Yes, our test lab is equipped with the state-of-the art infrastructure to simulate the necessary combinations of hardware, software and operating systems. We have successfully tested a eLearning product on multiple platforms, multiple databases, multiple client machines, for our client.


11. How will you ensure this that we have control over the status of the project. ?
Ans. We provide status reports on a weekly basis. Our status reports provide a comprehensive view of the action items in the project. We also have a regular interaction with our customers, to assess the overall status of the project. Further, various ad-hoc reports is presented to the customer as on need basis.


12. We have already invested on a testing tool and want you to use it. Can you help us??
Ans. Yes, our testing team has in-depth experience using a range of industry standard tools such as WinRunner, SilkTest, RationalRobot, QuickTest, Test Complete, LoadRunner, SilkPerformer, WebLoad, OpenSTA, Purify, PureCoverage, Jprobe and Junit. In case you have already invested in any other testing tool, our team has enough expertise to quickly learn and start using the tool.


13. Which tool is most suitable for our automated testing requirement?
Ans. There are several tools available in the market, each addressing specific testing needs. STAG has the experience and expertise to help you identify and select a tool that best meets your requirement and budget. We offer an independent vendor neutral recommendation on the choice of tool from the wide range available in the market today based on client requirement. We have developed a re-usable robust framework for many industry standard tools. This ensures successful implementation, mitigates risks associated with such projects, and reduces costs for our clients. It is also important to note that automating testing is not merely limited to selecting and using the right tool. It is important to understand what areas to automate. It is imperative that one plans a test automation effort well before proceeding. An ad-hoc approach to automation can actually result in longer test cycles and poor quality irrespective of the tool selected.