Re: [Javapathfinder-devel] JUnit exceptions

[Peter C. M. <Pet...@na...>]

If you inspect the path at the end of a JPF run, it is only non-empty  
in case there was a property violation (backtracking to the first  
state and not having any non-processed choice anymore *is* the end  
condition for the search)

-- Peter


On Sep 29, 2008, at 6:13 AM, Michal Kebrt wrote:

> After writing a part of JUnitProperty I realized it wouldn't be so  
> straightforward as it seemed to be. For example, JUnit has  
> @Test(expected=...) annotation which shouldn't produce an error when  
> expected exception occurs. Therefore the JUnitProperty should  
> understand some of JUnit internals which is not very clean solution.
>
> I am thinking of inspecting JVM Path object (and maybe other  
> information provided by Reporter) in JUnit's native peer but the  
> path is always empty, why?
>
> MK