Judson Valeski wrote:
>
> If you don't know what it feels like to checkin code w/ confidence that
> you're not going to regress the smoketests, try it, you'll like it. The
> daily smoketesters are not your personal testing partners, and tinderbox
> is not your build verification tool :-).
>
Not only does your stuff need to work, it needs to be fast.
Here are the performance tests that tbox is running, yes
they are easy one-liners:
Startup test:
(win32 help here? maybe this works on win32?)
mozilla/tools/performance/startup/startup-unix.pl
XUL test:
mozilla -chrome file://<path>/mozilla/xpfe/test/winopen.xul
Pageloader:
(btek running local copy of this, mozilla.org version on the way)
http://cowtools.mcom.com/page-loader/loader.pl
Part of moving forward on performance means "don't go backwards".
That means you've got to pay attention to what you are checking in,
and trying to fix regressions soon after they happen.
-Chris
