akka/akka-core

Javadsl TestKit/TestProbe

Open

#25,458 opened on Aug 10, 2018

View on GitHub
 (1 comment) (1 reaction) (0 assignees)Scala (3,547 forks)batch import
1 - triageddiscusshelp wantedt:testing

Repository metrics

Stars
 (13,277 stars)
PR merge metrics
 (Avg merge 8d 19h) (10 merged PRs in 30d)

Description

In the scaladsl, TestProbe extends TestKit with probing features.

In the javadsl, TestKit itself can be used for probing.

For TestProbe you can optionally supply the name for the probing actor. This feature is not exposed for the javadsl TestKit. While only useful for debugging/logging this might still be nice to add.

Going a step further, we could even consider introducing a the TestProbe/TestKit distinction to the javadsl as well: it seems this could be as simple as introducing a class TestProbe extends TestKit containing the probing methods, and deprecating them on the parent TestKit.

Whichever we choose, we should update the text and code of testing.md in the reference documentation to reflect this: right now the Java version mentions TestProbe which arguably works but doesn't seem right anymore since scaladsl and javadsl have diverged now.

Contributor guide

Research direction
Add a name parameter to the javadsl TestKit or introduce a TestProbe class for the javadsl. Then update the testing.md documentation accordingly.
Tech stack
scala
Domain
testing
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Java
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60