Additonal test cases

You be better off calling these field something that give an indication of what they do.

clickAction1 or better yet view1ClickAction and view1ClickAction2 ....

It might also make sense to create a method called createMockAction(which takes in a viewId and TriggerType) and then sets up mock objects in the method.