You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by Carl Marcum <cm...@apache.org> on 2021/06/12 13:13:13 UTC

rework the automated tests to not require an office build first

Hi All,

cc'd qa@

I think it would be good to rework the test framework to not require 
having just built the office.

Currently, to compile and run the tests, there are dependencies on 
environment settings created and files built into main/solver/<version>.
Mostly things like idlc, regmerge, and javamaker etc. and the UNO jar files.
All these file dependencies are also available in either the office that 
would be under test or the SDK.

I think it would be a benefit for QA and open the use and development of 
automated tests to testers and developers that don't also have a AOO 
build environment.
For instance I can run the test suite against Linux where I have a build 
env but not on Windows where I don't.

The one big thing about this would be it would require a tester to have 
the SDK installed in the office under test.
I think this is a much lower bar than building the office to get them.

Does anyone have an opinion one way or the other?

Thanks,
Carl


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org


Re: rework the automated tests to not require an office build first

Posted by Carl Marcum <cm...@apache.org>.
Hi Arrigo,

On 6/12/21 9:25 AM, Arrigo Marchiori wrote:
> Hello Carl, All,
>
> On Sat, Jun 12, 2021 at 09:13:13AM -0400, Carl Marcum wrote:
>
>> Hi All,
>>
>> cc'd qa@
>>
>> I think it would be good to rework the test framework to not require having
>> just built the office.
> It sounds like a very good idea to me.
>
>> Currently, to compile and run the tests, there are dependencies on
>> environment settings created and files built into main/solver/<version>.
>> Mostly things like idlc, regmerge, and javamaker etc. and the UNO jar files.
>> All these file dependencies are also available in either the office that
>> would be under test or the SDK.
>>
>> I think it would be a benefit for QA and open the use and development of
>> automated tests to testers and developers that don't also have a AOO build
>> environment.
>> For instance I can run the test suite against Linux where I have a build env
>> but not on Windows where I don't.
>>
>> The one big thing about this would be it would require a tester to have the
>> SDK installed in the office under test.
>> I think this is a much lower bar than building the office to get them.
>>
>> Does anyone have an opinion one way or the other?
> IMHO I am totally for it.
>
> Unfortunately I do not have resources (and knowledge) to help you at
> the moment, but if this is not an urgent matter, we can plan it.

Thanks, I was planning on doing the heavy lifting :)

I've already got a lot of it working on a CentOS 8 machine that I can't 
build office on and the tests build and run.

There are more use-cases like running them against the "installed" build 
for those that want to build office and test it in place that I still 
need to work out.

Best regards,
Carl
>
> I am looking forward to hear other peoples' opinions.
>
> Best regards,


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org


Re: rework the automated tests to not require an office build first

Posted by Arrigo Marchiori <ar...@yahoo.it.INVALID>.
Hello Carl, All,

On Sat, Jun 12, 2021 at 09:13:13AM -0400, Carl Marcum wrote:

> Hi All,
> 
> cc'd qa@
> 
> I think it would be good to rework the test framework to not require having
> just built the office.

It sounds like a very good idea to me.

> Currently, to compile and run the tests, there are dependencies on
> environment settings created and files built into main/solver/<version>.
> Mostly things like idlc, regmerge, and javamaker etc. and the UNO jar files.
> All these file dependencies are also available in either the office that
> would be under test or the SDK.
> 
> I think it would be a benefit for QA and open the use and development of
> automated tests to testers and developers that don't also have a AOO build
> environment.
> For instance I can run the test suite against Linux where I have a build env
> but not on Windows where I don't.
> 
> The one big thing about this would be it would require a tester to have the
> SDK installed in the office under test.
> I think this is a much lower bar than building the office to get them.
> 
> Does anyone have an opinion one way or the other?

IMHO I am totally for it.

Unfortunately I do not have resources (and knowledge) to help you at
the moment, but if this is not an urgent matter, we can plan it.

I am looking forward to hear other peoples' opinions.

Best regards,
-- 
Arrigo

---------------------------------------------------------------------
To unsubscribe, e-mail: qa-unsubscribe@openoffice.apache.org
For additional commands, e-mail: qa-help@openoffice.apache.org


Re: rework the automated tests to not require an office build first

Posted by Carl Marcum <ca...@gmail.com>.
Hi Pedro,

On 6/12/21 11:41 AM, Pedro Lino wrote:
> Hi Carl, all
>
>> On 06/12/2021 2:13 PM Carl Marcum <cm...@apache.org> wrote:
>> The one big thing about this would be it would require a tester to have
>> the SDK installed in the office under test.
>> I think this is a much lower bar than building the office to get them.
>>
>> Does anyone have an opinion one way or the other?
> This sounds excellent. It would probably allow more Windows users (the most used PC OS and accordingly where there are more AOO users) to test it.
>
> I volunteer to run any needed tests on Windows 7 x64.

If I'm able to follow through with it I'll let you know.

Thanks,
Carl

>
> Thanks!
>
> Cheers,
> Pedro
>
> ---------------------------------------------------------------------
> 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


Re: rework the automated tests to not require an office build first

Posted by Pedro Lino <pe...@mailbox.org.INVALID>.
Hi Carl, all

> On 06/12/2021 2:13 PM Carl Marcum <cm...@apache.org> wrote:

> The one big thing about this would be it would require a tester to have 
> the SDK installed in the office under test.
> I think this is a much lower bar than building the office to get them.
> 
> Does anyone have an opinion one way or the other?

This sounds excellent. It would probably allow more Windows users (the most used PC OS and accordingly where there are more AOO users) to test it.

I volunteer to run any needed tests on Windows 7 x64.

Thanks!

Cheers,
Pedro

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org


Re: rework the automated tests to not require an office build first

Posted by Carl Marcum <cm...@apache.org>.
Hi Keith,

On 6/20/21 9:10 PM, Keith N. McKenna wrote:
> On 2021-06-12 at 9:13, Carl Marcum <cm...@apache.org> wrote:
>> Hi All,
>>
>> cc'd qa@
>>
>> I think it would be good to rework the test framework to not require
>> having just built the office.
>>
> I believe that you are right. I know for myself, I do not have the capacity to
> be able to build on Windows and cannot run the automated tests.
>
>> Currently, to compile and run the tests, there are dependencies on
>> environment settings created and files built into main/solver/<version>.
>> Mostly things like idlc, regmerge, and javamaker etc. and the UNO jar files.
>> All these file dependencies are also available in either the office that
>> would be under test or the SDK.
>>
>> I think it would be a benefit for QA and open the use and development of
>> automated tests to testers and developers that don't also have a AOO
>> build environment.
> It would definitely be a help to QA. If a volunteer does not have the capacity
> to build, the most they can do is to confirm that a particular bug exists with
> their OS, and then verify that a build with a specific patch fixed the
> problem. With the ability to run the automated tests, individual volunteers
> could contribute more than just confirming and verifying particular bugs.
>
>> For instance I can run the test suite against Linux where I have a build
>> env but not on Windows where I don't.
>>
>> The one big thing about this would be it would require a tester to have
>> the SDK installed in the office under test.
>> I think this is a much lower bar than building the office to get them.
>>
>> Does anyone have an opinion one way or the other?
>>
> I believe that it would be a very good idea
>
> Regards
> Keith

I'm glad you agree.

I've made good progress on this and I can run the Build Verification 
tests on Windows 10 without building the office now.
It seems the tests themselves need some work but that's the point. I've 
been able to fix tests on Linux but not Windows.
Some tests randomly pass and fail (flaky tests). A lot can be fixed by 
adding pauses in the test code to let the UI catch up.

I'll probably submit a PR in the next few days after I've tested some more.

Best regards,
Carl




---------------------------------------------------------------------
To unsubscribe, e-mail: qa-unsubscribe@openoffice.apache.org
For additional commands, e-mail: qa-help@openoffice.apache.org


Re: rework the automated tests to not require an office build first

Posted by "Keith N. McKenna" <ke...@comcast.net>.
On 2021-06-12 at 9:13, Carl Marcum <cm...@apache.org> wrote:
>Hi All,
>
>cc'd qa@
>
>I think it would be good to rework the test framework to not require 
>having just built the office.
>

I believe that you are right. I know for myself, I do not have the capacity to
be able to build on Windows and cannot run the automated tests.

>Currently, to compile and run the tests, there are dependencies on 
>environment settings created and files built into main/solver/<version>.
>Mostly things like idlc, regmerge, and javamaker etc. and the UNO jar files.
>All these file dependencies are also available in either the office that 
>would be under test or the SDK.
>
>I think it would be a benefit for QA and open the use and development of 
>automated tests to testers and developers that don't also have a AOO 
>build environment.

It would definitely be a help to QA. If a volunteer does not have the capacity
to build, the most they can do is to confirm that a particular bug exists with
their OS, and then verify that a build with a specific patch fixed the
problem. With the ability to run the automated tests, individual volunteers
could contribute more than just confirming and verifying particular bugs.

>For instance I can run the test suite against Linux where I have a build 
>env but not on Windows where I don't.
>
>The one big thing about this would be it would require a tester to have 
>the SDK installed in the office under test.
>I think this is a much lower bar than building the office to get them.
>
>Does anyone have an opinion one way or the other?
>

I believe that it would be a very good idea 

Regards
Keith

>Thanks,
>Carl
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: qa-unsubscribe@openoffice.apache.org
>For additional commands, e-mail: qa-help@openoffice.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: qa-unsubscribe@openoffice.apache.org
For additional commands, e-mail: qa-help@openoffice.apache.org


Re: rework the automated tests to not require an office build first

Posted by Arrigo Marchiori <ar...@yahoo.it.INVALID>.
Hello Carl, All,

On Sat, Jun 12, 2021 at 09:13:13AM -0400, Carl Marcum wrote:

> Hi All,
> 
> cc'd qa@
> 
> I think it would be good to rework the test framework to not require having
> just built the office.

It sounds like a very good idea to me.

> Currently, to compile and run the tests, there are dependencies on
> environment settings created and files built into main/solver/<version>.
> Mostly things like idlc, regmerge, and javamaker etc. and the UNO jar files.
> All these file dependencies are also available in either the office that
> would be under test or the SDK.
> 
> I think it would be a benefit for QA and open the use and development of
> automated tests to testers and developers that don't also have a AOO build
> environment.
> For instance I can run the test suite against Linux where I have a build env
> but not on Windows where I don't.
> 
> The one big thing about this would be it would require a tester to have the
> SDK installed in the office under test.
> I think this is a much lower bar than building the office to get them.
> 
> Does anyone have an opinion one way or the other?

IMHO I am totally for it.

Unfortunately I do not have resources (and knowledge) to help you at
the moment, but if this is not an urgent matter, we can plan it.

I am looking forward to hear other peoples' opinions.

Best regards,
-- 
Arrigo

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org