QA trigger end date changed to avoid TriggerNeverFiresException #3175
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.
This PR fixes an issue that produced a
TriggerNeverFiresException
in some Cucumber tests, making QAs fail. The cause was due to the hardcoded end date of the trigger in the Cucumber scenarios, which was set to a date prior to the current date.Related Issue
n/a
Description of the solution adopted
The year in the start and end dates of some scenarios of the
TriggerServiceI9n.feature
has been changed to 2030.Screenshots
n/a
Any side note on the changes made
This is only a fast fix, a better solution would be to dynamically generated dates in the Cucumber scenarios, instead of using hardcoded dates. A dedicated issue (see #3176 ) has been created to track such improvement.