openoffice-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Damjan Jovanovic <dam...@apache.org>
Subject Re: Smoke Test to run on a built office
Date Thu, 07 Jul 2016 07:37:57 GMT
If it's not enough to kill the Java test process, you may need to kill
OpenOffice instances too, which run in separate processes.

If you only want to run a specific test, look at
https://wiki.openoffice.org/wiki/QA/test_automation_guide#Run_testing_2 for
how you run only 1 test class.

On Thu, Jul 7, 2016 at 9:28 AM, Patricia Shanahan <pats@acm.org> wrote:

> Thanks, I'll try that.
>
> Meanwhile, how do I get to do a second test run after killing the first
> one? "ant clean" does not help. Killing and restarting Cygwin does not
> help. Rebooting the system does let me run again, but is inconvenient.
>
>
> On 7/7/2016 12:11 AM, Damjan Jovanovic wrote:
>
>> The hung test method from your log is testInsertFunctionViaFormulaBar.
>> What
>> I'd recommend is getting a stack trace of the Java test process, eg. using
>> jstack (since you probably didn't run it with remote debugging enabled),
>> and seeing where in that test method it is stuck.
>>
>> On Thu, Jul 7, 2016 at 1:08 AM, Patricia Shanahan <pats@acm.org> wrote:
>>
>> How does one find out whether the tests have hung, or are just taking
>>> their time? I started them by running ant in the test folder using a
>>> cygwin
>>> shell that has the winenv.set.sh parameters for my AOO412 build.
>>>
>>> It started doing AOO things, with windows appearing, changing, and
>>> disappearing, so I left it to get on with the job. The next time I looked
>>> in on it, there was an empty spreadsheet on the screen. The last few
>>> shell
>>> lines were:
>>>
>>>      [exec]
>>>      [exec] setup -> ok
>>>      [exec] write_status -> ok
>>>      [exec] ---
>>>      [exec]
>>>      [exec] Jul 06, 2016 2:43:03 PM org.openoffice.test.common.Logger
>>> finish
>>>      [exec] INFO: Finish running test method [smokeTest]
>>>      [exec] Jul 06, 2016 2:43:03 PM org.openoffice.test.common.Logger
>>> start
>>>      [exec] INFO: Start running test method
>>> [testInsertFunctionViaFormulaBar]
>>>      [exec] Jul 06, 2016 2:43:03 PM org.openoffice.test.common.Logger
>>> start
>>>      [exec] INFO: Clean up temp directory for test method
>>> [C:\OpenOfficeDev\AOO412\test\testspace\temp]
>>>      [exec] Jul 06, 2016 2:43:04 PM org.openoffice.test.OpenOffice start
>>>      [exec] INFO:
>>> "C:\OpenOfficeDev\AOO412\test\testspace\install\OpenOffice
>>> 4\program\soffice.exe" "-automationport=12479" "-enableautomation"
>>> "-c8ebd53ec8fb426fbe3e4a4beba2533b" "-nofirststartwizard" "-norestore"
>>> "-quickstart=no"
>>>
>>>
>>>
>>> On 7/5/2016 4:42 PM, Damjan Jovanovic wrote:
>>>
>>> Plz see
>>>> http://www.mail-archive.com/dev@openoffice.apache.org/msg27036.html
>>>>
>>>> You probably want the qa tests, which run the (copied) Smoketest
>>>> nowdays.
>>>>
>>>> Damjan
>>>>
>>>> On Wed, Jul 6, 2016 at 12:25 AM, Carl Marcum <cmarcum@apache.org>
>>>> wrote:
>>>>
>>>> Hi all,
>>>>
>>>>>
>>>>> Are there other automated smoke test macros or scripts other than noted
>>>>> below that can be ran on a built office to test basic functionality and
>>>>> make sure nothing major is broken?
>>>>>
>>>>> I found this wiki page [1] that references a sxw document that contains
>>>>> macros and will display a report but I'm not sure how recent it is due
>>>>> to
>>>>> the file extension.
>>>>>
>>>>> The file is smoketestdoc.sxw in main/smoketestdoc/
>>>>> unxlngx6.pro/misc/zip
>>>>> of a build.
>>>>>
>>>>> [1] https://wiki.openoffice.org/wiki/SmokeTest
>>>>>
>>>>> Thanks,
>>>>> Carl
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>>>>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>>>>
>>>>>
>>>>>
>>>>>
>>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>>
>>>
>>>
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message