Slick Forums

When trying to write a unit test for my game I ran into a bit of a problem. I am looking for the best way to replace one or more of the system classes with mock objects. As far as I can see the only way I can do this with Artemis is to extract the code I wish to replace into a delegate and let the system class choose between the test and production versions.

It would be nice if I could choose the key that the system manager uses to map my systems with, that way I can swap out any system class without having to let other classes that refer to it know about the change. However this breaks the GoF recommendation to favour delegation over inheritance so perhaps it would be best to keep it the way it is.

How many Artemis users are unit testing? Also what has been your approach to this problem?

What steps will reproduce the problem?
1. Create a World
2. Create a Entity and give it a 5 varying Component types
3. Call Entity refresh()
3. Call World loopStart() to refresh everything
3. Get the Entity components with getComponents() method or use a breakpoint to browse the contents of the EntityManager componentsByType list.

What is the expected output? What do you see instead?
I expect to see 5 components. Instead depending on the ID of the Entity in my tests with only 1 entity in the World the getComponents() method returned 2 components when it should've returned all 5.

What version of the product are you using? On what operating system?
Latest source from this.

Please provide any additional information below.
I found a work around is to create 50 or so Entities with all my components so that the componentsByType list has all the component bags initialized.