# Squish Plugin ## v8.4.1 ### Fixes: - Fix displaying execution summaries generated with the plugin 8.3 and older ## v8.4 ### Enhancements: - Log additional settings and improve the console output readability The global plugin configuration and the --tags extra options are logged in the build's console output now. - Improve reporting on problems with Squish Packages - Store each step result files in a separate directory ### Fixes: - Fix Extra Options handling so other options can be used after --random Before this change, if the --random without a sequence number was followed by another option, the plugin would try to parse it as an argument for the --random option. - Fix circular dependency warning on the plugin startup The plugin automatically generates Squish Tool Installations from the old-style squish installation definitions. This operation was triggered too early and caused the circular dependency warning on the Jenkins startup. - Fix broken Squish report page If a job was configured to run multiple test suites the Squish report page displayed a single test suite multiple times instead of showing a summary for each test suite. - Fix broken test run for multiple suites when Result folder was set The plugin stopped the test run and reported an exception when a job was configured to run many test suites, and the "Result folder" was defined. ## v8.3 ### Enhancements: - Update minimum supported Jenkins version The minimum supported Jenkins version is 2.164.3 now. - Improve console output readability ### Fixes: - Fix showing 0 executed test cases in the console output In some cases the plugin reported 0 executed test cases in the console output even when test cases were executed. - Use a common timestamp for all result files Before that change, some report files might use different timestamps in their names - Fix displaying squishrunner and squishserver logs The log files are displayed in new tabs now. Before this change, if the log contained entries that looked like the HTML tags, the content of the log file might have been displayed incorrectly. ## v8.2 ### Enhancements: - The plugin retries sending results to Squish Test Center. The plugin failed a build in a case of sending results to the Squish Test Center failure. Now the plugin checks if the failure was caused by a database lock and retries sending results if so. - Additional check if an agent is running as a Windows Service By default Windows Services have limited access to displays. The plugin checks is the agent is running as a service and log a warning in the build console output if so. - More verbose logs for Squish Test Center uploads. ### Fixes: - Fix logging info about non-existing buildinfo.txt ## v8.1.1 ### Fixes: - Fix problem with logging scriptArgs - Fix issues with running tests on Linux Agent from Windows Master (and vice versa possibly) ## v8.1.0 ### Enhancements: - Squish Test Center integration The plugin makes sending test execution results to Squish Test Center possible. For more details please check the documentation. Jenkins Plugin - https://doc.froglogic.com/squish/latest/ao-hudson.html Squish Test Center - squish@froglogic.com - Simplify Squish pipeline step definition Limit mandatory options of the Squish pipeline step to "squishPackageName" and "testSuite" - Improve plugin verbosity Improve the plugin console output formatting and log additional information. Add a pipeline stage name to the summary page. ### Fixes: - Fix Environment Variables handling in pipeline Squish steps Before the fix, Environment Variables defined in a pipeline where not usable in all configuration fields of the Squish step. - Fix supporting "\*" or "/*" to define parent dir for suites on remote agents Before the fix, Test suite paths ended with "\*" or "/*" were not evaluated correctly on the remote agents. - Fix wording Fix a few wording issues. - Plugin version number The plugin version should be displayed in Console Output with newer Jenkins versions again. ## v8.0.1 ### Enhancements: - Squish Installations as a part of Global Tool Configuration Global Tools allow easier configuration of Squish installation locations on the different Jenkins slaves. In particular it allows to refer to a particular Squish installation under a single name and map that to different paths on different slaves (in particular on different platforms). The Squish installations defined as part of Squish global configuration will be automatically converted into the Squish Installations. - Squish Pipeline Step It's possible to use Squish Plugin as a regular Pipeline Step. It allows using environment variables defined in a pipeline. That was not possible with a General Build Step. - "Unstable on errors" in a Squish Step configuration If the option is checked, when the error occurs during the tests execution, a build status will be changed to the Unstable instead of Failed. In combination with active Abort on errors option, the job will be aborted after the current test suite is finished but build status will be set to the unstable. - Accept a test suites parent directory in a Squish Step configuration The plugin accepts Test Suite paths ended with the "\*" or "/*". When this kind of path is being used in a job configuration, the plugin discovers sub-directories and run test suites that name starts with the "suite_" prefix. - Make it possible to comment-out test suites. "#" in front of a test suite in a job configuration excludes it from the execution. ---