black box testing for Found Patterns Studio App Store apps about jazz HOT 7 OPEN

https://github.com/moteus/lua-travis-example

from jazz.

@dariusc93 let's chat about this sometime

from jazz.

@dariusc93 srsly

from jazz.

unit tests are more code to maintain, and they don't even verify that the program runs as expected. that's what black box testing is for.

from jazz.

Unit test works to make sure the functions work as intended (eg bindings in this case), not exactly to verify the program will run as expected since there are many factors outside the scope of a function that could impact the operation of the program itself. To test to make sure it works as intended as a whole, making/running examples can show that, or have a larger test scale outside of the scope of a bindings to make sure things work as they should, though in this case, probably would also have to be outside the scope of rust itself.

from jazz.

ideally, we'll test Torchbear with each of FPS' main projects on every change. for example, we have part of File Witness attempting to run with each change right now and something is broken. this is a very useful test because fixing that will ensure that our code and our integrations works as needed. #143

it'd be fairly straightforward to test Simple Webserver with an http request to http://localhost:3000/ that should output the same html document every time. this simple test would cover a lot of components, and alert us with any unforeseen output.

function tests themselves can break, so maintaining them is a bad distraction from maintaining our real code base, especially when code that depends on it would break anyway. Googlers have also made this point in Testing on the Toilet: Test Behavior, Not Implementation.

from jazz.

this is the highest value plan with the smallest size

from jazz.