Setting up a bunch of code to make the product perform repeated behaviours unattended; then producing red and green numbers on a screen; then reviewing neither the numbers, nor the outcome, nor the process, nor the product critically... also not a test.

Making the product do something is not a test. Making the product do something, challenging it, observing it, evaluating it, with intention to learn something about it—and with special focus on risk, on discovering problems that matter, and on not being fooled... THAT's a test.