Why upgrading to the newest Zap-fix version?

[Sasha ZAPModerator]

Hello CurtisDo,

Thank-you for your question.

Basically we recommend to upgrade each ZPX (Zap-fix) to its newly version because the newest versions fix previous bugs and include new features (Which most of them are free to the already prepaid costumers).

For example, the last newly version (14.0.63) contains the following new features:

– JavaScript support (Switch in Test Settings)
– MultiRun Sequential included in ZAP-fiX regular license
– Added detailed errors for external tests that are executed using Runtest method
– Added Runtest execution status into test results

And it fixes the following known bugs:

• Inserting Tests multiple times then opening another one creates slow GU
• Inserting Runtest method does not trigger test changes and the Save button remains disabled
• Changing object properties in Repository Explorer does not trigger test changes and the Save button remains disabled
• Running a saved test will enable the save button after the execution is complete
• TypeEncrypted shows unencrypted text in Results
• Type method: Special keys would not be entered into the text field. For example: % – percentage key would not be typed into a text field.
• Tooltip appears in the wrong place
• Line – wrong line report at error during execution (add +1 to count)
• Results: Expand typo (in expand all)
• Opening old test cases while JS is set, does not switch back to VB and fails run
• opening same test case twice removes syntax coloring
• Insert Call to test has issue – change syntax for JavaScript –
• add Datatable syntaxes to JavaScript
• Sluggish UI Bug after opening many test cases or creating new test cases
• After opening a saved Test Case – "Changes not Saved" dialog would still appear

Please contact Zap for further help.

Thanks,
Sasha

[Author]

Posts