Click on the 'Download' button on the menu bar above. On this page accept the EULA and you will be taken to the downloads page.

For detailed installation instructions, discussion of prerequisites and security notes refer to this page

TestCaddy has been designed for a minimum screen resolution of 1024 x 768 pixels.

 
 
Minimum Platform Support:
  • Windows 8, Windows 7, Vista SP2, or XP SP2
  • Windows 2003 SP1, Server 2008, or Server 2008 R2
  • 32 or 64 bit (TestCaddy is a 32-bit application)
Requirements:
  • Microsoft .NET 2.0
  • Microsoft SQL Server 2005 or 2008 (Full or Express Editions)
  • Microsoft Internet Explorer 8.0 or above (used by browser windows within TestCaddy forms)
  • Approximately 32MB Available Memory
  • Approximately 100MB Free Disk space
  • Windows Installer 3.1

Note: The full TestCaddy installation package includes Microsoft SQL Server 2008 Express Edition. It has the following higher prerequisites:

  • Windows Installer 4.5
  • Microsoft .NET 3.5.1

Both packages will optionally download and install the required Windows Installer and DotNet prerequisites for you. On older boxes this may require up to two restarts, so you may wish to install them manually first on such boxes.

If you are unsure, try just installing TestCaddy as it will tell you if .NET 2.0 or MSI 3.1 is missing from your system. Likewise asking TestCaddy to install SQL Express will tell you if you are missing .NET 3.5.1 or MSI 4.5. The installer can optionally install these missing pre-requisites for you if you wish. For further details on the pre-requisites refer to the Installation Detail page.

Yes, we now fully support Windows 7 and 8.

Make sure you have defined the path to the database correctly.

If you used the automated install of SQL Express using TestCaddy's Configuration Wizard, this path would have been set by default. This should read "localhost\TestCaddy". The username is 'sa' and the password is 'TestCaddy1'.

Some SQL servers use an instance name, e.g. SQLExpress, so you specify the server as machine_name\instance_name , e.g. machine2\SQLExpress. Some SQL server have no instance name and so you just specify the machine name, e.g. machine2

It can take quite a while for SQL Express to install. Perhaps even 20 minutes on slower boxes. TestCaddy allows up to 1 hour before quitting the installation. So have a look in the SQL install log file to see what is happening. SQL installation logs can be found in this location,
%ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt
where %ProgramFiles% is typically c:\Program Files

You can install multiple Instances of SQL Express on one box.
If you are having trouble getting SQL Express to install via TestCaddy's Configuration Wizard, it may be best to download the SQL Express installer package from Microsoft (there is a link on our download page) and install it manually. Then when you install TestCaddy you can just enter the location and login details for the SQL instance you manually installed.

Your SQL location and login details can be edited in TestCaddy at any time by going to the Database Manager window found on the File menu.
If you ever want the Configuration Wizard to come back, simply delete the TestCaddy.ini file from your TestCaddy data folder (see separate FAQ for location of this folder). Note: You will need to enter the SQL server location and username and password again, but not much else is stored in that ini file.

On a default installation of SQL 2005 or 2008 Express the SQL Browser service is not started for security reasons. This makes it harder for TestCaddy running on another machine to connect.
To remedy this, either:

  1. The browser service needs to be started or
      To start the SQL Browser service: Click on Start, Run and enter "services.msc". Once the Services control starts, locate the "SQL Server Browser" and right click it and select Properties. Set the startup type to Automatic.
  2. The SQL instance needs to be configured to listen on a TCP/IP port.
      To configure your SQL instance to listen on a TCP/IP port: Open "SQL Server Configuration Manager", (shortcut is usually created in the start menu under Microsoft SQL Server folder) Open "SQL Server Network Configuration" and then "Protocols for InstanceName" (where instance name is the name of your SQL server). Double click "TCP/IP" and on the drop down menu next to enabled select "Yes", You will need to restart your SQL server for the changes to take effect.
      TestCaddy also needs to be given that port as part of the server details (in the Configuration Wizard, or if your TestCaddy is already connected to a server you can use File -> Database Manager -> Change), which is done by appending a comma followed by the port number to the server name without the instance name, e.g. if the port number is 1433 (this is the default port) and full SQL instance name is 1.2.3.4\SQLExpress then for the Server field enter, 1.2.3.4,1433

The following Microsoft KB discusses this for SQL 2005,
http://support.microsoft.com/default.aspx?scid=kb;EN-US;914277
but there doesn't seem to be a similar official article for 2008. The following article may be some help,
http://www.linglom.com/2009/03/28/enable-remote-connection-on-sql-server-2008-express/

If you ask TestCaddy to install SQL Express 2008 for you it will try to start the SQL Browser service. If it can then it will set the SQL Server connection details to use the IP Address of the machine. If it can not, then it will use 'localhost' and present the warning that begins, "Could not start SQL Browser Service" which directs to this FAQ.
The SQL Browser service may fail to start if there is more than one instance of SQL on the box, e.g. side-by-side SQL 2005 and 2008 installs. In any case the issue should be able to be resolved. Contact TestCaddy technical support if you'd like help with your particular situation. Also Note: Your firewall might also prevent remote connections. Sqlserver.exe and sqlbrowser.exe need to be added to firewall exceptions in order for SQL 2008 Express to accept remote connections. Refer http://blogs.msdn.com/sql_protocols/archive/2006/09/30/SQL-Server-2005-Remote-Connectivity-Issue-TroubleShooting.aspx



Yes, SQL 2005 can be installed on 64 bit operating systems and used with TestCaddy but it is not recommended.

On 64bit operating systems, SQL 2008 is recommended. Use our package which includes SQL2008 Express or before installing TestCaddy, download and install SQL Server 2008 Express, then install TestCaddy and point it to the installed SQL Server 2008 Express.

On the other hand, if you still wish to use SQL 2005, we have tested TestCaddy on Vista 64 bit using SQL 2005 Express without Service Pack 2 and it appears to operate without failure, however we recommend applying SQL 2005 Service Pack 2 as soon as possible after your TestCaddy installation.

When applying Service Pack 2, note that you must be careful to follow the instructions given in this FAQ, as you could end up with a 'SQLExpress' instance alongside your TestCaddy instance, rather than upgrading it.
If you or someone in your organisation has recently upgraded TestCaddy to a new version then you may get the following question:

---------------------------
Upgrade Database?
---------------------------
The SQL Server which you are connecting to has an older TestCaddy database version and needs to be updated in order to continue. If you choose No, then you will be able to select another SQL server or exit the application.

Would you like to upgrade your database now?
Note: We highly recommend that you backup your database first (see the FAQ section of our website if you need instructions).
---------------------------
Yes No
---------------------------


This message occurs because TestCaddy has a database version system and it knows the version of database that it has been coded to work with. So if the Product Database (or TestCaddy's Master database) is still from an older version then when you try to connect to it with TestCaddy you will get the message/question above.


Ideally your administrator should install the new version of TestCaddy when others are not using TestCaddy and perform the necessary database upgrades for you. Refer to the Upgrading FAQ on this page.


If your administrator or someone else in your team has upgraded the databases but not given you the latest version of TestCaddy, then you will get a similar message where TestCaddy complains that you need a newer version in order to be allowed to connect to the databases.


Usually all Product Databases on your SQL server will be upgraded at once, but the situation can arise where some Product Databases are upgraded and others aren't. This isn't an issue, TestCaddy will simply offer to upgrade each database when someone tries to connect it.
As mentioned in the message, you should backup your SQL databases before allowing TestCaddy to do any uprading. Refer to the separate FAQ on this page for how to do this.

In order to backup TestCaddy, you need to backup the main TestCaddyMaster database on your SQL server and all the Product Databases you have created.
You can also backup the ini file on each box where TestCaddy is installed, but this only stores the SQL connection details (and a few defaults) which are fairly easy to enter again if needed.
You can backup your SQL databases in any standard way. Typically you can do this via Microsoft SQL Management Studio (R) or automate it with a batch file and sql script file run by a scheduled task. Details on these can be found at this Microsoft link, http://msdn.microsoft.com/en-us/library/ms191304.aspx
 
A simple batch file, TestCaddyBackup.bat might look like this:
sqlcmd -S localhost\TestCaddy -U sa -P TestCaddy1 -i TestCaddyBackup.sql
And the TestCaddyBackup.sql file which backs up the TestCaddyMaster database as well as a product database called MyProductA might be,

BACKUP DATABASE TestCaddyMaster TO DISK='c:\TestCaddyMaster.dat'
go
BACKUP DATABASE MyProductA TO DISK='c:\MyProductA.dat'
go

  1. Backup your TestCaddy Databases (refer separate FAQ)
  2. All users should close TestCaddy
  3. Run the installer for the new version of TestCaddy on one box where you already use TestCaddy.
  4. Run the new version of TestCaddy. It will tell you that the databases need to be upgraded and ask if you wish to do the upgrade now. If you select Yes, it will upgrade the TestCaddyMaster database and all the Product Databases. You can obviously opt out at this point, e.g. if you haven't yet done your backup.
  5. Upgrade TestCaddy on all workstations where users run TestCaddy. If a user hasn't upgraded TestCaddy it will complain that the database version is newer than TestCaddy supports and will prevent logging in.

Note: If for some reason one Product Database does not get upgraded at this point in time (e.g. you have taken it offline), then when someone next tries to connect to it with TestCaddy, then TestCaddy will offer to upgrade just that one Product Database.

What if the worst happens?
If anything goes wrong with the upgrade, you will return to the message about the databases needing to be upgraded. You can select No at this point, Exit the Application and send your log and configuration file to Technical Support (see separate FAQ on their location).
You can revert to the old version of TestCaddy by restoring your database backups, uninstalling the new TestCaddy and re-installing the old TestCaddy. It will find your original ini file and operate as before without needing to re-run the Configuration Wizard.

 
TestCaddy stores an INI file for all users on a workstation in a folder below the Common Documents folder.

The INI file is a text file which stores a few configuration details for the local copy of TestCaddy to read when it starts up. It stores your SQL Server connection details, the last user logged in and the last Product Database you connected to.
TestCaddy also stores a text log file for each user in the same folder. The log files have the username as part of the filename, e.g. TestCaddy_BobS.log.
The INI and Log files are useful to send to Tech Support if you are emailing about an issue.
The files can be found in the following folders:

On Windows XP:
%ALLUSERSPROFILE%\Documents\TestCaddy
(typically C:\Documents and Settings\All Users\Documents\TestCaddy )

On Windows 7 and Vista:
%PUBLIC%\Documents\TestCaddy
(typically C:\Users\Public\Documents\TestCaddy )

TestCaddy ensures that all users (Everyone) has full access to the INI and log files.
It should not be required, but you can edit the INI file with a text editor (best done when TestCaddy is not running). You can also delete the ini file if you want the Configuration Wizard to show when you next start TestCaddy.

Yes you can run multiple copies of TestCaddy. This is often useful. Note that only the first copy will log to the text logging. TestCaddy will also warn you if you try to run the same test in two copies of TestCaddy at once, just as it would if two different users tried to run the same test at once.

You should not normally need to run TestCaddy with Administrator privileges on Vista. It will need to be installed by a user with the rights to install applications, and if it is most convenient to use the Administrator to do that then that will be fine. End users on the box will not need to re-run the Configuration Wizard because there is one common INI file for all users on a box.
Multiple users can run TestCaddy on one box at the same time (e.g. using Vista's switch login feature). In that case they share an INI file so only one will need to run the Configuration Wizard.

Firstly, you must download SQL Server 2005 Express SP2, which can be found here. Once downloaded, follow the instructions below. Please note: SQL Server 2005 Express with SP2 comes as a full version. Therefore, please follow steps 3 to 5 carefully, as failure to do so can result in an additional instance of SQL Server being installed alongside your TestCaddy instance, rather than upgrading the existing SQL instance.

  1. Stop existing SQL Server
  2. Start installing SQL2005 Express SP2 (Open the installer file), and proceed with the SQL Server Configuration Wizard.
  3. At the Registration Information screen, untick 'Hide advanced configuration options', click 'Next'.
  4. At the Instance Name screen, click 'Installed instances', and choose an existing instance (e.g. TESTCADDY if SQL Server was installed through TestCaddy). Click 'Next'. Note. If you DO NOT do step 4, the existing instance of SQL will not be upgraded to SP2 (see note above).
  5. At Existing Components screen, tick all available options. Click 'Next'.
  6. Proceed through the rest of the Configuration Wizard with defaults* until configuration is completed. * You may change other details if desired.
  7. Reboot system.

Here is a link to a complete script for backing up your TestCaddy databases on a SQL server. Be sure to read the Readme.txt file in the zip file and follow instructions on changing the few configuration settings in the script. The script must be setup as a Scheduled Task on the box running SQL Server. It does the following:
  • Creates a backup of all TestCaddy databases on the specified SQL Server, and stores the files in a local location. The script backs up the TestCaddyMaster database and any TestCaddy Product Databases on the SQL Server.
  • If a remote location has been specified, the script copies the files to that location ready for backing up via your normal file backup strategy.
  • Deletes the backup files that are older than two weeks (note this can be changed).
We recommend using a VPN to your office.  TestCaddy is tested over a VPN connection with high latency. A second option is you can connect TestCaddy to a remote SQL Server by using Stunnel to encrypt the data that is being transferred. Stunnel is an open source, free to use program that allows you to encrypt arbitrary TCP connections inside SSL. This is a good option for a small satellite office without a permanent VPN connection to the head office. If you would like to setup Stunnel to use with TestCaddy, please download our Stunnel Guide, as it contains detailed instructions on where to get Stunnel from, and how to set it up.
Error193

Error193





These errors are due to not being connected to the internet, the installer downloads and installs the MSI pre-requisite if it is not on your system and to do this it must be connected to the internet.

To resolve this issue you must either connect to the internet and run the TestCaddy installer again or install MSI manually. MSI can be downloaded here.

Firstly, you must download SQL Server 2008 Express SP3, which can be found here. Once downloaded, follow the instructions below. Please note: SQL Server 2008 Express with SP3 comes as a full version.

  1. Stop existing SQL Server (through SQL Server Configuration Manager)
  2. Start installing SQL2008 Express SP3 (Open the installer file), and proceed with the SQL Server Configuration Wizard.
  3. At the Select Features screen make sure that the box next to your SQL server instance is ticked (if installed by TestCaddy the default name is TESTCADDY). If this box is not ticked then your TestCaddy SQL instance will not be updated and a new SQL instance will be installed alongside your existing one.
  4. Proceed through the rest of the Configuration Wizard, following the Configuration Wizards default path will update your SQL successfully.
  5. Restart your SQL server (if your SQL server start mode is set to automatic then rebooting your system will have the same effect).

If you wish to add a new option to the X or Y axis when editing a Saved Graph, you need to create a new GraphSet which defines the options, the SQL required to get the data to be graphed and what database field name each option uses.

The built in Graph Sets can be exported to XML, edited (with a good text editor) and then re-imported.

The TestCaddy Tech Support team can assist with this or if you are proficient with SQL and XML you can do this yourself.

Note that you may want to add your options to an existing GraphSet XML file so that your new options are available at the same time as existing options.

You should always change the Name field of the XML file to avoid confusion. On import every GraphSet will be given a unique ID but conflicting names can be confusing.

The basic layout of the XML file is

The Reports window has a Manage Templates link which lists the current Report Templates available and allows you to export existing Templates and import new Templates. You can also De-Activate templates which prevents them from being used in a new report.

The Templates are standard HTML and JavaScript with template variables which get replaced with the various elements like the Saved Graphs when they are displayed.

You can export existing Templates, edit them with a good TextEditor and then re-import them and either change existing reports or add new reports to use the new Templates.

The variables available are:

First, check the Microsoft KB http://support.microsoft.com/kb/931712

If these suggestions don't work, some customers have also reported success by following;

"In the Administrator: Command Prompt window, type the following commands. Press the Enter key after each command:

DISM.exe /Online /Cleanup-image /Scanhealth
DISM.exe /Online /Cleanup-image /Restorehealth"
- From http://answers.microsoft.com/en-us/windows/forum/windows_8-windows_updat...

To Uninstall TestCaddy simply open the control panel and click "Add Remove Programs", locate TestCaddy and click the uninstall button.

This will not remove the .INI file or reg keys which can be manually removed by following the FAQ here.

TestCaddy creates an installation folder in "C:\Program Files\TestCaddy" that can be manually removed by selecting and deleting it.

TestCaddy creates an installation folder and a log file folder which can be manually deleted and found through the FAQ links above.

TestCaddy creates 2 Reg Keys on installation which can be manually deleted by using Run > regedit and finding them in the treeview under;

HKEY_LOCAL_MACHINE (or HKEY_CURRENT_USER)/SOFTWARE/Microsoft/Internet Explorer/Main/FeatureControl/FEATURE_BROWSER_EMULATION/TestCaddy.exe

AND
FeatureControl/FEATURE_BLOCK_LMZ_SCRIPT/TestCaddy.exe

These Reg Keys do not effect any existing programs apart from TestCaddy and help with compatibility issues. More information can be found on this Microsoft KB article.

TestCaddy contains no bundled Adware or software (apart from the optional Microsoft SQL server)

Symptom Details:

TestCaddy operates correctly most of the time but from time to time an action like simply selecting a test to view will take 20 seconds or more to complete.

If you were to analyse performance with SQL Profiler you would see Execution Errors like this:

<MemoryGrants xmlns='http://schemas.microsoft.com/sqlserver/2004/07/queryprocessor' Version='1.0' Build='10.50.1600.1'>
	<Grant>
		<SPID>54</SPID>
		<BatchId>0</BatchId>
		<SQLHandle>0x03000A000DD07C4F5991010152A000000100000000000000</SQLHandle>
		<PlanHandle>0x05000A000DD07C4F40214782000000000000000000000000</PlanHandle>
		<MemoryRequested>573</MemoryRequested>
		<MemoryGranted>0</MemoryGranted>
		<MemoryUsed>0</MemoryUsed>
		<DOP>0>/DOP>
		<TimeOutInMS>25000</TimeOutInMS>
		<MemoryRequestTime>2012-05-30 07:33:19.89</MemoryRequestTime>
		<MemoryGrantTime></MemoryGrantTime>
	</Grant>
</MemoryGrants>

This issue is logged in our system as ticket TC-770. To workaround the issue simply ensure that the SQL Server has a minimum Memory amount set, so that it can get memory grants quickly. We recommend a minimum of 500Mb. It is also a good idea to set the Maximum memory SQL can use so that there is plenty of memory for the Operating System as per this article: sql-server-optimal-memory-settings. Typically TestCaddy runs well with a minimum of 500Mb and a maximum of 2048Mb (assuming your machine has say 3Gb of RAM).