This repository was archived by the owner on Sep 8, 2022. It is now read-only.
Release/4.0.0 #61
Merged
Release/4.0.0 #61
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…void merge conflicts
Both reporting frameworks are designed for reporting test results. ExtentReports community version is not on Maven central, so Galenium was stuck with an old version. Allure is very much alive and a lot more flexible and extendable. * switch to Allure reporting * straighten out dependency declarations * clean up logback config * log to files and attach to Allure * move TestNG listeners to dedicated package BREAKING CHANGE: Use Allure API to write to report and SLF4J loggers to log
Galenium now has some testing capabilities that use direct HTTP communication and do not need a browser. * feat: split test base along need for browser * fix(integration): add version for allure maven plugin
The integration module should take care of running the necessary plugin for report generation. Leaving this up to the actual test project is unnecessary clutter/boilerplate.
Allure default configuration should be sensible and require no effort in test project. The default configuration should live in the integration. * refactor: move allure properties to integration resources * refactor: move allure report plugin config to integration
Makes it easier to read on the CLI when you have a wide terminal. As the rule is already available in commitlint this is the natural place to put the configuration.
To have a baseline of javadoc comments with since tags Maven's Javadoc plugin was used. Preferences was given to: * uninformative comments over no comments. * live with misleading @SInCE tags over investing manual effort * docs: run javadoc:fix over 1.0.0 * docs: run javadoc:fix over 2.0.0 * docs: run javadoc:fix over 3.0.0 * chore: fix pre-commit warning about unexpected key * docs: run javadoc:fix over 4.0.0-SNAPSHOT * revert: remove unused constants again * docs: fix one comment, run javadoc:fix again * docs: javadoc generation was done in specs-plugin and all modules Creating fresh changes.xml files as changes come up. The new strategy is to have all changes at the appropriate level in the module hierarchy and aggragate them during site generation.
The configuration is a copy from an example. Method names with line numbers are too noisy for Galenium logging.
This should get rid of some of the new warnings on CI. The imports were introduced because of links in Javadoc comments. All the links were fully qualified by the recent javadoc:fix run, so the imports are obsolete now.
* chore: bump dependency versions Ran mvn versions:use-latest-releases to keep close to development in upstream libs. * fix: extent replaced by Allure Logging to test cases is now handled by logging to file and then attaching the file to test case in Allure report. * build: bump plugin versions for archetype and formatter
* refactor: move allure properties to integration resources * refactor: move allure report plugin config to integration * refactor: new naming scheme introduced with Allure The GLNM acronym is also part of the reporting dir since the introduction of Allure.
Allure does not have a direct equivalent to Extent categories, so just removing these methods for now.
Replace the Extent categories with Allure labels which have values and names. Just put "true" when there is no real value.
* refactor: move AEM interaction to new package * feat: add XHR functionality to cookie fetcher Adds a configuration option to AEM author login fetcher to activate XHR. This makes the fetcher issue a GET prior to the actual cookie fetching POST. * chore: fix error message during comment linting Error message kept appearing twice on every commit: [WARNING] Unexpected key(s) present on https://github.com/alessandrojcm/commitlint-pre-commit-hook: sha Renamed 'sha' to 'rev' as in the other config above.
THe generated project would not compile and complain about additional JARs and missing classifiers.
Apparently context is not logging anything anymore.
Test systems are notorious for not getting their certificates right, so Galenium will be as insecure as possible about this to get testing quicker.
Bumps [netty-all](https://github.com/netty/netty) from 4.1.39.Final to 4.1.42.Final. - [Release notes](https://github.com/netty/netty/releases) - [Commits](netty/netty@netty-4.1.39.Final...netty-4.1.42.Final) Signed-off-by: dependabot[bot] <[email protected]>
Manipulating default is not a good idea. Do your own thing!
Avoids boiler plate in test projects, when trying to react to certain MQs.
Was included transiently and brought its own StringUtils which clashed with commons-text.
Behavior was all screwed up. Test device and tags were used for one, but not the other.
Eclipse keeps doing this, so just committing it.
Sometimes verification is ok, but we still get the timeout exception. We get an exception that says everything is fine. Better not throw the exception since our verification worked.
Tags are needed for parsing and running, but we get them from the call. No need to persist them.
Most test projects do not care for Javadoc as there is no reuse across projects.
* feat(galen): add log output showing tags and spec name * build(deps): bump Allure to newest release Just released today. Should be good. * feat(galen): add reporting steps to spec check * fix(galen): remove adding tags to provider Method is gone. Functionality probably irrelevant. Tags are important for parsing, but are passed to checking method anyway. * feat(report): add extra step with thread name * fix(examples): update samples
The integration module is the natural place to aggregate the API docs for UI tests.
Examples do not need to be released.
…non-snapshot versions
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.