Upgrade issues between v3 builds

[borderblaster]

Hi

Our test team are currently using testlog v3 build 1010. We would like to upgrade to build 1011 to take advantage of the bug fixes and enhancements in it. We are cautious however because build 1010 seems reasonably stable and sometimes one is better off with the devil they know. The main worry is that if we went to build 1011 and it has problems and is unstable, we could not revert back to build 1010 because if we open a database that has been edited using a newer v3 build of testlog a message appears saying database cannot be opened please upgrade to newer version.

Do passmark have a disaster recovery solution in place for this kind of scenario? Corruption of the database at this stage of our project would be painful.

[Tim (PassMark)]

There isn't any automated backup/roll-back procedure so you should backup your database before installing the new version. There weren't any structural changes to the files between those two builds so it shouldn't affect the database too much.

If you make changes to the database and then need to revert back to the older build, you will need to replace the ".tdb" file of the database with one from the version you will be using, so create a new empty database with the old version and copy the ".tdb" file from it to the database edited with the new version, now the database should be able to be opened with the old build.

If you have been using the web module there are currently 2 known issues that will be fixed in a release next week;

- Some malformed HTML in the project test case edit for the Test Phase field, causing the currently selected phase to display/save be saved as blank.
- Some more changes to the automatic redirection in TestLog to work with HTTPS