ara-7.0.5

Feat/merge 7.0.0 (#334)

* fix: ignore unknown fields when uploading Cucumber scenarios

* ⬆️  Upgrade to 7.0.5

Co-authored-by: Omar CHAHBOUNI <[email protected]>
Co-authored-by: Omar CHAHBOUNI <[email protected]>

ara-7.0.4

⬆️  Upgrade to 7.0.4 (#327)

ara-7.0.3

⬆️  Upgrade to 7.0.3

ara-7.0.2

⬆️ Upgrade to 7.0.2

ara-7.0.1

Upgrade version 7.0.1

Release 6.1.0

Release 6.1.0

What's new ?

Previously, it was only possible to move or delete one functionality at a time. It was very tedious to repeat these actions over multiple nodes. This release resolves this issue by enabling to manage multiple selection !

Features

• Move multiple features (#8): In the cartography tab, you can now move multiple functionalities together to a given target
• Delete multiple features (#297): The same feature as above, but for deletion

Fixes

• Add a 404 page (#283): if an URL doesn't exist, a not found page is displayed
• Get rid of infinite loading (#292): Previously, if a project had no settings (i.e no source, country or team assignable to functionalities), a loader was indefinitely spinning. An error page is now displayed instead.

Tests

• Cypress tests — thanks to @z25clave, @BenjaminDupont

Release 6.0.0

Release 6.0.0

ARA now supports Cypress !

What's new ?

Breaking Changes

• Add Cypress reporter (#26):

The refactoring (#158) from the previous release laid the groundwork to add new reporters more easily. The Cypress reporter is the first to benefit from the modularity previously added.

You can now configure ARA to support Cypress executions:

1. Go to the settings (MANAGE PROJECT)
2. In the SOURCES tab, add a new source with the Cypress technology
3. In the TYPES tab, add a type linked to the previously created source
4. (Optional) Add one or more countries if needed
5. (Optional) In the TECHNOLOGIES tab, you can update the default Cypress settings

After configuration, the feature can now process reports generated from Cypress.
Like the Postman and Cucumber reporters, this feature:

• Create executions from a zip containing reports generated by Cypress
• Add Cypress related scenarios (via uploadCucumberScenarios in the Cypress resource)

Note:

• Bear in mind that for now, Cypress only relies on the cypress-cucumber-preprocessor.
  The report generation with mochawesome is not yet supported.
• The Cucumber & Postman upload scenario resources (uploadCucumber & uploadPostman) are now deprecated. Please stop using them and replace them by uploadScenarios (in the Postman and Cucumber resource).
  To aim toward modularity, there are now resources per Technology.
• If your project handles Cypress reports but you want to rollback to a previous version, ARA may be unstable. To avoid any problem, delete all the Cypress related settings.

For more details, you can check the documentation here: https://github.com/Decathlon/ara/blob/master/doc/uploads/UploadCypress.adoc

Fixes

• Fix Docker broken links in the documentation (#268) — thanks to @ludomartin

Tests

• Cypress tests — thanks to @z25clave, @BenjaminDupont

Release 5.0.0

Release 5.0.0

The main feature added by this release is the modularity of ARA reporters: the current Cucumber and Postman handling is now independent, making it easier to add new test technologies!

You can still install ARA from the official Docker images.

The images are available here :

• https://hub.docker.com/r/decathlon/ara-db/tags
• https://hub.docker.com/r/decathlon/ara-server/tags

Read this section for more informations about how to install it locally.

This release contains:

What's new ?

Breaking Changes

• Refactor the way the reporters are integrated (#158):
  Previously, the reporters were tightly coupled to the execution handling code, and relied on a component (fetcher) that had the following issues:
  • it relied on reflexivity, which:
    • highly depends on code
    • has unclear relations
    • is not easy to search in an IDE
    • cannot be debugged
    • has performance issue
  • it was redundant and misleading: the build results were already "fetched", as the zip was uploaded. Saving the content and then getting it had the following problems:
    • this step is useless
    • it costs time and resources to do it
    • this adds complexity, thus creating more risks for bugs to appear later
    • it already had a bug: a new zip with the same name could not replace a previous folder containing a faulty zip content, thus requiring the user to delete it.
  • it was highly dependent on the type of the reporter (here Cucumber and Postman)

To sum up, this release makes reporters:

• independent:
  • each reporter is located in a specific location.
  • the settings are also independent: each reporter has its own setting, unlike previously were all the settings were mixed
• have more straightforward, readable code
• easier to update
• easier to test
• easier to maintain
• see performance increase
• fix a bug

The reporters can now be implemented independently, making it easier to contribute!

Features

• Add a Windows CMD version of manage-db.sh (#93): This feature enable to init the database in Windows too.
• Add the reporting section of pom.xml (#228): This let the developers generate a site from maven, giving a quick overview of the project — thanks to @qualitesys

Fixes

• Get rid of npm commands in the client pom.xml (#168): The npm and mvn commands are now run separately, thus getting rid of random build failures
• Fix the (docker) installation for Ubuntu (#222): You can now launch a local ARA installation via docker & docker-compose in Linux systems — thanks to @dktsni, @bbutel
• Flag a project as Default Project (#162): If you want to set a project as default, you don't have to uncheck the default project anymore — thanks to @dktsni, @BenjaminDupont
• Change the feature label (#11): Fix the broken link between a feature and scenario when the feature label has been updated — thanks to @dktsni, @slaout, @ghost

Tests

• Cypress tests (#258) — thanks to @z25clave, @BenjaminDupont

What should I do to update to this version ?

If you update to this version, you'll need to:

Update the database:

• Create the table technology_setting:

DROP TABLE IF EXISTS `technology_setting`;
CREATE TABLE `technology_setting` (
 `id` bigint(20) NOT NULL AUTO_INCREMENT,
 `project_id` bigint(20) NOT NULL,
 `code` varchar(64) COLLATE utf8_unicode_ci NOT NULL,
 `value` varchar(512) COLLATE utf8_unicode_ci DEFAULT NULL,
 `technology` varchar(16) COLLATE utf8_unicode_ci NOT NULL,
 PRIMARY KEY (`id`),
 UNIQUE KEY `unique_technology_setting` (`project_id`,`code`,`technology`),
 CONSTRAINT `fk_technology_setting_projectid` FOREIGN KEY (`project_id`) REFERENCES `project` (`id`) ON DELETE CASCADE
) ENGINE=InnoDB AUTO_INCREMENT=10 DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci ROW_FORMAT=DYNAMIC;

• Copy your old settings, if any:

insert into technology_setting (project_id, code, value, technology) select project_id, 'report.path' as code, value, 'CUCUMBER' as technology from setting where code = 'execution.indexer.file.cucumberReportPath';
insert into technology_setting (project_id, code, value, technology) select project_id, 'step.definitions.path' as code, value, 'CUCUMBER' as technology from setting where code = 'execution.indexer.file.cucumberStepDefinitionsPath';
insert into technology_setting (project_id, code, value, technology) select project_id, 'reports.path' as code, value, 'POSTMAN' as technology from setting where code = 'execution.indexer.file.newmanReportsPath';

• (Optional) Delete the copied lines, as they are no longer used in this version:

delete from setting where code in ('execution.indexer.file.cucumberReportPath', 'execution.indexer.file.cucumberStepDefinitionsPath', 'execution.indexer.file.newmanReportsPath');

What if I want to rollback to the previous version ?

If you want to rollback, then you'll need to do the opposite:

insert into setting (project_id, code, value) select project_id, 'execution.indexer.file.cucumberReportPath' as code, value from technology_setting where code = 'report.path' and technology = 'CUCUMBER';
insert into setting (project_id, code, value) select project_id, 'execution.indexer.file.cucumberStepDefinitionsPath' as code, value from technology_setting where code = 'step.definitions.path' and technology = 'CUCUMBER';
insert into setting (project_id, code, value) select project_id, 'execution.indexer.file.newmanReportsPath' as code, value from technology_setting where code = 'reports.path' and technology = 'POSTMAN';

Release 4.1.0

Release 4.1.0

Today we're excited to announce a brand new version of ARA which will focus on stability and add a new feature to export the cartography of functionalities from a project and import it to another ARA project or even to a SquashTM project !

You can still install ARA from the official Docker images.

The images are available here :

• https://hub.docker.com/r/decathlon/ara-db/tags
• https://hub.docker.com/r/decathlon/ara-server/tags

Read this section for more informations about how to install it locally.

This release contains the following improvements :

Breaking Changes

None

Features

• Add a feature to export the functionalities cartography to JSON and import it in another ARA project (#165)
• Add a feature to export the functionalities cartography to integrate it as exigence in SquashTM (#184)
• Display the matching problems in date descending order instead of ascending (#173) — thanks to @JulienBarlet

Fixes

• Fix a performance issue in the Executions and Problems screens which is triggered by too many exceptions and freeze the screen (#81)
• Adjust the color used by the search criteria in the execution screen (#171) thanks to @TroyonGuillaume
• 
Fix various security vulnerabilities (#155, #156, #187, #226)
• Various documentation updates (#145, #166 #170, #186, #188) — thanks to @JulienBarlet, @owulveryck, @z28rbill)

Release 4.0.0

Release 4.0.0

You can now install ARA from the official Docker images.

The images are available here :

• https://hub.docker.com/r/decathlon/ara-db/tags
• https://hub.docker.com/r/decathlon/ara-server/tags

Read this section for more informations about how to install it locally.

This release contains the following improvements :

Breaking Changes

• Refactor the project to extract database related code to it's own module (#102)
• Remove QueryDSL classes generation to prevent the need of a database up & running when build the server (#119, #97, #96)

Fixes

• Update the documentation with the new procedure to install ARA (#100)
• Fix an error when Windows users starts the Database Docker image which prevents the structure from being imported in the database (#115, #15)
• Remove old informations and files (#82, #86)
• Fix a failing unit tests on Ubuntu only (#16)
• Add Licence notice on all the files (#128)

Features

• Create two docker images and a docker-compose configuration to easily install ARA locally, you don't have to install & build everything now !! (#84)
• Add automatic builds & deliveries to fix errors faster (#83, thanks to @mmornati and @lusoalex )
• Add documentations about Cucumber and Postman test reports' uploads on ARA (#111, #114, #118)
• Rework the pom.xml files to make the build faster and clearer (#87, #101)