You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sentry.apache.org by "Sravya Tirukkovalur (JIRA)" <ji...@apache.org> on 2016/03/09 22:03:42 UTC
[jira] [Updated] (SENTRY-410) Some negative test cases do not check
for specific Sentry exceptions
[ https://issues.apache.org/jira/browse/SENTRY-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sravya Tirukkovalur updated SENTRY-410:
---------------------------------------
Fix Version/s: (was: 1.7.0)
1.8.0
Moving all unresolved jiras with fix version 1.7.0 to 1.8.0. Please change the fix version if you intend to make it into 1.7.0 release.
> Some negative test cases do not check for specific Sentry exceptions
> --------------------------------------------------------------------
>
> Key: SENTRY-410
> URL: https://issues.apache.org/jira/browse/SENTRY-410
> Project: Sentry
> Issue Type: Test
> Affects Versions: 1.4.0
> Reporter: Sravya Tirukkovalur
> Fix For: 1.8.0
>
>
> in Context.java:
> {noformat}
> // verify that the sqlexception is due to authorization failure
> public void verifyAuthzException(SQLException sqlException) throws SQLException{
> verifyAuthzExceptionForState(sqlException, AUTHZ_EXCEPTION_SQL_STATE);
> }
> {noformat}
> This just checks for status 42000, which would also be the case for other failures other than SemanticExceptions. We need to make stronger checks in the tests.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)