minus-squarethirtyfold8625@thebrainbin.orgtoFunny@sh.itjust.works•So, how's the job search going?linkfedilinkarrow-up1·1 day agoI think there’s one question you should answer in order to fully describe your “testing framework”: is it being used for “end to end tests” or “integration tests” or “unit tests”? https://k-hartanto.medium.com/testing-pyramid-and-testing-ice-cream-cone-what-is-the-difference-6ddde3876c20 For unit tests, something like https://en.wikipedia.org/wiki/JUnit is useful. For testing a program after it’s deployed, something like https://jbehave.org/reference/stable/story-syntax.html is useful. You get different information about your program from each type of testing, and one type can detect issues even if the other didn’t, so doing both is useful. linkfedilink
minus-squarethirtyfold8625@thebrainbin.orgtoFunny@sh.itjust.works•So, how's the job search going?linkfedilinkarrow-up1·1 day agoYour (verbose and harder to understand) example reminds me of https://jbehave.org/reference/stable/story-syntax.html linkfedilink
minus-squarethirtyfold8625@thebrainbin.orgtoFunny@sh.itjust.works•So, how's the job search going?linkfedilinkarrow-up6·2 days agohttps://en.wikipedia.org/wiki/Cucumber_(software) linkfedilink
I think there’s one question you should answer in order to fully describe your “testing framework”: is it being used for “end to end tests” or “integration tests” or “unit tests”? https://k-hartanto.medium.com/testing-pyramid-and-testing-ice-cream-cone-what-is-the-difference-6ddde3876c20
For unit tests, something like https://en.wikipedia.org/wiki/JUnit is useful. For testing a program after it’s deployed, something like https://jbehave.org/reference/stable/story-syntax.html is useful. You get different information about your program from each type of testing, and one type can detect issues even if the other didn’t, so doing both is useful.