Inconsistency in AggregateTestFixture with constructor command handlers

[CodeDrivenMitch]

Basic information

• Axon Framework version: 4.9.1
• JDK version: -
• Complete executable reproducer if available (e.g. GitHub Repo): -

Steps to reproduce

• Create aggregate with constructor command handler
• Create AggregateTestFixture and execute givenCommands and when on it with the same creational command
• The test succeeds, and there is a second event published at index 0

Expected behaviour

The AggregateTestFixture should detect a constructor command handler being called for the second time, or being able to validate the unqqueness of the aggregate through validating the event indexes.

Actual behaviour

The test passes, allowing two events with index 0.

[abuijze]

Are you sure it's appending two events, or is it the consistency check that's kicking in an applying event 0 to a fresh instance of the aggregate to ensure it doesn't have any "illegal state changes"?