You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The timeout given to opa test gives the impression that it is per-test when it is really for the entire test run. This means that as test suites get larger the --timeout parameter must be increased to scale with it.. which shouldn't really be the case.
What I would propose is to make the --timeout be on a per-test basis so that it can scale better as larger policy libraries are developed and tested. As I understand the idea behind the timeout flag was to just prevent tests from hanging or taking too long, so this should still fulfill the original use-case.
The text was updated successfully, but these errors were encountered:
patrick-east
changed the title
opa test timeout is for full test run and not per test
opa test timeout is for full opa test run and not per test case
Sep 23, 2019
Blokje5
added a commit
to Blokje5/opa
that referenced
this issue
Oct 20, 2019
The timeout given to
opa test
gives the impression that it is per-test when it is really for the entire test run. This means that as test suites get larger the--timeout
parameter must be increased to scale with it.. which shouldn't really be the case.What I would propose is to make the
--timeout
be on a per-test basis so that it can scale better as larger policy libraries are developed and tested. As I understand the idea behind the timeout flag was to just prevent tests from hanging or taking too long, so this should still fulfill the original use-case.The text was updated successfully, but these errors were encountered: