typelevel / typelevel/fs2-grpc

e2e tests

Open
#35 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Scala
Stars
284
Forks
66
Avg merge
1d 7h
Merged PRs (30d)
4

Description

As suggested by @fiadliel we should introduce some more tests that cover:

  • client, server startup
  • e2e single-single request/response
  • e2e single-stream request/response
  • e2e stream-single request/response
  • e2e stream-stream (client closes first) request/response
  • e2e stream-stream (server closes first) request/response

There are a lot more possible scenarios (e.g. errors, test against different language implementations), but it's some of the most basic test requirements.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files or existing test entry points. Start by locating the client/server startup and request/response test harness, then cover the listed single and streaming combinations; done means those basic scenarios pass.

Written by the indexing model from the issue text.

Assessment

Tech stack
grpc, scala
Domain
api, testing
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.