same to follow code
https://github.com/liquibase/liquibase/blob/v4.29.1/liquibase-standard/src/main/java/liquibase/change/custom/CustomChangeWrapper.java#L163-L174

Just to be sure add synchronized, for static property executeCallCount and rollbackCallCount.

This is a test, I'm not sure to understand why it would need a sync keyword. I don't think this is needed here.

how to care for static property?
maybe, alternative way was check call count the execute and rollback method with Mockito. I think that's the way to do it politely.

I found alternative way. it is Check ExampleCustomTaskChange with executed liquibase.getDatabaseChangeLog().getChangeSets().
I will try it.

        List<CustomChange> customChanges = liquibase.getDatabaseChangeLog().getChangeSets().stream().flatMap(changeSet ->
                changeSet.getChanges().stream().filter(change ->
                        change instanceof CustomChangeWrapper &&
                                ((CustomChangeWrapper) change).getCustomChange() instanceof ExampleCustomTaskChange
                ).map(change ->
                        ((CustomChangeWrapper) change).getCustomChange())
        ).collect(Collectors.toList());
        for (CustomChange customChange : customChanges) {
            assertEquals(1, ((ExampleCustomTaskChange)customChange).executeCallCount);
            assertEquals(0, ((ExampleCustomTaskChange)customChange).rollbackCallCount);
        }

I wrote this code. but cannot check call-count, actual value is 0. because, difference ExampleCustomTaskChange object.

I was going to suggest making ExampleCustomTaskChange a singleton class, and then checking rollbackcount but I think this won't help with this issue. Let me ask tomorrow one of our team members with more experience/knowledge on custom changes because my guess is rollback is executing twice because there might be something else calling also this same method.

Hi @momosetkn,

I was talking about this with someone else from the team, and we agreed that synchronized keyword is not needed there. To validate counts, we think maybe what we can do here is to have a map and save your ExampleCustomTaskChange instances there, then save this map in the current scope. I was thinking of adding something like this in CustomChangeWrapper, but I'm unsure if this is the right place. It would probably be if some other custom changes implement something like this, but for now, we can probably do this in the scope you were trying to do this validation.

Thanks,
Daniel.

I see, ThreadLocal(map in the current scope) can resolve synchronous problem.
I fix.

@MalloD12
Sorry for the late fix.
I fixed.

Hey @momosetkn we don't need to create several liquibase instances if they are all using the same changelog. I would leave only one of these.

That's my only suggestion to update on this test.

Thanks,
Daniel.

ok, I fixed!