Get first feedback on chapters in sections `1. Introduction` and `2. Basic`

[richelbilderbeek]

The earlier chapters that introduce Bevy are taking shape. When ready, ask for feedback!

[richelbilderbeek]

Ready! Time to ask the community!

[richelbilderbeek]

Posted at https://discord.com/channels/691052431525675048/1278594326963818582:

Dear Bevy community,

I think this is the right place to ask for feedback on a book about Bevy, as it is a type of help.

I would enjoy any feedback about the 1. Introduction and 2. Basic sections of the book 'Developing Bevy games using TDD' as can be found at https://richelbilderbeek.github.io/bevy_tdd_book/ .

Guidelines for contributing can be found at https://github.com/richelbilderbeek/bevy_tdd_book/blob/master/CONTRIBUTING.md .

Thanks for those that help out, you'll be added to the 'Acknowledgements' section at https://richelbilderbeek.github.io/bevy_tdd_book/misc/contributors/ , with already some community members from here lister 🙂

I expect to process the feedback in around October, so no rush!

Thanks and cheers, Richel

[richelbilderbeek]

Feedback collected:

Shane Celis: This is an exciting project because games traditionally have been pretty difficult to test. I’ve seen a few test harnesses made for bevy that have impressed me with how testable it can be but it’d be a huge asset to have a guide on how one could do that.

nixpulvis:

Although the main function is a bad candidate, one can test it if one really wants to! For example, by writing a script that > simulates input, such as sending the standard key combination ALT + F4 to the program to close it. However, one needs > to decide on a per-project basis if this extra testing is worth the extra effort.

I'd call these "integration tests" and perhaps leave that as a TODO or something for the future. It would be really cool to have a guide on setting up mock inputs and even doing visual diffs on the UI.

[richelbilderbeek]

I am closing the Discord feedback now.