You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by Raphael Bircher <r....@gmx.ch> on 2012/06/20 10:43:30 UTC
[VCLAuto] Problems with build.xml
Hi all
I try to run VCLAuto, the new GUI Testtool. I settet up a Win 7 VM for
it and I followed the guide on the wiki
http://wiki.services.openoffice.org/wiki/QA/vclauto
But if I try to run build.xml via ant, to get the junit.jar, I got the
following error: http://pastebin.com/ZRc3frep
Turning the firewall of does not help. Can I simply load the junit.jar
manualy, or is there an other problem. Thanks for help.
Greetings Raphael
--
My private Homepage: http://www.raphaelbircher.ch/
Re: [VCLAuto] Problems with build.xml
Posted by Jürgen Schmidt <jo...@googlemail.com>.
On 6/21/12 11:50 PM, Raphael Bircher wrote:
> Hi Zhe Liu
>
> Am 21.06.12 07:49, schrieb Zhe Liu:
>> Hi Raphael Bircher,
>> Did you run the testing successfully? I wanna get some feedback to improve it.
>>
>>
> I think, the tool itself works, but I run in same trubble. Take a look
> at http://people.apache.org/~rbircher/download/ooo_bugs/vclauto/ maybe
> you can help me.
>
> Same feedback from the tool. I can compare, because i worked with both.
>
> Installation.
> Both, the old and the new TT are not easy to install. The old one was
> not so easy cause configuration and so on. The new one is not easy
> because of the depencity (Ant, Eclipse, junit) So, it's only samething
> for power Users.
>
> I find it harder to execute the new Testtool as the old one. By the old
> one you have had simply to load the script and run it. By the new one
> you have to take a look to the parameters. But this is only a entry
> barriere.
>
> Debuging: Sametimes usefull can be the screenshot wich are taken by the
> VCLAuto. I see no avantage by searching the errors. By both you have to
> understand source Code. For my point of view it's more a question of the
> taste, Java or Basic. The Scipts from VCLAuto are more readable, because
> they ar small and smart. But i have no illusion here, this will change
> over the time ;-)
>
> From the points above, VCLAuto and VCLTestTool are equal solutions.
> Well, VCLAuto is maybe newer. But I have two big critisme to VCLAuto
>
> - VCLAuto can't test Localized Builds at the moment.
> - We have much less tests for VCLAuto then for the VCLTestTool (I beleve
> that the old TestTool covers 20 Times more then the VCLAuto Tests now)
> This is also the reason why VCLTestTool use much more time to run.
> VCLAuto is not realy faster, it has simply less Testcase, and from a QA
> point of view, this is bad news.
>
> From my point of view, the VCL auto is atm not a equal replacement for
> the VCLTestTool. The VCLAuto is indeed the fresher tool, but also less
> mature. I support the move to VCLAuto, but i also have to remind every
> one here that there is still a load of Work.
nobody said that the new tool is a 100% replacement of the old tool. The
old one is not maintained anymore and nobody writes new tests :-( The
new one is a clean fresh implementation where people know the code and
where people have interest to maintain it. And of course where people
have started to write either new tests or convert old existing tests.
Our challenge is to build some new knowledge in this area and document
everything to make it easy for people to get started and to help.
Juergen
Re: [VCLAuto] Problems with build.xml
Posted by Zhe Liu <al...@gmail.com>.
2012/6/22 Raphael Bircher <rb...@apache.org>:
> Hi Zhe Liu
>
> Am 21.06.12 07:49, schrieb Zhe Liu:
>> Hi Raphael Bircher,
>> Did you run the testing successfully? I wanna get some feedback to improve it.
>>
>>
> I think, the tool itself works, but I run in same trubble. Take a look
> at http://people.apache.org/~rbircher/download/ooo_bugs/vclauto/ maybe
> you can help me.
Firstly thanks for your trying.
Currently, testing can be only performed in English locale. I saw your
OpenOffice UI is not English. The test script can be written
language-neutral, but the existing scripts is not. The tool is
brand-new. There is still a lot of work to do next.
>
> Same feedback from the tool. I can compare, because i worked with both.
>
> Installation.
> Both, the old and the new TT are not easy to install. The old one was
> not so easy cause configuration and so on. The new one is not easy
> because of the depencity (Ant, Eclipse, junit) So, it's only samething
> for power Users.
The old testtool IDE is developed and maintained by OpenOffice
developers. The key issue is that nobody works on it now.
Ant+Eclipse+JUnit are very popular and active open source projects. We
don't need to spend time in developing/maintaining them. I admit
these tools are more acceptable by developers, maybe not by common
users. If you only concern about installation, we can pack these tools
in one out-of-box zip.
>
> I find it harder to execute the new Testtool as the old one. By the old
> one you have had simply to load the script and run it. By the new one
> you have to take a look to the parameters. But this is only a entry
> barriere.
As far as I know, you also need to set several parameters before
running testing with the old testtool.
Anyway, I will provide a default value and a global place to set AOO's
location. There will be no need to set it for each test class.
>
> Debuging: Sametimes usefull can be the screenshot wich are taken by the
> VCLAuto. I see no avantage by searching the errors. By both you have to
> understand source Code. For my point of view it's more a question of the
> taste, Java or Basic. The Scipts from VCLAuto are more readable, because
> they ar small and smart. But i have no illusion here, this will change
> over the time ;-)
Did you use the Eclipse's debugging, source code reference and search
function? It's far more power than the old VCLTesttool, and more
complex. Another awesome feature is the code refactor of Eclipse. As
you know, test script often changes as design changs. Code refactor
can save us a lot of time.I will write some guide to explain it later.
As I mentioned before, VCLAuto just gives us a chance to write GUI
testing in Java and not to replace VCLTesttool. Java is far more
popular programming language than Basic, maybe it can attract more
people to write testing scripts.
>
> From the points above, VCLAuto and VCLTestTool are equal solutions.
> Well, VCLAuto is maybe newer. But I have two big critisme to VCLAuto
>
> - VCLAuto can't test Localized Builds at the moment.
> - We have much less tests for VCLAuto then for the VCLTestTool (I beleve
> that the old TestTool covers 20 Times more then the VCLAuto Tests now)
> This is also the reason why VCLTestTool use much more time to run.
> VCLAuto is not realy faster, it has simply less Testcase, and from a QA
> point of view, this is bad news.
>
> From my point of view, the VCL auto is atm not a equal replacement for
> the VCLTestTool. The VCLAuto is indeed the fresher tool, but also less
> mature. I support the move to VCLAuto, but i also have to remind every
> one here that there is still a load of Work.
>
> Greetings Raphael
VCLAuto is very young. Currently, the existing test cases are more
proper for demo we can write gui testing in Java and not enough for
replacement of VCLTestTool. Indeed there is still a load of work, but
pls be patient. I also hope someone here to coninue to maintain
VCLTestTool. The number of its legacy scripts is very big.It can cover
very many functions and still is very valuable in the current
situation.
--
Best Regards
>From aliuzhe@gmail.com
Re: [VCLAuto] Problems with build.xml
Posted by Raphael Bircher <rb...@apache.org>.
Hi Zhe Liu
Am 21.06.12 07:49, schrieb Zhe Liu:
> Hi Raphael Bircher,
> Did you run the testing successfully? I wanna get some feedback to improve it.
>
>
I think, the tool itself works, but I run in same trubble. Take a look
at http://people.apache.org/~rbircher/download/ooo_bugs/vclauto/ maybe
you can help me.
Same feedback from the tool. I can compare, because i worked with both.
Installation.
Both, the old and the new TT are not easy to install. The old one was
not so easy cause configuration and so on. The new one is not easy
because of the depencity (Ant, Eclipse, junit) So, it's only samething
for power Users.
I find it harder to execute the new Testtool as the old one. By the old
one you have had simply to load the script and run it. By the new one
you have to take a look to the parameters. But this is only a entry
barriere.
Debuging: Sametimes usefull can be the screenshot wich are taken by the
VCLAuto. I see no avantage by searching the errors. By both you have to
understand source Code. For my point of view it's more a question of the
taste, Java or Basic. The Scipts from VCLAuto are more readable, because
they ar small and smart. But i have no illusion here, this will change
over the time ;-)
>From the points above, VCLAuto and VCLTestTool are equal solutions.
Well, VCLAuto is maybe newer. But I have two big critisme to VCLAuto
- VCLAuto can't test Localized Builds at the moment.
- We have much less tests for VCLAuto then for the VCLTestTool (I beleve
that the old TestTool covers 20 Times more then the VCLAuto Tests now)
This is also the reason why VCLTestTool use much more time to run.
VCLAuto is not realy faster, it has simply less Testcase, and from a QA
point of view, this is bad news.
>From my point of view, the VCL auto is atm not a equal replacement for
the VCLTestTool. The VCLAuto is indeed the fresher tool, but also less
mature. I support the move to VCLAuto, but i also have to remind every
one here that there is still a load of Work.
Greetings Raphael
Re: [VCLAuto] Problems with build.xml
Posted by Reizinger Zoltán <zr...@hdsnet.hu>.
2012.06.21. 7:49 keltezéssel, Zhe Liu írta:
> Hi Raphael Bircher,
> Did you run the testing successfully? I wanna get some feedback to improve it.
I tried to run tests, but I can not start it.
The build run OK.
When I try to configure the Junit for
testscript/src/testcase/SayHelloToOO.java, I can add VM arguments, but
the test class is empty and I can not add any value to it.
When I add to class "test", I get error messeage: Can not find test
class 'test' in project 'AOO_test'.
I tried to search on test class, the Test selection dialogbox is empty,
Zoltan
>
> 2012/6/20 Raphael Bircher <rb...@apache.org>:
>> Hi Du
>>
>> Am 20.06.12 11:49, schrieb Du Jing:
>>> when you run build.xml via ant(select ant 2),please don't select "test" in
>>> configuration check box,only select the "prepare.dependencies".Hope can
>>> help you~
>>>
>> Yes, it helps, thanks!
>>
>> Greetings Raphael
>
>
Re: [VCLAuto] Problems with build.xml
Posted by Zhe Liu <al...@gmail.com>.
Hi Raphael Bircher,
Did you run the testing successfully? I wanna get some feedback to improve it.
2012/6/20 Raphael Bircher <rb...@apache.org>:
> Hi Du
>
> Am 20.06.12 11:49, schrieb Du Jing:
>> when you run build.xml via ant(select ant 2),please don't select "test" in
>> configuration check box,only select the "prepare.dependencies".Hope can
>> help you~
>>
> Yes, it helps, thanks!
>
> Greetings Raphael
--
Best Regards
>From aliuzhe@gmail.com
Re: [VCLAuto] Problems with build.xml
Posted by Raphael Bircher <rb...@apache.org>.
Hi Du
Am 20.06.12 11:49, schrieb Du Jing:
> when you run build.xml via ant(select ant 2),please don't select "test" in
> configuration check box,only select the "prepare.dependencies".Hope can
> help you~
>
Yes, it helps, thanks!
Greetings Raphael
Re: [VCLAuto] Problems with build.xml
Posted by Li Feng Wang <ph...@gmail.com>.
It's Ok to load junit.jar manually.
2012/6/20 Du Jing <bj...@gmail.com>
> when you run build.xml via ant(select ant 2),please don't select "test" in
> configuration check box,only select the "prepare.dependencies".Hope can
> help you~
>
> On Wed, Jun 20, 2012 at 4:43 PM, Raphael Bircher <r....@gmx.ch> wrote:
>
> > Hi all
> >
> > I try to run VCLAuto, the new GUI Testtool. I settet up a Win 7 VM for
> > it and I followed the guide on the wiki
> > http://wiki.services.openoffice.org/wiki/QA/vclauto
> >
> > But if I try to run build.xml via ant, to get the junit.jar, I got the
> > following error: http://pastebin.com/ZRc3frep
> >
> > Turning the firewall of does not help. Can I simply load the junit.jar
> > manualy, or is there an other problem. Thanks for help.
> >
> > Greetings Raphael
> > --
> > My private Homepage: http://www.raphaelbircher.ch/
> >
>
--
Best Wishes, LiFeng Wang
Re: [VCLAuto] Problems with build.xml
Posted by Du Jing <bj...@gmail.com>.
when you run build.xml via ant(select ant 2),please don't select "test" in
configuration check box,only select the "prepare.dependencies".Hope can
help you~
On Wed, Jun 20, 2012 at 4:43 PM, Raphael Bircher <r....@gmx.ch> wrote:
> Hi all
>
> I try to run VCLAuto, the new GUI Testtool. I settet up a Win 7 VM for
> it and I followed the guide on the wiki
> http://wiki.services.openoffice.org/wiki/QA/vclauto
>
> But if I try to run build.xml via ant, to get the junit.jar, I got the
> following error: http://pastebin.com/ZRc3frep
>
> Turning the firewall of does not help. Can I simply load the junit.jar
> manualy, or is there an other problem. Thanks for help.
>
> Greetings Raphael
> --
> My private Homepage: http://www.raphaelbircher.ch/
>