When developing a new section of code functionality with modules I'm not familiar, I'll often create a set of unit tests that are for "tinkering" and interactively analyzing the results in the debugger.
These tests are not good "unit tests" because they often will not be reproducible without some setup from another human. (i.e. not good for automated testing and CI).
Are these just throw-away code? I see some minimal value in these tests, just above the "throw-away" threshold, but barely.
What would I call these tests, so that another developer could obviously know their purpose when coming into the project for the first time?
I've considered calling them "sandbox" tests?
The main purpose of this question is to gather what the community at large would call these.