Test case token verification with wrong secret always succeeded

The hard coded data in the test case had the previous token format,
and would always fail regardless of whether the secret was wrong or
not. The test is now updated to verify that the verification succeeds
with the correct key and fails with the incorrect one.

Good news is that the code it tests worked :)
Merge pull request #9 from noaresare/pr/wrong_secret_testcase_fix

Test case token verification with wrong secret always succeeded