When we went to Ready! API, I had been hoping that the assertion editors would get a re-working. However, they still have all of the same short-comings of SoapUI. Specifically, the editors don't ...
I came to find a comment like this, and am glad someone else has the same problem. It gets very cumbersome when working with re-factoring a lot of assertions all at once to deal with the small "default" size of windows for assertion editors.
It would be good to have a "remembered" assertion editor window for each type or to be able to set a default.