-
Notifications
You must be signed in to change notification settings - Fork 55
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
IWF-472: Fix all the panic and enable test coverage #535
Conversation
@@ -17,6 +17,9 @@ import ( | |||
) | |||
|
|||
func TestLockingWorkflowTemporal(t *testing.T) { | |||
// TODO: Remove this line to enable the test | |||
t.Skip("TestLockingWorkflowTemporal - Skipping this test - See: https://github.com/indeedeng/iwf/issues/536") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems that this test has been failing for a while, created an issue to fix this in the future: #536
I believe that before the tests passes because the panic
's would somehow recover, and after I added the t.Fatalf
calls that actually mark the tests as failed the right way, it always fails the pipeline
022d86f
to
3456615
Compare
3456615
to
38bac14
Compare
…ss token in the action
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #535 +/- ##
==========================================
- Coverage 72.15% 64.56% -7.60%
==========================================
Files 56 59 +3
Lines 5043 6617 +1574
==========================================
+ Hits 3639 4272 +633
- Misses 1138 2066 +928
- Partials 266 279 +13 ☔ View full report in Codecov by Sentry. |
In summary:
On others notes:
|
@@ -0,0 +1,11 @@ | |||
package helpers |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Q: should this be in the integ
package similarly to util.go?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I did that at first, but it creates a circular dependency, because the helper error functions are also used in the routers files for each test.
i.e. Package integ
has a test file, that test file imports the routers package for that test e.g. wf_stop.NewHandler()
and then that package would include integ
again to call the error helper, thus creating a circular dependency
Closes #446 |
Description
Checklist
Related Issue
Closes #446