Make AggregateRootTestCase methods more reusable about eventsauce HOT 5 CLOSED

it'll be less of a hassle for the laravel package, but it'd be much more of a hassle for the main implementation.

Didn't think too much about that problem, I was focused on making it as easy as possible for the users of the Laravel package.

Even just using all of the traits from the laravel one would be trivial to setup right?

That's true

Thanks for your input here! 👍

from eventsauce.

@freekmurze in the laracon workshop I just used the CreatesApplication trait from Laravel, perhaps we can ship with an additional baseclass which extends the eventsauce one and adds CreatesApplication?

from eventsauce.

@frankdejonge That works too indeed. But by only putting on CreatesApplication you'd still miss the other methods provided by the InteractsWithContainer, InteractsWithConsole, InteractsWithDatabase, MocksApplicationServices traits and so on.

If the current AggregateRootTestCase would be refactored so all methods are in a trait you could choose the style you want. Want to extend AggregateRootTestCase? Fine! Want to use the base test of your project (that you might have customized a bit), just add the TestsAggregateRoot trait to it.

from eventsauce.

Doesn't laravel provide a single trait to combine those all? Extracting the behaviour from our base class is not trivial because of all the methods used from its base class provided by PHPUnit, which then all need to be added as abstract ones, through which it'd be very hard to detect when things are changing. I agree it'll be less of a hassle for the laravel package, but it'd be much more of a hassle for the main implementation.

from eventsauce.

Even just using all of the traits from the laravel one would be trivial to setup right?

from eventsauce.