Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

QA - Dates in Cucumber Scenarios should be generated dynamically #3176

Open
gbarbon opened this issue Dec 15, 2020 · 0 comments
Open

QA - Dates in Cucumber Scenarios should be generated dynamically #3176

gbarbon opened this issue Dec 15, 2020 · 0 comments
Labels
Enhancement This PR/Issue improves an part of Kapua Test Test related stuff. It's a dirty job, but someone needs to do that!

Comments

@gbarbon
Copy link
Member

gbarbon commented Dec 15, 2020

Is your feature request related to a problem? Please describe.
The dates in cucumber scenarios should be generated in a dynamic way, and not hardcoded.

Hardcoded dates have already caused an issue, see for instance PR #3175 . In this case the trigger end date was in the past (which clearly was not the case when the scenarios had been written), causing QA failures. A date generator method, that generates dates in the future, would have prevented such issue.

Describe the solution you'd like
A Cucumber step dedicated to date generation.

Describe alternatives you've considered
n/a

Additional context
n/a

@gbarbon gbarbon added Enhancement This PR/Issue improves an part of Kapua Test Test related stuff. It's a dirty job, but someone needs to do that! labels Dec 21, 2020
@gbarbon gbarbon changed the title Dates in Cucumber Scenarios should be generated dynamically QA - Dates in Cucumber Scenarios should be generated dynamically Apr 22, 2021
@Coduz Coduz moved this to To Do in Eclipse Kapua Backlog Jun 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement This PR/Issue improves an part of Kapua Test Test related stuff. It's a dirty job, but someone needs to do that!
Projects
Development

No branches or pull requests

1 participant