Best practice for selenium tests that have add, update, delete functionality

I have just started writing selenium tests for my asp.net application using MSTests(I triend NUnit, but i didin't see any difference between it and ms...) and I'm liking them so far, except for the part that test fire randomly.

Now I get the part that tests should not be dependant on other tests(!!!), but how will you tests the add, update, delete functionality then if your tests fire randomly and they do not depend on each other?

I can see only 2 ways how to write such a tests:

1. Use OrderedTests, which I don't like.


2. Write one BIG test that does all those things, but then I have a test that does 3 things!