In any software development it is wise to set a 3-stage approach:
See the following diagram to depict the ways a QVW application is moved among stages and the roles of each stage.
QlikView™ 3 Stages Diagram (Development-Testing-Production)
While the Production is clear we should have it (or else we’ve missed the point, right? ), for the first two stages, some aspects should be covered:
But the best option here is to have a sub folder named ”.-PRJ” in the same folder with the application. In that sub folder, all the XML files with metadata of the QVW file (script, variables, interface definitions, actions, macros, etc) will be saved automatically. This one is the most recent available and it brings additional value, especially in a multi-developer environment, through the integration with CVS, SVN or another source versioning solution.
This allows not only version comparison, but also check-in / check-out facilities (avoiding two developers to work in same area and the inherent risk of generating conflicting versions).
2. For the Testing stage, at least 3 perspectives need to be covered:
Assuming there are enough reasons mentioned above to consider the 3 stage approach, the budgetary constraints are still, especially nowadays, a major issue. It is not easy for any kind of organization to double the licensing budgets just to provide this kind of redundancies.
But even under all these constraints, there are good news: the licensing model of QlikView™ is providing a special testing license, named QlikView™ Test Server, that is approx half price of the regular equivalent QlikView™ Server and is providing the same number of CAL licenses as the associated QlikView™ Server (without extra charge for the CALs!).
For the QvS Enterprise Edition this was available for some time already, but there is also now a brand new one, called QvT SBE (Small Business Edition), available since this summer, at a fairly reasonable price point!