My all time favorite too. I still return to this game every few years. If you're a fan I suggest checking out this book: https://bossfightbooks.com/products/jagged-alliance-2-by-dar...
You can do that with a simple terminal command as well, btw. https://gist.github.com/lauri/84674ab22aafc4e0f398a52a53cfd7...
One such game is Jagged Alliance 2. See here: https://github.com/dariusk/ja2 Some fine folks have also made a version that works on modern computers: https://github.com/ja2-stracciatella/ja2-stracciatella
Here it is: https://github.com/lauri/minitest-apidoc It isn't something I would encourage others to use in its current state, but maybe it will give you some ideas. It uses Ruby's Minitest and adds some syntax to it.…
I always thought it would be a good idea to generate API documentation from tests. Kind of the same idea you have but the other way around. The problem I used to have is that if you write your documentation by hand it…
My all time favorite too. I still return to this game every few years. If you're a fan I suggest checking out this book: https://bossfightbooks.com/products/jagged-alliance-2-by-dar...
You can do that with a simple terminal command as well, btw. https://gist.github.com/lauri/84674ab22aafc4e0f398a52a53cfd7...
One such game is Jagged Alliance 2. See here: https://github.com/dariusk/ja2 Some fine folks have also made a version that works on modern computers: https://github.com/ja2-stracciatella/ja2-stracciatella
Here it is: https://github.com/lauri/minitest-apidoc It isn't something I would encourage others to use in its current state, but maybe it will give you some ideas. It uses Ruby's Minitest and adds some syntax to it.…
I always thought it would be a good idea to generate API documentation from tests. Kind of the same idea you have but the other way around. The problem I used to have is that if you write your documentation by hand it…