Instructions for installation on a web server
From TestMaker-Wiki
Contents |
Set testMaker
- Open a browser and type in the address bar the link to the public testMaker directory. You will ger this link from your provider.
- As described in the message you call the installer by clicking the appropriate links.
- First, you can still change the language. Then click on "Start installation or update".
- You need the following required data from the provider:
- Database type
- Database hostname
- Database name
- Database username
- Database password
- Prefix for all tables: change if there is already a testMaker installation available in the same database
- System e-mail address: enter your own e-mail address (that which testMaker should use for sending mail identification and error messages).
- select "Save"
- Then select "Create an administrator access"
- Enter data for first user and register (the first user gets the user ID 1 and is super-user, ie it has all available rights and can not be removed from the system)
- Then log in: Finished!
Update testMaker (from testMaker 3.0 to testMaker 3.3)
Background info: If some time has passed since the download of testMaker there are now probably a more recent version of testMaker. Therefore, it is possibly useful tu update testMaker before starting to work with it. However, a testMaker installation should only be updated if a newer (stable) package version is available (for example, the version 3.3). To decide whether you want to update your testMaker, you can read up on the changes.
To upgrade testMaker from version 3.0 to version 3.3 following steps are necessary:
Back up and taking offline of the current version of testMaker
- Since testMaker 3.3 includes changes on the database, it is advisable to make a database backup before the upgrade. To be sure, even before the update, a copy of the test makers can directory be created. Thus in case of emergency the entire update can be reversed.
- If a testMaker version is used publicly, it is also important that no one (participants, authors) has access to testMaker during the update. To ensure this you can
- temporarily rename the main directory of testMaker, for example, in tM_update or
- create a "htaccess"-file to block the access
Download and installation of version 3.3
- Now you have to download the latest package version of testMaker (version 3.3) from http://sourceforge.net/projects/testmaker.
- After that the zip file has to be unzipped (for example with the help of 7-Zip).
- Transfer the unzipped files and directories to the already existing testMaker directory on the public web server (such as FTP or WebDAV). The existing files and directories of the old testMaker version will be overwritten. If necessary the overwriting of files has to be confirmed. Test runs, user accounts etc.which are saved in the database will remain the same. It also remains the configuration file, so that you can continue working after the update as usual.
Start version 3.3
- Open testMaker in the browser in the usual way. There appears an update dialog that gives some instructions for the update. After a few clicks the database structure and the test run structure are automatically adapted and the test runs compressed. This process may take very long for lareg databases(about an hour per GB).
- If the script is finished, you can test the updated version of testMaker.
- Now you only have to remove the blockade so that participants and authors have access again.
