René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Test Coverage: End to End Tests for Dataflow Runner","articleBody":"**Is your feature request related to a problem? Please describe.**\r\n\r\nCurrently, Feast's end to end tests only verify correctness with Feast Core's [Direct Runner](https://github.com/gojek/feast/blob/2fa30ac1883ad6fdc42168487a0fbafd38020b16/infra/scripts/test-end-to-end.sh#L103), leaving a gap in test coverage for the Dataflow runner. This is an issue a we are unable to verify that new additions to the codebase work well with the Dataflow runner, requiring PR authors to do error prone manual testing.\r\n\r\nCase study: PR #575 \r\n- I submitted small PR #575 which updated how `Runner`s are rendered.\r\n- Since the PR is relatively small and all the tests pass, I assumed that the PR did not introduce any bugs and didn't do any independent testing on my own.\r\n- I only discovered that the PR broke the Dataflow runner after it was merged, leaving a known bug on the master branch.\r\n\r\nThis bug in the PR would have been caught by Feast's test suite, had it tested with the Dataflow runner in addition to the Direct runner.\r\n\r\n**Describe the solution you'd like**\r\nAdd End to End Tests using the Dataflow Runner, in additional to the Direct Runner.","author":{"url":"https://github.com/mrzzy","@type":"Person","name":"mrzzy"},"datePublished":"2020-04-01T16:12:00.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":2},"url":"https://github.com/595/feast/issues/595"}