Let\'s say I want to write a function that validates an email address with a regex. I write a little test to check my function and write the actual function. Make it pass.>
If you are testing the same functionality, I'd check them in the same test, with multiple assertions, provided that your tests remain simple enough.
Some people advocate that every test must have just a single assertion, because the test must be very, very, very simple.
If the test is not simple, say that you have loops and ifs, you would need a test for the test itself, to check that its logic is correct, and this is not good.
If your test has multiple assertions, but still remain simple (no loops, no ifs) and the multiple assertions are testing the same thing, then I'd not be so aggressive in advocating "single assert per test". The choice is yours.