I was reading the POD for Test::More today and something struck me as odd:
There are rare cases when you will not know beforehand how many tests your script is going to run. In this case, you can declare that you have no plan. (Try to avoid using this as it weakens your test.)Would someone mind explaining why that weakens the test? As a contrived example, what if I want to test that every record in a file got loaded to a database? The ok function (and it's bretheren) are very good at making assertion-style statements (I personally like "is"). I don't know how many records will be in the file, so I won't know how many tests will be executed before hand.
thor
Feel the white light, the light within
Be your own disciple, fan the sparks of will
For all of us waiting, your kingdom will come
In reply to No plan "weakens" my Test scripts? by thor
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |