Before testing Data Base Procedures and Triggers, Tester should know that what is the Input and out put of the procedures/Triggers, Then execute Procedures and Triggers, if u get answer that Test Case will be pass other wise fail.
Create queries with the data which triggers/procedures should not allow, if the transactions pass, triggers not fired if transaction fails triggers fired.
The concept is simple.Let us take the example of a trigger, say, an update trigger for the employee table.Now, the logic here is, let's say when a row is modified(for eg, Emp name is being changed), that information needs to be emailed to a person.We can use triggers to do this. By setting a trigger on an action, we indirectly ensure that, whenever that action takes place, the corresponding trigger will fire and the commands in the trigger will get executed.
