Skip to content

Comments

Remove flow-api gRPC dependency from e2e tests#3899

Draft
iskakaushik wants to merge 3 commits intomainfrom
remove-flow-api-dep
Draft

Remove flow-api gRPC dependency from e2e tests#3899
iskakaushik wants to merge 3 commits intomainfrom
remove-flow-api-dep

Conversation

@iskakaushik
Copy link
Contributor

Summary

Replaces all gRPC FlowServiceClient calls (connecting to flow-api on port 8112) in e2e tests with direct in-process calls to *cmd.FlowRequestHandler. This removes the need to have a running flow-api server when running e2e tests, since FlowRequestHandler has the same method signatures and its APIError return type satisfies the error interface.

e2e tests now use FlowRequestHandler in-process, so the flow-api
server is no longer needed.
@codecov
Copy link

codecov bot commented Feb 6, 2026

❌ 1 Tests Failed:

Tests completed Failed Passed Skipped
1224 1 1223 3
View the full list of 1 ❄️ flaky test(s)
::TestMain

Flake rate in main: 100.00% (Passed 0 times, Failed 7 times)

Stack Traces | 0s run time
FAIL	github..../peerdb/flow/e2e [build failed]

To view more test analytics, go to the Test Analytics Dashboard
📋 Got 3 mins? Take this short survey to help us improve Test Analytics.

Handler methods like CreateCDCFlow return cmd.APIError, which typed
the err variable as APIError. Subsequent := reuse with functions
returning plain error (GetPeerflow, loadConfigFromCatalog, etc.)
caused compile failures. Use apiErr for handler returns to keep
err as plain error.
@ilidemi ilidemi marked this pull request as draft February 6, 2026 16:10
@ilidemi
Copy link
Contributor

ilidemi commented Feb 6, 2026

Great direction @iskakaushik! As this is an infra change, please make sure to add relevant reviewers when it's ready to be taken a look at

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants