I recently tweeted:
A new test sequence: CRUDCA: Create, read, update, delete, create again. — Because sometimes an object can’t be again. #software #testing
I got some feedback from this, so let’s present the idea in a bit more detail.
Many systems know these 4 basic actions for an object:
- Create
- Read
- Update
- Delete
That’s where the abbreviation CRUD comes from. In many cases that’s also a rather typical test sequence to check whether the system can handle these actions. — And often it’s also good enough testing.
But sometimes there are more restrictions at work:
- An object may only be created once and only once. It may be removed, but then not created again.
- It must be possible to create an object with identical properties again and again.
This is how I came up with ‘CRUDCA’: Create, read, update, delete, create again.
Obviously, it depends on the particular (business) context whether or not it is allowed to create a certain object. The ‘create again’ part covers the action of attempting to create the object. The expected behaviour comes from the requirements or specification of the system.
