Your decision to use Skiva to create test tools has several advantages and benefits. The major reason for implementing tests is to improve the quality of the products and systems that are in play. However, the best software may have design flaws that would interfere with its acceptance by the general public, as a result of which our processes are designed to bring the necessary tests in to play, to identify the best tests to quantitatively describe, and to determine results for the process. You should note that test tool acquisition is also a part of the process.
Acquisition of the tools needed to perform reliable testing may be marketplace driven, or may be created for specific needs and clients. However, at Skiva we have learned that the decision about which tools are needed is best done by those with the expertise to look at the processes which must be tested. There are industry standards, but matching the test tools available with the products and processes which need to be reviewed is where the skill and knowledge of the consultant comes to the fore.
We recognize that there are immediate needs to review a particular product or system. In addition, most of our clients like to be able to increase their knowledge about the tools and processes as well as the specific product, so the final form of testing may be a melding of outside assistance and internal testing procedures.
Our experience at Skiva tells us that testing tools which are modular in nature allow for certain portions of the testing to be done by automated software-testing-services, thus ensuring that there is a seamless interface between the testing modules as this relies wholly on first class pre-planning, design and strategy.
