Schedule for RT 3.2.3?

Just wondering how 3.2.3 is looking. I thought the first release
candidate was going to appear last Monday …

Kevin Murphy

Just wondering how 3.2.3 is looking. I thought the first release
candidate was going to appear last Monday …

As often happens at a small company, “other stuff came up” (much of it
having to do with getting 3.4 ready to go out the door.

3.2.3 was going to go out with the broken bulk update of custom fields
functionality disabled. But Todd’s sent us a nice patch to add back
working bulk update of custom fields. Since it doesn’t come with a test
script, it’s waiting on someone (either me, one of my folks or someone
on the lists) testing out the patch.

Jesse

:slight_smile:

Want to point me at how to test web interface code? Do RT’s
tests actaully pretend to be a browser?

Or, do you just me in-line tests for Web.pm?On Mon, Dec 06, 2004 at 01:31:10PM -0500, Jesse Vincent wrote:

On Mon, Dec 06, 2004 at 11:03:03AM -0500, Kevin Murphy wrote:

Just wondering how 3.2.3 is looking. I thought the first release
candidate was going to appear last Monday …

As often happens at a small company, “other stuff came up” (much of it
having to do with getting 3.4 ready to go out the door.

3.2.3 was going to go out with the broken bulk update of custom fields
functionality disabled. But Todd’s sent us a nice patch to add back
working bulk update of custom fields. Since it doesn’t come with a test
script, it’s waiting on someone (either me, one of my folks or someone
on the lists) testing out the patch.

Jesse

Kevin Murphy


The rt-users Archives

Be sure to check out the RT wiki at http://wiki.bestpractical.com


The rt-users Archives

Be sure to check out the RT wiki at http://wiki.bestpractical.com

:slight_smile:

Want to point me at how to test web interface code? Do RT’s
tests actaully pretend to be a browser?

Web testing is getting much less painful than it used to be.
The current gold standard for RT web testing is lib/t/08_web_cf.pl.in
in the RT 3.3 distribution. It adds a new dependency when running the
test suite, but another dependency in the “DEVEL” section isn’t a big
deal as it’s not required by end-users.

Best,
Jesse