This section explains when and how project files that were created or modified in one version of Virtualize can be opened in an earlier version of the product. It applies to the following types of project files:
- .pva
- .pvn
- .changetemplate
Understanding the Available Project File Formats
Project files can be saved in three formats: YAML, XML, and Compressed XML. The following table outlines the key differences between the formats:
File Format | Readable/Searchable | Size |
---|---|---|
YAML† | Smaller than XML / Larger than Compressed XML | |
Compressed XML (deprecated) | Smallest | |
XML (deprecated) | Significantly larger than Compressed XML |
† YAML is the default format unless it was previously set to Compressed XML or XML.
To change the file format used:
- Go to Parasoft > Preferences.
- Open Parasoft > Misc.
- In the Save Settings area, select the desired option.
YAML Files - Forward Compatibility
YAML file format was introduced in version 2024.2. If a YAML project file is created (or opened and saved with minor changes) in a newer version of the product, it can generally still be opened in version 2024.2. Changes involving a feature that was modified or added in a newer version of the product are not considered minor changes.
For example, if version 2025.x provides new options in a certain tool and you change the default values for these options, you will no longer be able to open the related file in earlier versions. If you opened a 2024.2 YAML file in 2025.x, modified options common to both versions and resaved the file, you would still be able to open the file in 2024.2.
In some cases, a YAML project file that was created (or opened and saved with minor changes) in a newer version of the product can still be opened in earlier major versions (for example, a file from 2025.x can be opened in 2024.2) though this forward compatibility across major versions is not guaranteed.
XML and Compressed XML Files - Deprecated and Not Backwards Compatible
XML and compressed XML project files were deprecated in version 2024.2. If an XML or compressed XML project file is created (or opened and saved with minor changes) in version 2024.2, it cannot be opened in earlier versions.
Binary Files - Removed
Binary project file format was removed in version 2024.2. Any modified files will be resaved using the workspace preference except when Load Test modifies a .tst file in which case the original file format will be preserved but it will no longer be openable by an earlier version of the product.
Data Repositories - Forward Compatibility
Certain product releases may change the data format used when adding data to the Data Repository Server. In these cases, data repositories from earlier version need to be migrated as described in Migrating Data Repository Servers. The new-format data repositories (newly created or migrated) cannot be opened in product versions that expect the older-format data repositories.
Backward Compatibility
Project files created in one version of the product can always be opened in newer versions of the product. For example, a suite created in version 9.10.x can be opened in version 2020.x.