Version 2.3.0

All backup files for a decision table are now automatically packed in a ZIP file and only remain unpacked as long as the decision table is opened in LF‑ET.

If decision tables are located on network drives, annoying delays can occur in rare cases du­ring saving. The management of backup files could be identified as the reason which led to the development of a second, alternative version of backup file management.

Individual simulation steps and the rules run are now automatically recorded and evaluated statistically. Logs and statistics can either be saved or deleted once the simulation is completed.

Takeover of information from decision tables that has so far been available for Java and Groovy has been expanded. In the case of Enum generation for intervals also boolean isInInterval(double/int value) are now being automatically ge­ne­ra­ted.
 

Generation of stateless and generic software modules, as well as the use of annotations, are now supported for Java and Groovy languages.

In the case of bulk generation, e.g. in the context of CI/CD using the LF-ET-Maven-Plugin, overwriting of already existing and functionally identical software modules can now be suppressed: SkipUnchanged
 

Newly added functions include generation for Python, JavaScript and TypeScript.

LF‑ET supports different test case/test suite export formats so that ge­ne­ra­ted test cases can be documented and their execution recorded in a desired fashion.

If test data are used for test case generation, it is possible that more than one data set is suitable in order to generate a specific test case. With the new option also data-driven test cases can now be ge­ne­ra­ted in addition to recommended test cases.
 

In the case of "state-based testing" using LF‑ET, a rule is regarded as a transition from one state to another. As regards n-switch-coverage n stands for the number of states between the start and end state of a test case.

In order for the configuration file to be assigned more specifically to LF‑ET, the "LFET." prefix can now be added to the file name: LFET.Project.ini. It is case-insensitive.
 

LFET.Project.yaml and Project.yaml are alternative names for the Project.ini file and enable the lightweight markup language YAML to be used instead of the classic property format (key=value).
 

If LF‑ET, while searching for Project.ini-files for the currently open decision table in the same directory, finds a file with the same name, with the .ini or .yaml ending in addition to the .lfet ending, LF‑ET adds this file as the first in the list of Project.ini-files found.

Several Project.ini files can now be nested. Individual global settings such as e.g. package definition for Java module, can now be overridden in a sub-folder for a group of decision tables.

The search algorithm for Project.ini files has been completely modified and optimized. Rare cases of delays when opening decision tables or when generating programs should now be a thing of the past.