Mailing-List: contact dev-help@chemistry.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@chemistry.apache.org
Date: Wed, 13 Aug 2014 22:52:13 +0000 (UTC)
From: "Gabriele Columbro (JIRA)" <jira@apache.org>
To: dev@chemistry.apache.org
Message-ID: <JIRA.12673664.1381747128850.77385.1407970333488@arcas>
In-Reply-To: <JIRA.12673664.1381747128850@arcas>
References: <JIRA.12673664.1381747128850@arcas>
Subject: [jira] [Updated] (CMIS-728) JUnitHelper silently swallows
 exceptions
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/CMIS-728?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:all-tabpanel ]

Gabriele Columbro updated CMIS-728:
-----------------------------------

    Fix Version/s:     (was: OpenCMIS 1.0.0)
                   OpenCMIS 0.12.0

> JUnitHelper silently swallows exceptions
> ----------------------------------------
>
>                 Key: CMIS-728
>                 URL: https://issues.apache.org/jira/browse/CMIS-728
>             Project: Chemistry
>          Issue Type: Bug
>          Components: opencmis-tck
>    Affects Versions: OpenCMIS 0.10.0
>            Reporter: Samuel Langlois
>            Assignee: Florian M=C3=BCller
>             Fix For: OpenCMIS 0.12.0
>
>         Attachments: CMIS-728.patch
>
>
> The class {{org.apache.chemistry.opencmis.tck.impl.JUnitHelper}} is not h=
elping much ;-)
> We use it to run the TCK, but whenever an exception occurs as part of the=
se tests, it gets swallowed by this line, and we lose precious information =
on what actually happened:
> {code}
> Assert.fail(e.getMessage());
> {code}
> It would be better to attach the whole stack trace to the failure message=
.
> However, I think the simplest would be to let the Exceptions pass and pop=
 at the surface.
> Here is a patch to do just that, if it helps.
> Thanks!


--
This message was sent by Atlassian JIRA
(v6.2#6252)