A normal test suite for a shop proves that good behaviour works: a user logs in, adds a mug to the cart, pays, and sees the right total. These tests are valuable, and our fictional shop.example has 212 of them, all passing. They answer one question: does the feature do what it should?
Security needs the opposite question: what should not be possible? Can one customer open another's invoice? Can a crafted input crash the parser? Can an expired session still act? Few ordinary tests ask these things, because the people writing them are thinking about customers, not attackers.
💡Good to know
For each feature, write down one thing it must refuse to do. Those refusals are your security tests.