Hi Helge,
OOoProgramDir is set, and the OOo it specified are launched. But after that,
when checking if
the WelcomeDialog exists, the script is stoped. Testtool and OOo don't quit.
Just like we press
Shift+F5 to Cancel the test. See comments in the hStartTheOffice below.
[quote]------------------------------------------------------------------------------------
sub hStartTheOffice (optional sProfPath as String, optional sProfParameter as
String)
......
'///+<li>To disable the configuration lock dialog <i>-nolockcheck</i> is also
appended</li>
'///+<li>To enable the automated testing <i>-enableautomation</i> has been
added</li>
'///+<li>If you make a remote-test, the office process can't be started by the
testtool; you would get an error message</li>
try
if IsMissing (sProfPath) then
sStartUpOffice
'/////////////////////This can start up office
......
Kontext "WelcomeDialog"
if WelcomeDialog.Exists(2) then '/////////////////////Test
stopped after execute this instruction
......
end if
'///+</ol>
'Disable Quickstarter internaly
hDisableQuickstarterAPI
' put application on MacOS X to most front
raiseApplication
end sub
[/quote]------------------------------------------------------------------------------
I found the "GUI Platform" number is 18, which doesn't exist in the list in sub
GetToolPlatform in
global/system/includes/sysinfo.inc
[quote]------------------------------------------------------
sub GetToolPlatform
......
GUI = GetGUIType
select case GUI
......
end select
......
select case GUI
case 1:
......
case 2:
.......
case 3:
......
case 4:
'UNIX
select case iGuiVersion
'/////////////////////have no 18
case 01 : gSystemnummer = SYS_SOL
case 02 : gSystemnummer = SYS_SCO
case 03 : gSystemnummer = SYS_LIN
case 04 : gSystemnummer = SYS_AIX
case 05 : gSystemnummer = SYS_X86
case 06 : gSystemnummer = SYS_IRI
case 07 : gSystemnummer = SYS_HP
case 08 : gSystemnummer = SYS_FBSD
case 12 : gSystemnummer = SYS_OSX
case 13 : gSystemnummer = SYS_PPC
case 14 : gSystemnummer = SYS_NBSD
case 15 : gSystemnummer = SYS_LIN64
case 16 : gSystemnummer = SYS_LINSPARC
case else: Print "Unknown OS ("+GUI+"/"+iGuiVersion+") please
insert in sysinfo.inc::GetToolPlatform. TestTool will try to use the same
environment as Solaris SPARC uses."
gSystemnummer = SYS_SOL
end select
end select
gtPlatform = PlatFormExt(gSystemnummer)
gtSYSName = PlatFormName(gSystemnummer)
end sub
[/quote]----------------------------------------------------------------------------
Do you have any further clues?
Thank you!
Lihua
发件人： Helge Delfs
发送时间： 2009-03-20 13:47:38
收件人： dev
抄送：
主题： Re: [qa-dev] [automation]Can VCLtesttool run under MIPS CPU?
Hi Lihua,
Am 20.03.09 02:55, Peter Junge schrieb:
>>>> We tried to run VCLTesttool under loongson platform. But failed. First
>>>> probe showes no data transfered to the server. VCLTesttool stop to run
>>>> script after: if (WelcomDialog.exist(2))
This is due to the testtool can't find or start the office installed on
the system. Is your OOoPrgramDir in testtoolrc set ?
> As the TT uses TCP/IP to connect to the soffice process, its at least
> worth a try. I know that remote testing is possible in theory, but never
> tried it. Hopefully the team in Hamburg can give us a hint.
I did remote testing when started working with VCLTestTool 10 years ago
:-) I currently don't have any experience doing remote testing with
current testscripts. May be there must be some adaptions to the testcode
in some areas but you can give it a try.
AFAIR you just have to change the hostname from 'localhost' to hostname
where office is installed.
Good luck :-)
Best Regards
Helge
--
===============================================================
Sun Microsystems GmbH Helge Delfs
Nagelsweg 55 Quality Assurance Engineer
20097 Hamburg OOo Team Lead Automation
http://qa.openoffice.org mailto:[email protected]
http://wiki.services.openoffice.org/wiki/User:Hde
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
