Hi Paul,
as you note, defining a login macro would do exactly what your customer
looks for. Nevertheless a macro makes only sense when it is reused
multiple times.
In your groovy example, could you imagine cases where the name of your
closure differs from the value of your reportAs attribute? If not,
perhaps could we imagine a way to notify the result listener that a
closure has been entered and that it should be displayed in the report
just like a macro call.
Cheers,
Marc.
Paul King wrote:
>
> I have a customer that would like to add some convention or extra
> attribute for reporting of groups. They would like something like:
>
> <group description="..." reportAs="login">
> ...
> </group>
>
> It is actually used within our DSLs in Groovy:
>
> def login(...) {
> ant.group(description:'...', reportAs:'login') {
> ...
> }
> }
>
> The 'reportAs' or 'label' or 'info' attribute would appear in the
> report in bold instead of the current step name of 'group'.
> This would allow our DSLs to end up more naturally reflected
> in the reports.
>
> Does this sound like it would be of general interest?
>
>
> Cheers, Paul.
> P.S. we could also explore whether we could make macrodef's
> or other steps/tasks be able to make use of such a feature.
> _______________________________________________
> WebTest mailing list
> [email protected]
> http://lists.canoo.com/mailman/listinfo/webtest
>
--
Blog: http://mguillem.wordpress.com
_______________________________________________
WebTest mailing list
[email protected]
http://lists.canoo.com/mailman/listinfo/webtest
