What's new in JSystem 6.1.11
Mar 3, 2019
- New Features:
- Issue #343 - Add mode to the Difido binder that will support relating to root scenario as single test
- Bug Fixes:
- Issue #344 - Hide in HTML is not working in the Difido reports
New in JSystem 6.1.10 (Aug 13, 2018)
- Bug Fixes:
- Exception in thread "DefaultShutdownHook" while running with JSystem maven plugin
- Java 9 Support - Enable JSystem to run with Java 9
- Multiple selection doesn't save user selection
- Parameters from type parameter provider are not fully shown in the Difido HTML report
- Scenario Parameters are no longer working with JSystem 6.1.09. ArrayIndexOutOfBounds exception appears
New in JSystem 6.1.09 (Dec 21, 2017)
- Bug fixes:
- Issue #307 - Properties from the summary.properties files are read only at the start of the execution
New in JSystem 6.1.08 (Dec 5, 2017)
- Issue #292 - Bean dialog - References usage
New in JSystem 6.1.07 (Nov 24, 2017)
- Issue #292 - Bean dialog - References usage
- Issue #314 - Context menu plugin is working on for tests and not for root scenario, fixtures, flow control, etc..
New in JSystem 6.1.06 (Sep 4, 2017)
- New Features:
- Issue #281 - Adapt the Difido reporter to the refactoring made in the Difido server
- Issue #294 - Allow adding items to the scenario context menu with plugins
- Issue #296 - Allow reading and executing building blocks also from jar files.
- Issue #297 - Remove the "New Features" tab from the properties dialog.
- Issue #303 - Allow building tests project even when it includes no system object project
- Issue #306 - Add the ability to configure the port in the SSH connection of the CLI system object
- Bug Fixes:
- Issue #196 - "scenario.as.test.fail.terminate" feature doesn't work
- Issue #292 - Bean dialog - References usage
- Issue #293 - Bean Dialog - empty input
- Notes:
- This version is compatible with Difido version 2.1.01
- Issue [#196] was caused by the XML reporter. Notice that the behavior of the XML reporter was changed to reflect all the executions since the last init of the reports instead of only the last one.
New in JSystem 6.1.05 (Mar 21, 2017)
- New Features:
- Issue #271 - Add minimum time interval between message to the Difido report
- Issue #273 - Show in the report the number of planned tests.
- Issue #280 - Change the archetypes to get the JSystem version from the properties
- Bug Fixes:
- Issue #272 - The Difido reports are not reading the properties file from the correct directory when running the Maven plugin from a folder which is not the root one.
New in JSystem 6.1.04 (Jul 28, 2016)
- Bug Fixes:
- Issue #266 - JSystem Maven Plugin is always adding the JUnitReporter to the reporter.classes property.
- Issue #268 - Unicode characters are not visible in the Difido server.
- New Features:
- Issue #265 - Make the Difido report the default reporter.
- Issue #267 - We should have a better message in case a wrong scenario is specified to the JSystem Maven Plugin.
- Issue #260 - Scenario properties are not shown in the Difido report.
- Notes:
- The Difido HTML report is now enabled by default.
New in JSystem 6.1.03 (Jul 28, 2016)
- Bug Fixes:
- Issue #258 - Add configuration file for the Difido HTML report..
- Issue #255 - Reference is not working when using with parameter from type string array.
- Issue #239 - ${param} throws “java.lang.NumberFormatException: For input string: "${}" in an int input fields of a BB.
- New Features:
- The HTML report has new colors and it is also a lot easier now to change them to different colors.
- Notes:
- This version works with the Difido server version 2.0.1.
New in JSystem 6.1.02 (Jul 28, 2016)
- Issue #233 - Backward compatibility for flow control values that are stored in the XML file instead of the properties file.
- Issue #241 - 'For Condition' can not read values from references as list parameters.
- Issue #249 - The Difido common dependency is still a snapshot version.
- Issue #250 - At some cases, exception is thrown while trying to parse parameters from type Date.
- Issue #251 - Upgrading from Java 7 to Java 8 breaks the "If condition" building block.
- New Features:
- Issue #245 - Add support for the new abilities of the Difido report server.
- Issue #247 - Change the behaviour of the Difido remote reporter.
- Issue #248 - Add a new tab for configuring the Difido remote properties.
New in JSystem 6.1.01 (Feb 19, 2015)
- Bug Fixes:
- Issue #234 - Remote debugging in Java 8 is not supported
- Issue #232 - When a parameter from type Enum is using a value that is no longer part of the Enum, the value becomes null without proper message
- Issue #229 - Tests archetype generates a wrong package
- Issue #226 - When 'DataDriven' and 'For Loops' building blocks are nested inside other building blocks containers, they are not executed
- Issue #221 - When the test parameter name is changed, the value of the old parameter is kept in the scenario properties file
- Issue #217 - When dropping a BB to the middle of a long scenario, the scenario tree will be scrolled to the top (Thanks for Guy Tal for contributing)
- Issue #216 - When copying and pasting a large amount of building block, the order of the BBs is not kept (Thanks for Guy Tal for contributing)
- Issue #214 - Parameters from type ObjectArrayParameterProvider can't be opened if they include a reference
- Issue #209 - Loop (For each) in inner scenario is always set to default values
- Issue #205 - Data driven is not working with a single line in the CSV file
- Issue #162 - Debug checkbox is not working properly under Linux and Mac
- Issue #77 - Meaningful name disappear from the scenario tree
- Issue #142 - Add cancel button to the remote debugging dialog
- New Features:
- Issue #202 - Introducing a new HTML reporter!
- Issue #228 - Make the maximum number of retries for graceful mode in the cli connection configurable
- Issue #222 - Data driven mechanism should allow adding plugins
New in JSystem 6.1.00 (Mar 28, 2014)
- Bug Fixes:
- Issue #193 - When test class is missing, the runner should continue scenario execution with a correct message.
- Issue #192 - When test method is no longer exists, and executing the scenario from the command line, the method name doe's not appear
- Issue #191 - When test method is no longer exist, the missing test should be considered as error and not as warning
- Issue #189 - When adding a scenario that include scenario as test to another scenario, the scenario as a test is always mapped
- Issue #167 - Parameter providers values are empty under Linux and Mac
- Issue #184 - The name of scenario that is marked as test does not appear correctly in the JUnitReporter (Thanks goes to Vincenzo Marrazzo from Sony-Ericsson for the contribution)
- New Features:
- Enhancement #106 - Data driven support - Read a CSV file and execute a scenario the number of lines in the file. In each iteration parameters will be created with the titles as names
- Enhancement #187 - Add support to the Maven plugin for running multiple scenarios with various SUT's
- Notes:
- IMPORTANT : Issue #185 - JSystem is now complied with Java compliance level of 1.7. That means the Java 7 features can now be used in the automation projects, but JSystem can no longer run with JVM lower then 7.
New in JSystem 6.0.00 (Feb 18, 2013)
- Support for Maven projects!
- Groovy support. JSystem now supports writing tests and system objects in the Groovy language
- The ReportElement is now synchronized and there is a new service in ReporterHelper that helps to report element from specific originator. This is useful for concurrent reporting.
- New implementation for the publish event and a new interface for the publishers When switching projects, the user can now select the project root folder and JSystem will automatically find the classes folder.
- Cli system object supports authentication of SSH sessions by keys.
- Support for init/flush the reports from the tests JVM.
- Notes:
- JUnit reporter was added to the default reporters in the reporter.classes property.
- JSystem code was ported to GitHub
New in JSystem 5.7.02 (Aug 16, 2012)
- New Features:
- Support for scenario properties caching for faster scenario loading (experimental)
- Delete scenario feature:
- Toggle debug mode
- Faster log zipping
- Better reporting for loops inside scenarios that are marked as test
- Bug Fixes:
- Bug Fix 3525124: last 'scenario as test' in not shown in report in cli mode. As a blessed side effect the endRun event works now in command line mode.
- Bug Fix 3554724: 'mark as negative test' doesn't work in 'scenario as test'
- Notes:
- The report server configuration details were moved to the JSystem properties dialog
- Few changes were made in the third party dependencies
New in JSystem 5.7.01 (Apr 23, 2012)
- New Features:
- Added JunitReporter. This reporter mimic the behavior of JUnit Ant report The result XML can be read from any CI (Jenkins/Hudson) systems. To use the reporter add it to the property reporter.classes. The XML will be created in the log folder.
- Bug Fixes:
- Bug Fix 3459986: Reports are not created when running tests from IDE
- Bug Fix 3459990: Test parameters are not shown when running from command line
- Bug Fix 3462942: Test documentation from the scenario tree doesn't support EOL
- Bug Fix 3482156: Sometimes test description is not refreshed in scenario tree. Notes
- Added support for Java 7
- Removed the Selenium libraries from the installation package
New in JSystem 5.7.00 (Apr 23, 2012)
- New Features:
- Major improvement in the scenario tree performance.
- Added test/scenario information view to the tests tree.
- Added support for AND,OR operators to the tests tree search box
- Test parameters are now shown as disabled in execution time.
- The modify file dialog was added to a condition on which the user tries to save scenario with name of an already existing scenario that is in read only state. Bug Fixes:
- Bug Fix 3434092: Sub scenarios parameters are saved with no reason.