[abbot-users] Entity includes in script files - Ant parameter replacement semantics?

[<Jos...@cs...>]

Good point, I'm not using Costello and am hand writing the test script =
files.

Saving back out would certainly put everything in one big file again.

The main aim is to build a common set of actions that can be dragged =
into many main test scripts, for example in role based testing.

Its currently working fine in my local hacked version and I'm happy to =
issue a patch to make schema validation configurable and support entity =
includes out of the box.

Since I'm at it, has anyone thought of using ant parameter replace =
semantics in the abbot script files?

It would be a great way to make chunks of script files more re-usable:

e.g.

<action method=3D"actionSomeAction" =
class=3D"com.test.SomeComponentTester" =
args=3D"SomeComponent,${some.property.set.in.ant}"/>

and have this property expand: some.property.set.in.ant

Canoo WebTest extends ant directly and this is a feature that I have =
used extensively, that and the ability to store a parameter for later =
use (like the id for a server generated object)

Apologies if this is rehashing someone else's comments,

Josh

Subject:	Re: [abbot-users] Entity includes in script files
Not a bad idea, but if the script loader doesn't actually know about=20
the include, there's no way it's going to be able to write the script=20
back out in the same way.

BTW, this might be a good approach to handling a common set of=20
<component> definitions, as was brought up recently.

On Oct 25, 2005, at 12:22 AM, <Jos...@cs...> wrote:

> Hi guys,=20
>  =20
>  Just getting to grips with a large scale Abbot testing project and=20
> was thinking that using entity includes for pulling in chunks of XML=20
> into a script would be useful.=20
>  =20
>  The only way I could get this to work was to hack Script.java and=20
> change the method at line 331 to:=20
>  =20
>  public void load(Reader reader, String fileName)=20
>  =20
>  And then pass this file name as the system id to:=20
>  =20
>  Document doc =3D builder.build(reader, fileName);=20
>  =20
>  I also disabled schema validation as external dtd entity includes and =

> external schema validation don't play nicely.=20
>  =20
>  Perhaps this could become a system property? Whether you want schema=20
> validation enabled or not, then entity includes would just work with=20
> this flag disabled.=20
>  =20
>  To include any xml data into a script file:=20
>  =20
>  <?xml version=3D"1.0" encoding=3D"UTF-8"?>=20
>  <!--=20
>  Declare the external includes=20
>  -->=20
>  <!DOCTYPE SYSTEM [=20
>  <!ENTITY someName SYSTEM "./some_file.xml">=20
>  ]>=20
>  =20
>  <AWTTestScript>=20
>  =20
>  &someName;=20
>  =20
>  ....=20
>  =20
>  </AWTTestScript>=20