[Libreoffice] Running smoketest module standalone.

[Yifan Jiang]

Hi Caoln,

Thanks for the ideas! The preferred goal is for option b, to make it able to
run automatically without manual intervention. As an ideal result, we can have
machines persistently check out the latest build and give back the testing
results automatically.

One question is I saw the smoketest.cxx seems handling the Macro security
releasing on run time (Not sure my understanding is right), so is there
specific reasons to extract the logic out (making another piece of code)? It
could be the best if I can have things reusable at the current code base, so
that we do not need to maintain 2 different code set for similar testing (I
think some developers are also happy to use 'make check'). What is your
concern about this aspect? Thanks a lot :)

Best wishes,
Yifan

On Tue, Jul 12, 2011 at 11:57:06AM +0100, Caolán McNamara wrote:
> On Tue, 2011-07-12 at 18:51 +0800, Yifan Jiang wrote:
> > Hello all,
> > 
> > I was working on extracting smoketestoo_native module out of the build system,
> > to investigate the possibility running it with Libreoffice binary build. So
> > that we could allow QA to run this quick test for a basic level of smoke
> > testing with a released or pre-released build.
> 
> You could try...
> a) just grabbing the smoketest.sxw itself out of a build and manually
> open it and click "run" after turning off macro protection. You don't
> need any infrastructure to do that
> b) extract out the logic that sets up a temp user dir with macro
> protection already turned off in the settings and hack around passing
> that to your installed set so that you can leave out clicking the "turn
> off macro protection" step and dig out the command line invocation to
> open and automatically run the macro in the smoketest.sxw without manual
> intervention.
> 
> a is super fast to do.
> 
> C.
>