Testing the alert is not going to give you exactly the information you'd expect when the alert has to go over multiple tables in the database. One thing to not, testing isn't actually testing the alert to make sure it will interact with the correct devices. The testing functionality does two things (1) can the action be fired, in this case an email and (2) translate the variables into data. If the alert test is showing data and not the variables, it's working. You'd see similar results if you test an alert based on a custom poller. The test ends up grabbing a random value to send in the action. As long as you're not getting the variable back, the test was successful. Now, having said that, when the alert actually fires, the variables in the action will take into account the group member that triggered the alert based on the information the alert trigger is looking at. It will then grab the variable data relevant to that group member. To truly test the alert, you'd basically reverse the trigger condition, have it only email to you, and you'll see that variable information you'd expect.