Frequently Asked Questions

Got a question ?
We may have the answer below, but if not, please contact us
  1. ?

    What does your product suite do ?
    It is a set of tools allowing users to identify the level of quality assurance risk they are carrying, or will carry, on software development projects, or similarly, in operations. Once the present or projected level of risk is known, it can me managed & mitigated. If the level of risk remains unknown, as is often the case, then mitigation becomes reactive, not proactive.
  2. ?

    What information do I need to use your tools ?
    The tools have been designed for simplicity & rapid application. The product suite has three main types of estimation tools. Type 1 & 2 insist that the user input should be functional processes, use cases, user stories or test scenarios. The type 3 tool allows a user to input any sensible metric, provided it is applied consistently. For example, requirements, lines of code, security threats etc., anything at all.
  3. ?

    Are the predictions from your tools reliable ?
    Yes, absolutely. The computational engine was tested rigorously in the field prior to being released to the market. It took fourteen months of R&D, seven years of field testing at client sites & six months of coding to produce versions Alpha, Beta & Gamma. All these versions use the same computational engine, but some functional & user interface differences exist between them. Basically, if the user inputs are correct, the product suite outputs will be correct.
  4. ?

    Are your tools better than others ?
    There are no other comparable tools in the market place that we are aware of. There are plenty of methods available to find via the internet, but no computational tools. The closest thing to a computational tool that we have found are spreadsheets that "say things" but don't actually do much. Even within large multinational consultancies, the best that you'll find is methodology & spreadsheets; no significant science or engineering at all. If you believe in science, engineering & hard numbers rather than sales-talk, then yes, our tools are better than others.
  5. ?

    When can I use your tools ?
    You can use our product suite across the entire software development life-cycle process. It can be applied before a project commences to estimate the maximum number of tests required & the associated risk, or it can be utilized father down the life-cycle track to monitor how much risk the project is presently taking at any specific point in time. If you wish, you can track the risk in real time simply by knowing the total number of tests designed to date. In addition, the tool-set calculates the system-wide coverage & risk associated with an existing test repository (i.e. full regression suite), whilst simultaneously computing the size of test repository sub-set required for a desired statistical level of confidence, at minimal human effort.
  6. ?

    What phases of testing do your tools cover ?
    Our product suite covers all phases. The type 1 & 2 tools are used for functional estimates with respect to system/s integration testing, whilst the type 3 tool is used for unit testing. Indeed, the type 3 tool can be applied to any form of non-functional testing, including performance & cyber-security. We have also included a regression testing calculator, along with a user acceptance testing risk visualization interface. Our product suite is the only tool-set an information technology client needs to perform estimates, & quantify the associated risk, in any project or operational situation.
  7. ?

    Can your tools save us money ?
    Most definitely our product suite can save you money. By knowing how much a project needs to test, & by knowing the percentage risk associated with that estimate, you can act so that you are not testing too much. Conversely, you can also determine if your quality assurance services are not testing enough. Do not presume, like many people, that an information technology service provider has budgeted for an endless stream of testing on your project; they have not. It is very likely that they will not include an estimate for the number of tests to be executed on your project with their tender / bid submission. They may include the number of man-days as information, but this tells you nothing about the quality that they will be delivering. To understand the quality being delivered, you must know the number of tests anticipated to be executed. Clients often expect a defect-free product from vendors, but in reality, what they actually receive is the level of quality assurance which could be achieved within budget & time constraints.
  8. ?

    What is the meaning of your ' ? ' logo ?
    The meaning of our logo is obvious if you look carefully & think about it. You can see that it's a question mark, but you should also see a ruler above a ball of string. This asks the question, "how long is a piece of string ?". As we all know, a piece of string can be any length you wish. This is also precisely the case when testing software. It is possible to continue testing software "forever", the real skill is knowing when to stop. This is exactly what our product suite does, it advises users when to stop testing. Another neat thing about our logo is that the name Testimation forms a keyhole with the ruler. This conveys the notion that our product suite is the key to answering the question - "when should we stop testing ?".