Create test plan with plan for unit tests and more
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 42/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- java
- Domain
- documentation, testing
Research direction
Start by reviewing the library's existing end-to-end tests and inventorying its units, noting that units need not be single classes. Create a high-level test plan covering each unit, its main use cases, and the strategy for fast unit tests; done means the plan clearly guides adding tests beyond the current end-to-end coverage.
Written by the indexing model from the issue text.
Description
This library is in initial phase and the main focus has been in finding a model for the Reactive API for Apache Pulsar.
There are only a few end-to-end tests at the moment.
To add tests, it makes sense to first do a high level test plan and describe the test strategy.
Each "unit" should be listed in the plan and the main use cases to test would be listed too. The units aren't necessary single classes. Unit tests should execute quickly.
- Dominant language
- Java
- Stars
- 67
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from apache/pulsar-client-reactive
-
Difficulty 3/5 1-2 days Newbie friendliness 39/100
apache/pulsar-client-reactive#227 ·
-
Acknowledge outside of consumeMany and consumeOneMay be free again @lhotari claimed this 491 days ago, and no pull request is open. Open
apache/pulsar-client-reactive#220 · 1 comment · 1 assignee ·
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
apache/pulsar-client-reactive#216 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
apache/pulsar-client-reactive#182 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
apache/pulsar-client-reactive#114 · 6 comments ·
All issues in apache/pulsar-client-reactive
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
beehive-lab/TornadoVM#1151 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
FasterXML/jackson-dataformats-binary#823 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day