The Stack Trace View should be relatively stable from now on. It's a candidate for automated testing.

One idea is to produce a recording of a Java program where we have total control of some stack traces. For example, we could have a well-known and deterministic path through the program and we throw some throwable in some methods. We should then be able to get the stack traces of only those e.g. exception events, so that we know what the stack trace should look like.

If we design that Java Program cleverly, we can have a tree that branches in interesting ways. We would then have Jemmy work with that Stack Trace view.