Automated test for Bevy through BRP

[mockersf]

Objective

• Show how a Bevy app can be automated through BRP

Solution

• Example app_under_test is a basic app with a randomly placed button. when the button is clicked, the app quit
• Example automated_test click that button through BRP using WindowEvent so that it goes through the whole of Bevy

Testing

• Run both example and they both exit

[kfc35]

I see the value in these examples as is (to demonstrate manipulating a live-app for testing purposes), but I wonder if these examples could be made more compelling by exploring it from the prospective of an app creator attempting to incorporate automated tests into their project.

For example, it might be helpful to setup how this could look if someone wants to have these automated tests run in CI by giving an example GitHub Action config or something alongside (although something like that might probably be in the works for this repo itself?, in which case I would just express that such a setup may be useful to share with app creators as well!).

I’m also not sure if the phrase “Automated Test” sounds too vague for what this is. I would liken this to an “(End-to-end?) Integration Test" since it tests running a whole app.

[kfc35]

Just to link back to the other example in some way optionally

Suggested change

	//! ```
	//! ```
	//! This example can be paired with the `automated_test` example, which will run an automated
	//! test on this app.

[kfc35]

nit: I think the example could be more compelling if these print statements were in logical coordinates to match what’s going on in automated_test so the viewer sees numbers match

[kfc35]

Suggested change

	.add_plugins(RemotePlugin::default())
	// To make the app available for automated testing, we add these
	// remote plugins to expose API’s for a testing framework to call.
	.add_plugins(RemotePlugin::default())