As described in the mini README, I had to split the tests into multiple files, as I didn't find any option of WTR to refresh files between runs.
I suppose potentially we could introduce such logic ourselves by using the "barebones" variant of html tests (the 2nd code snippet in this page), where runTests would be replaced by direct calls to specific test cases and we would perform a reload after each of them, but I'm not sure it's worth it, let me know if I should give it a try 🚀
EDIT: Or, we could leverage undoPrehide() to get rid of the element again. However, I'm not sure if we want to couple the tests to its implementation like that.
As described in the mini README, I had to split the tests into multiple files, as I didn't find any option of WTR to refresh files between runs.
I suppose potentially we could introduce such logic ourselves by using the "barebones" variant of html tests (the 2nd code snippet in this page), where
runTestswould be replaced by direct calls to specific test cases and we would perform a reload after each of them, but I'm not sure it's worth it, let me know if I should give it a try 🚀EDIT: Or, we could leverage undoPrehide() to get rid of the element again. However, I'm not sure if we want to couple the tests to its implementation like that.