Customers with a valid Maintenance Agreement will get all upgrades for the licenses/ product variants, they have bought, without additional costs (besides full support).
Just download the latest QF-Test version from our homepage:
When we release a medium- or major upgrade, it is necessary to request the actual license file:
The purchase of further GUI-technologies (Java Swing, SWT, JavaFX, Web) is always possible.
A major upgrade refers to the "first" version number, e.g. from 3.5.7 to 4.0.0, a medium upgrade to the version number in the "middle" , e.g. from 4.0.0 to 4.1.0. Users with a valid Maintenance Agreement are authorized to do each QF-Test upgrade for free (besides full support).
QF-Test version numbers consist of three parts, major~, medium~ and minor version. QF-Test licenses are generally valid for all minor versions within the same major.medium version, plus all older QF-Test versions.
Upgrades without Maintenance: Customers without a valid Maintenance Agreement can buy QF-Test upgrades to the current version. QF-Test upgrades cost from 20% to 40% of the actual license price.
There are different ways of handling the life cycle of software that, like QF-Test, is widely used in production environments while continuously being maintained, improved and extended. You find the newest features of the versions in the Release Notes. For the current QF-Test version 4 and further ones, we decided to go to the traditional "Beta" concept. Therefore the life cycle for a QF-Test version is as follows:
Development never stops. While the latest version is still being maintained, a new version evolves. When a number of new features has matured, typically a first Beta version is released, for example 4.0.11-beta1. More Beta releases with additional features may follow.
The version of QF-Test currently under development is the one that undergoes the most testing and generally can be considered as rather stable.
A helpful feature of Beta releases is, that during a limited time span, they can be used with a license valid only for the previous release, giving users without maintenance a chance to evaluate the new version without committing to anything.
Once the feature set of the new version is ready, one or more release candidates like 4.0.11-rc1 may follow where typically only minor details may differ from the final version.
When finally ready, a "dot-zero" version is released, 4.0.0 in this example. Having been available in the form of beta versions and release candidates for some time and not to forget our own "Quality First" test-automation efforts, QF-Test "dot-zero" releases are quite mature.
Maintenance releases like version 4.0.11 are released at irregular intervals, mostly to fix bugs but with extensions to the current feature-set. In case of a severe bug a maintenance version will be released as soon as the bug is fixed.
Sometimes small but annoying bugs are discovered soon after a release. They don't warrant a new release but are important enough to take care of. In such a case patch versions like 4.0.0-p1 are released to provide the latest changes to those who need them. Patches are announced on the QF-Test mailing list only (more about the QF-Test mailing list).
During development of new features or bug-fixes it is often necessary to solicit feedback from users. To that end, experimental patches are sometimes released to individual customers or, if of general interest, via the mailing list.
A patch is a very small set of changes relative to a given QF-Test version. It is provided in the form of a ZIP archive which is extracted over an existing QF-Test installation. There is only one ZIP file for all operating systems and installing a patch causes far less overhead than upgrading to a new QF-Test release.
A patch is always a temporary solution. The next full maintenance release will include all working fixes from patches since the last release and thus supersede previous patches.
We always run a full set of tests against official patches. However, due to the shorter release cycles patches cannot be quite as well tested as full releases. If you encounter problems after installing a patch, you can usually disable the patch by removing the file .../qftest/qftest-x.y.z/qflib/patch.jar. Please report all problems with patches to qftest-bug@ or to the mailing list. qfs.de