It's a downside of assertion-based tests. My workaround is to seed the test with print statements, triggered only when a debug flag is set. When the silence scares me, I flip on the debug switch and listen to the reassuring chatter.One of my paranoid fears about the junit assert testing is that it's impossible to tell if a test ran and did everything, or didn't do anything. The output is the same in both cases.Dan.
- Re: [jira] Commented: (DERBY-499) Expose BOOLEAN da... Rick Hillegas
- [jira] Commented: (DERBY-499) Expose BOOLEAN d... Rick Hillegas (JIRA)
- [jira] Commented: (DERBY-499) Expose BOOLEAN d... Andrew McIntyre (JIRA)
- Re: [jira] Commented: (DERBY-499) Expose B... Kathey Marsden
- Re: [jira] Commented: (DERBY-499) Expo... Andrew McIntyre
- Re: [jira] Commented: (DERBY-499) ... Kathey Marsden
- [jira] Commented: (DERBY-499) Expose BOOLEAN d... Rick Hillegas (JIRA)
- Re: [jira] Commented: (DERBY-499) Expose B... Daniel John Debrunner
- Re: [jira] Commented: (DERBY-499) Expo... Rick Hillegas
- Re: [jira] Commented: (DERBY-499) Expose B... Daniel John Debrunner
- Re: [jira] Commented: (DERBY-499) Expo... Rick Hillegas
