-
Notifications
You must be signed in to change notification settings - Fork 48
Release Notes
Itai Agmon edited this page Jun 14, 2016
·
29 revisions
- 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
- 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
The Difido HTML report is now enabled by default.
- 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
The HTML report has new colors and it is also a lot easier now to change them to different colors
This version works with the Difido server version 2.0.1
- 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
- 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
- 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
- Issue #202 - Introducing a new, advanced, modern HTML reporter! For instructions how to use it please refer to this blog.
- 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
- Issue #166 - Upgrade package XML-APIS from 1.0.b2 (jsystemApp) to XML-APIS 1.4.01 for better integration with Webdriver
- 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)
- 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
- 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.
- Issue #183 - 'Mark as Known Issue' is not working properly when executing from the command line
- Issue #180 - Run properties doesn't work when running via JSystem Maven plugin not from the tests project folder.
- Issue #169 - 'If' condition is not working when executing with JSystem Maven plugin
- Issue #99 - For loop parameters are saved in the XML instead of the properties file
- Issue #98 - Reports are not correct when test method is no longer exist
- Issue # - When creating test project from the archetype, The test project artifact is now excluded from the lib folder. This causes changes in the tests to be updated in the runner UI without rebuilding the project.
- Enhancement #174 - Deploy JSystem runner as ZIP file in addition to the tar.gz file
- Enhancement #173 - Add link from JSystem runner to the on-line documentation
- Enhancement #171 - Removed the POI library from JSystem dependencies. The library is longer required because the feature that enables editing scenarios from Excel file is deprecated. This change will allow users to use advanced POI versions in their projects.
- Added the reporter helper method reportByOriginator to use in concurrency reports as described in the blog
- Fixed a null pointer exception in the StringBufferParameterProvider class
- Fixed the linux runBase bash script to allow JSystem debugging under Linux.
- Fixed the case on which scenario s had a scenario s' that was marked as test and scenario s is included in scenario s'' then scenario s' was no longer marked as test.
- IMPORTANT: The Maven repository server was changed in this version to maven.top-q.co.il
- Minor changes in the reporting of the multiple scenario executor when XML file is not found
- 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. 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. (Thanks for Liel Ran for the contribution).
- Support for init/flush the reports from the tests JVM.
- JUnit reporter was added to the default reporters in the reporter.classes property.
- JSystem code was ported to GitHub
- Support for scenario properties caching for faster scenario loading (experimental)
- Delete scenario feature (Thanks to Hadar Elbazz for the contribution)
- Toggle debug mode (Thanks to Or Rubin for the contribution)
- Faster log zipping
- Better reporting for loops inside scenarios that are marked as test
- 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'
- The report server configuration details were moved to the JSystem properties dialog
- Few changes were made in the third party dependencies
- 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 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.
- Added support for Java 7
- Removed the Selenium libraries from the installation package
- 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 Fix 3434092: Sub scenarios parameters are saved with no reason.
- Added ‘reset to default’ feature. User can can revert scenario/test parameters to the default values. (Thanks to Limor Bortman for the patch)
- Added ‘edit only locally’ feature that allows the user to set scenario to a state on which the scenario is editable only when it is the root scenario. (Thanks to Tomer Gafner for the patch)
- Scenario user documentation is now saved in the root scenario context, like regular parameter.
- Pluggable tabs - User can add custom tabs to the runner.
- Pluggable publisher - User can add custom publisher to the runner
- JSystem now returns meaningful error levels on exit. 0 if all tests passes successfully since launching JSystem, 101 if at least one test failed and 102 if at least one test returned warning and no test failed.
- Fixed the reporter.classes property to search for the real reporters in the system
- Changed the behaviour of ‘save as’ option. Scenario modifications will not be saved to the original scenario, only to the new scenario.
- runScenario.bat execution mode is supported again.
- scenario.as.test.fail.teminate is now true by default
- Changed the default JSystem log format pattern from XML to simple string
- Removed support for the old report server
- Added integration with SCM.
- Scenario handling performance improvement- Fixed 3177385
- Bypass the Swing bug that causes scenarios not to stop in some cases.
- UIEventHandler/ValidationHandler interfaces were added to the systemTestCases classes.
The JSystem project is maintained by Top-Q