Migrate PubSub removing flaky test

[mcruzdev]

Description

Use testcontainers for PubSub tests.

The main goal is to remove the following flaky test https://github.com/dapr/java-sdk/actions/runs/13773009141/job/38515768267#step:19:13432.

Closes one of the flaky test links related on the #1258 issue.

Issue reference

We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.

Please reference the issue this PR will close: #[issue number]

Checklist

Please make sure you've completed the relevant tasks for this PR, out of the following list:

• Code compiles correctly
• Created/updated tests
• Extended the documentation

[mcruzdev]

@artur-ciocanu @cicoyle @salaboy

Trying to move the following test to use Testcontainers I got a problem.

java-sdk/sdk-tests/src/test/java/io/dapr/it/pubsub/http/PubSubIT.java

Lines 571 to 572 in 3a8fd61

	public void testPubSubBulkSubscribe() throws Exception {
	DaprRun daprRun = closeLater(startDaprApp(

When running the test from PubSub the following assert works well:

java-sdk/sdk-tests/src/test/java/io/dapr/it/pubsub/http/PubSubIT.java

Line 612 in 3a8fd61

assertEquals(1, messages.size());

I have 1 message with the first message containing 10 statuses.

But using in-memory (Testcontainers) I have 10 messages and each one with 1 statuses.

I would like to know if the in-memory PubSub supports bulk message? The PubSub from DaprRun uses Redis

[artur-ciocanu]

@mcruzdev I will try to review ASAP, but could you please check why the ITs are failing?

[mcruzdev]

@mcruzdev I will try to review ASAP, but could you please check why the ITs are failing?

It is another mapped flaky test

[mcruzdev]

Error, I need to change the assert...

expected: 
  [io.dapr.it.pubsub.http.PubSubIT$ConvertToLong@5bbe4e8f,
      io.dapr.it.pubsub.http.PubSubIT$ConvertToLong@dc7818,
      io.dapr.it.pubsub.http.PubSubIT$ConvertToLong@b2fdfa8,
      io.dapr.it.pubsub.http.PubSubIT$ConvertToLong@4613e544,
      io.dapr.it.pubsub.http.PubSubIT$ConvertToLong@abac76b4,
      io.dapr.it.pubsub.http.PubSubIT$ConvertToLong@e8f49fdd,
      io.dapr.it.pubsub.http.PubSubIT$ConvertToLong@bf3b3eb2,
      io.dapr.it.pubsub.http.PubSubIT$ConvertToLong@9843cc0f,
      io.dapr.it.pubsub.http.PubSubIT$ConvertToLong@3346a35b]
 but was: 
  [io.dapr.it.pubsub.http.PubSubIT$ConvertToLong@f7ce0e8f,
      io.dapr.it.pubsub.http.PubSubIT$ConvertToLong@5bbe4e8f,
      io.dapr.it.pubsub.http.PubSubIT$ConvertToLong@dc7818,
      io.dapr.it.pubsub.http.PubSubIT$ConvertToLong@b2fdfa8,
      io.dapr.it.pubsub.http.PubSubIT$ConvertToLong@4613e544,
      io.dapr.it.pubsub.http.PubSubIT$ConvertToLong@abac76b4,
      io.dapr.it.pubsub.http.PubSubIT$ConvertToLong@e8f49fdd,
      io.dapr.it.pubsub.http.PubSubIT$ConvertToLong@bf3b3eb2,
      io.dapr.it.pubsub.http.PubSubIT$ConvertToLong@9843cc0f,
      io.dapr.it.pubsub.http.PubSubIT$ConvertToLong@3346a35b]

[artur-ciocanu]

@mcruzdev could you please check what is wrong with the tests, I see this error:

Error:    DaprPubSubIT.testLongValues:578 » Runtime org.opentest4j.AssertionFailedError: 
expected: 
  [io.dapr.it.pubsub.http.PubSubIT$ConvertToLong@5bbe4e8f,
      io.dapr.it.pubsub.http.PubSubIT$ConvertToLong@dc7818,
      io.dapr.it.pubsub.http.PubSubIT$ConvertToLong@b2fdfa8,
      io.dapr.it.pubsub.http.PubSubIT$ConvertToLong@4613e544,
      io.dapr.it.pubsub.http.PubSubIT$ConvertToLong@abac76b4,
      io.dapr.it.pubsub.http.PubSubIT$ConvertToLong@e8f49fdd,
      io.dapr.it.pubsub.http.PubSubIT$ConvertToLong@bf3b3eb2,
      io.dapr.it.pubsub.http.PubSubIT$ConvertToLong@9843cc0f,
      io.dapr.it.pubsub.http.PubSubIT$ConvertToLong@3346a35b]
 but was: 
  [io.dapr.it.pubsub.http.PubSubIT$ConvertToLong@f7ce0e8f,
      io.dapr.it.pubsub.http.PubSubIT$ConvertToLong@5bbe4e8f,
      io.dapr.it.pubsub.http.PubSubIT$ConvertToLong@dc7818,
      io.dapr.it.pubsub.http.PubSubIT$ConvertToLong@b2fdfa8,
      io.dapr.it.pubsub.http.PubSubIT$ConvertToLong@4613e544,
      io.dapr.it.pubsub.http.PubSubIT$ConvertToLong@abac76b4,
      io.dapr.it.pubsub.http.PubSubIT$ConvertToLong@e8f49fdd,
      io.dapr.it.pubsub.http.PubSubIT$ConvertToLong@bf3b3eb2,
      io.dapr.it.pubsub.http.PubSubIT$ConvertToLong@9843cc0f,
      io.dapr.it.pubsub.http.PubSubIT$ConvertToLong@3346a35b]

[artur-ciocanu]

@mcruzdev the PR looks good. There are a few things that I think should be addressed:

• Please make sure that you use logger instead of System.out, I have tried to add comments to all the places, but please double check and make sure that we use logger everywhere
• The Dapr Jackson serialzer could replaced with CustomizableObjectSerializer instead of creating an inline class
• I see that there are quite a few Thread.sleep() invocations, I am wondering if there is a way to avoid them. If not I am OK with them.

Please take a look and let me know your thoughts.

[mcruzdev]

Hi @artur-ciocanu we really need a custom ObjectSerializer, using a CustomizableObjectSerializer that allow the ObjectMapper be customizable are broking some tests.

I just copied the old behavior to the new way to write tests (using testcontainers to instantiate dapr).

[artur-ciocanu]

@mcruzdev you made my day! Really nice patch, thank you! 🙇

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 78.34%. Comparing base (d759c53) to head (3806ae6).
Report is 179 commits behind head on master.

Additional details and impacted files

@@             Coverage Diff              @@
##             master    #1407      +/-   ##
============================================
+ Coverage     76.91%   78.34%   +1.42%     
- Complexity     1592     1878     +286     
============================================
  Files           145      234      +89     
  Lines          4843     5832     +989     
  Branches        562      601      +39     
============================================
+ Hits           3725     4569     +844     
- Misses          821      943     +122     
- Partials        297      320      +23     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.