Note: If you are on a 64bit operating system, we recommend using SQL Server 2008. In that case, please use steps 1 and 2 as a guide only, as SQL Server 2008 has different prerequisites to SQL Server 2005. The prerequisites can be found on the SQL Server 2008 Express download page.
A Step By Step guide to download and install TestCaddy.
Please save all open files before beginning the installation process.
- If you do not have Microsoft .NET Framework Version 2.0 installed on your system, you can download and install it here. If you are unsure whether .NET 2.0 is installed on your system, just download and run the TestCaddy installer, it will advise you if it cannot find .NET2.0. Even if you have a later .NET version installed, you still need .NET 2.0.
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=5b2c0358-915b-4eb5-9b1d- 10e506da9d0f – .Net 2.0 SP2
- If you do not have Windows Installer 3.1 or greater installed on your system, you can download and install it here. It is only required if you wish TestCaddy to install SQL for you or you are installing SQL yourself (see step 3). A restart will be required after installation is completed.
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=5a58b56f-60b6-4412-95b9- 54d056d6f9f4 – Windows Installer 4.5
- Every person who runs TestCaddy in your company should share a central Microsoft SQL Server or
SQL Express instance. It can be SQL 2005 or 2008. So gather the connection details of an existing SQL instance or install one.
- Option 1: Ideally your IT Department will happily supply a SQL Server instance where TestCaddy can create its product databases. It is a good idea for TestCaddy to have its own SQL instance as it will create a TestCaddyMaster database on the server and also a database for each product you wish to test (using a name supplied by the test lead). Before moving on to step 4, record the SQL server name (or IP Address) and the instance name and the username and password to connect with. You will need this information for configuring your copy of TestCaddy and you will need to provide it to other users of TestCaddy in your Company.
Note that the username requires permissions on the SQL server such that it can create databases.
- Option 2: If you would like SQL 2008 or SQL installed
elsewhere on your network you can download and install Microsoft SQL Server 2005 Express Edition Service Pack 2 from here or Microsoft SQL Server 2008 Express from here . It is often simplest to choose Mixed Mode authenticatoin and use the ‘sa’ username and password (refer to the security note). Before moving on to step 4, record the name (or IP Address) of the machine where you installed SQL and the instance name (if relevant). Also the username and password you chose. You will need this information for
configuring your copy of TestCaddy and you will need to provide it to other users of TestCaddy in your Company.
- Security Note:
- Please ensure your TestCaddy SQL server instance is not accessible to outside internet traffic to minimise any security risk. When installing Microsoft SQL Express 2005, the TestCaddy installer uses Mixed Mode authentication. This uses both Windows Authentication and SQL Server Authentication. Windows Authentication is more secure but requires someone who is able to administer the SQL Server instance to integrate with your company’s Active Directory. Hence using SQL Server Authentication and the default ‘sa’ user on the SQL instance is easiest if you are setting up TestCaddy yourself. For similar reasons the TestCaddy SQL installation will start the SQLBrowser service. If security is important to your situation, we recommend asking your IT Department to provide a properly setup SQL server instance for TestCaddy production use.
- While your SQL password should be strong, don’t use a high access (e.g. company administrator) level password because you have to share it with all TestCaddy users.
- Note for 64 bit Operating Systems
- If you are on a 64 bit OS then we recommend SQL 2008 but if you choose 2005 then you will get a warning during the install that Windows recommends installing Service Pack 2. TestCaddy has been tested to run on SQL 2005 on Vista 64bit without SQL SP2, but we still recommend applying the service pack as soon as possible.
- Option 1: Ideally your IT Department will happily supply a SQL Server instance where TestCaddy can create its product databases. It is a good idea for TestCaddy to have its own SQL instance as it will create a TestCaddyMaster database on the server and also a database for each product you wish to test (using a name supplied by the test lead). Before moving on to step 4, record the SQL server name (or IP Address) and the instance name and the username and password to connect with. You will need this information for configuring your copy of TestCaddy and you will need to provide it to other users of TestCaddy in your Company.
- Install TestCaddy
to your system.- Download TestCaddy here
- Running the installer package will place a shortcut both in your Start Menu and on your Desktop.
- Download TestCaddy here
- Click the shortcut link on either your Desktop or your Start Menu to
run TestCaddy.
- The first time it runs, TestCaddy will show a Configuration Wizard which helps you to connect to an existing SQL Server on your network OR you can ask TestCaddy to install an instance of SQL Express for you on the box where you are running TestCaddy.
- Once you have completed the Configuration Wizard and got TestCaddy running for yourself you can provide the SQL connection details to other users. They will need to install TestCaddy and enter the SQL connection details during the Configuration Wizard. You may want to configure a few settings first, so refer to the section in the User Manual on Setting Up TestCaddy for Team Use.
- If TestCaddy installed SQL Express for you the details of this instance (needed by other TestCaddy users) are
- SQL Server: ‘machine_name’\TestCaddy
- Username: sa
- Password: TestCaddy1
Where ‘machine_name’ refers to the machine where TestCaddy ran the SQL installation and can be an IP Address or hostname. If a user is running TestCaddy on the same
box as SQL they can use localhost as the machine name. The instance TestCaddy as indicated by ‘\TestCaddy’. The password is case sensitive.
- The first time it runs, TestCaddy will show a Configuration Wizard which helps you to connect to an existing SQL Server on your network OR you can ask TestCaddy to install an instance of SQL Express for you on the box where you are running TestCaddy.