3.1.01

Note

Important - Difido is finally released to the Maven Central repositiories! That means that you no longer need to add the Top-Q Nexus repository to your POM file. But, we had to change the group id of the artifcates from il.co.topq to il.co.top-q.

       <dependency>
            <artifactId>difido-testng</artifactId>
            <groupId>il.co.top-q.difido</groupId>
            <version>3.1.01</version>
        </dependency>

New Features

1. Issue #269 - Add support for TestNG client for working with HTTPS servers
2. Issue #270 - Implement PyTest Binder
3. Issue #274 - Prepare the project for deployment to Maven central
4. Issue #275 - Add colors to rows in the Difido server main table according to the status of the executions
5. Issue #276 - Add support for multiple suites in the TestNG client

3.1.00

New Features

1. Issue #268 - Support for ElasticSearch 7.x

Notes

This version bumps the support from Elasticsearch version 6.x to version 7.x (tested on 7.17.3 but should work with more advanced versions).
Please notice that Elastic no longer supports mapping types and previous versions of Difido were using types when creating the Elastic mapping.
The mapping types were removed from the mapping, but this will only take affect when creating a new Elastic schema.

In addition, Difido does not yet supports xpack security, so to avoid annoying messages in the log, you can disable the security in your nodes by adding the following line to your elasticsearch.yml file:

xpack.security.enabled: false

3.0.00

IMPORTANT

This release includes a major change in the persistency mechanism. The data is not longer kept in docRoot/reports/meta.json but rather in an embedded H2 server.
When upgrading from an older version, the server will try to convert the meta.json file to the new format. A backup file with name meta.json.upgrade.backup will be created when the process will finish.
While this scenario was tested on different environments, it is very recommended to backup the meta.json file before launching the server for the first time. Failing to do so may result in LOSING ALL OF YOUR DATA.

New Features

1. Issue #221 - Store the metadata in database instead of the metadata.json file
2. Issue #248 - Remove package names from the TestNG report.

Bug Fixes

1. Issue #237 - The get execution state is not working

2.3.00

New Features

1. Issue #208 - Implement Archive Manager
2. Issue #216 - Allow the delete execution API an option to skip deletion from the Elastic
3. Issue #217 - The Difido archiver should not delete executions from the Elastic
4. Issue #218 - Limit the number of execution to archive in each iteration
5. Issue #220 - Server - Log the remote address for each request

Bug Fixes

1. Issue #222 - Server - Add timeouts to write operations that are done to the file system
2. Issue #224 - Tests duration in "Test Execution Report"/Summary Table

2.2.05

New Features

1. Issue #159 - Replace the string in the Elastic mapping to text or keyword since the string in no longer supported
2. Issue #203 - Implement a metadata retriever utility
3. Issue #204 - Add support for multiple Elasticsearch nodes for high availability
4. Issue #205 - Add api call for downloading reports of specific execution as ZIP file
5. Issue #207 - Upgrade the Spring Boot version to 1.4.4
6. Issue #209 - TestNG - Change the timestamp in the report elements to include milliseconds
7. Issue #211 - Add ability to download the executions as zip files directly from the server's gui
8. Issue #213 - Add support for hide tests in the HTML

Bug Fixes

1. Issue #148 - Add support for adding run properties during setup phase when using TestNG
2. Issue #192 - execution.properties not working while using the api
3. Issue #210 - The metadata retriever utility is no longer compiled after changing to Spring boot 1.4.4
4. Issue #214 - Failure and error messages in the setup and teardown phases of TestNG should be changed to warning

Notes

This version works with well with JSystem 6.1.10 and 6.1.11

2.2.04

New Features

1. Issue #199 - Add an option to serve archived (gzipped) resources

Bug Fixes

1. Issue #198 - When trying to move the tree frame border in the report, the border is getting glued to the mouse cursor
2. Issue #202 - Test parameters with multiple lines are not shown correctly in the report.

2.2.03

Bug Fixes

1. Issue #166 - Supporting of UTF encoding in Windows machines

v2.2.02

Bug Fixes

1. Issue #184 - Concurrent modification exception when writing metadata to disk
2. Issue #185 - In extremely high load, the server fails to assign a unique execution ID to some executions
3. Issue #187 - Starting new test and generating the reports is taking too long

v2.2.01

New Features

1. Issue #169 - Add the ability to filter the reports that are shown in the last reports
2. Issue #174 - Create interactive plugins mechansim
3. Issue #177 - Add periodic tests for the Elasticsearch health in the server and enable or disable it accordinly

Bug Fixes

1. Issue #113 - Changing "doc.root.folder" property is not working
2. Issue #165 - Execution Tree view - top level icon is always JSystem
3. Issue #179 - Dates are changing in the server since there is a common use in SimpleDateFormat which is not thread safe
4. Issue #181 - The executions are not freed from the server's memory after the execution is ended

Notes

Tested with JSystem 6.1.05 - 6.1.09

2.2.00

New Features

1. Issue #155 - Add to the server the options to show automatically the reports of the last executions
2. Issue #156 - Add the list of the tests and test statuses to the mail
3. Issue #157 - Add the execution duration to the execution reports table in the server and to each test in the Elastic
4. Issue #158 - Auto refresh the Execution Reports table in the main server view
5. Issue #161 - The mail subject should be read from template file instead of reading it from the configuration
6. Issue #162 - Set the Java version to 8
7. Issue #163 - Add icons to the buttons in the execution reports view.

Bug Fixes

1. Issue #160 - There are too many writes to the meta.json file.
2. Issue #164 - When locking execution it is also becomes active