Developers!!!

[Ann]

Hi

I was wondering if there was a graceful way to log the application
crash. I am trying to test an app who stability is still maturing.

Also I noticed when the view is not found (say null) and test perform
click on it, there is assertion thrown and the test terminates. Is
there a smooth or gracful way of logging it (say ok, this view is
modified in this build and so moving on to test the next testcase) and
continue with the next test in the test suite? I hope my question is
clear.

Thanks
Ann.

[Christopher Orr]

On 22/01/2011 18:22, Ann wrote:
> Hi
>
> I was wondering if there was a graceful way to log the application
> crash. I am trying to test an app who stability is still maturing.
>
> Also I noticed when the view is not found (say null) and test perform
> click on it, there is assertion thrown and the test terminates.

I imagine it would be smarter to detect that the View you searched for
is `null` and then *not* click on it, but instead call the JUnit fail()
method.

Chris

[Ann]

I do that, but the page has tens of them, I wanted to know if there is
another option.

Ann

[Christopher Orr]

If you're doing this lots of times, would it be possible to just create
a "get view" helper method which does this check for null and calls
fail() each time?

Chris