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
returnfmt.Errorf("failed to get instance from collection: %w", err)
}
assert.Equal(&c.ErrorFeature, expected, got)
returnnil
}
And therefore the component tests using this step are wrongly passing.
The function should return c.ErrorFeature.StepError() so that the test fails when there are discrepancies in the expected value.
However, the component tests will need to be reviewed and rewritten as they won't pass as they are.
Also, they seem to be calling an endpoint that does not even exist:
The component test step
the instance in the database for id "id" should be:
is not returning an error when the assertion fails:dp-dataset-api/features/steps/steps.go
Lines 84 to 101 in 4a8072c
And therefore the component tests using this step are wrongly passing.
The function should return
c.ErrorFeature.StepError()
so that the test fails when there are discrepancies in the expected value.However, the component tests will need to be reviewed and rewritten as they won't pass as they are.
Also, they seem to be calling an endpoint that does not even exist:
dp-dataset-api/features/instances.feature
Lines 342 to 353 in 4a8072c
dp-dataset-api/features/instances.feature
Lines 378 to 390 in 4a8072c
Presumably they should be calling
PUT "/instances/{instance_id}"
A review of these tests is required
The text was updated successfully, but these errors were encountered: