I think weekly report makes sense. When we try to cut a release, we would
like to see the reports too.
Thanks,
Raymond
--------------------------------------------------
From: "Luciano Resende" <[EMAIL PROTECTED]>
Sent: Wednesday, June 11, 2008 2:49 PM
To: <tuscany-dev@ws.apache.org>
Subject: Re: Good practice for disabling/ignoring failing test cases
+1 for using this pattern to disable/ignore tests that are failing.
How about also running the script in an automated fashion and sending
an e-mail to the list with the results ? What would be a good interval
for running the script ?
On Wed, Jun 11, 2008 at 1:03 PM, Kevin Williams <[EMAIL PROTECTED]>
wrote:
The vtest contributors get credit for this pattern! :-) We also have
a Ruby script that scans the test source and, among other things,
lists ignored tests and the associated blocking Jiras.
On Wed, Jun 11, 2008 at 11:49 AM, Simon Laws <[EMAIL PROTECTED]>
wrote:
On Wed, Jun 11, 2008 at 6:43 PM, Vamsavardhana Reddy
<[EMAIL PROTECTED]>
wrote:
Thanks Raymond for pointing this out. We never used this strategy in
Geronimo (infact, I have never put any JIRA number in any of the source
files other that Release Notes may be). I have come across this in
Tuscany
source code and have been following it consistently from then on.
Should
give credit to who ever started this in Tuscany :)
++Vamsi
On Wed, Jun 11, 2008 at 11:02 PM, Raymond Feng <[EMAIL PROTECTED]>
wrote:
> Hi,
>
> I see Vamsi uses the following strategy to disable failing unit test
cases.
>
> @Test
> @Ignore("TUSCANY-xxxx") // Ignore the test case due to JIRA
> TUSCANY-xxxx
> public void testMySrtuff() {
> }
>
> I think it's a very good practice we should follow to maintain a
> clean
> build while keep track of the ignored failing test cases with JIRAs.
>
> Thanks,
> Raymond
>
+1 good idea
Simon
--
Luciano Resende
Apache Tuscany Committer
http://people.apache.org/~lresende
http://lresende.blogspot.com/
