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

Make default timeout for codeception into env var #36

Open
6 of 18 tasks
roborourke opened this issue May 26, 2022 · 1 comment
Open
6 of 18 tasks

Make default timeout for codeception into env var #36

roborourke opened this issue May 26, 2022 · 1 comment
Labels
should have Should be done, medium priority for now

Comments

@roborourke
Copy link
Contributor

roborourke commented May 26, 2022

In some cases, we're seeing timeouts on test runs from the selenium web driver. This might be an inability to resolve the server, but could also be that things are just exceptionally slow sometimes.

Being able to configure the default codeception timeout globally could be very useful for debugging but also for making sure test runs are consistent in their outcome.

Acceptance criteria:

  • Default codeception timeout value can be set via an environment variable at run time called CODECEPT_TIMEOUT
  • Validate that the timeout is applied on long running tests
  • Add documentation about the variable

For Altis Team Use

Ready for Work Checklist

Is this ticket ready to be worked on? See
the Play Book Definition of Ready

  • Is the title clear?
  • Is the description clear and detailed enough?
  • Are acceptance criteria listed?
  • Have any (potential) dependencies been identified?
  • Is an estimate or time box assigned?
  • Is a priority label assigned?
  • Is this ticket added to an epic? (Optional)

Completion Checklist

Is this ticket done? See
the Play Book Definition of Ready

  • Has the acceptance criteria been met?
  • Is the documentation updated (including README)?
  • Does any code/documentation meet project standards?
  • Are automatic tests in place to verify the fix or new functionality?
  • Or are manual tests documented (at least on this ticket)?
  • Are any Playbook/Handbook pages updated?
  • Has a new module release (patch/minor) been created/scheduled?
  • Have the appropriate backport labels been added to the PR?
@roborourke roborourke added should have Should be done, medium priority for now to refine Issues needing refinement. labels May 26, 2022
@mikelittle
Copy link
Contributor

Hey team! Please add your planning poker estimate with Zenhub @ferschubert-hm @jerico @wisyhambolu

@mikelittle mikelittle removed the to refine Issues needing refinement. label Nov 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
should have Should be done, medium priority for now
Projects
None yet
Development

No branches or pull requests

2 participants