Hey Lionel, So you basically have two options. We already have a test concept where we open a file and execute a basic macro in it. You can find an example for it in sc/qa/extras/macros-test.cxx
The other more flexible option is that you open a document and call the uno calls yourself from c++. The advantage of the second option is that it allows to add additional assertions and easier debugging but it takes a bit more code. Regards, Markus On Aug 2, 2013 5:59 PM, "Lionel Elie Mamane" <lio...@mamane.lu> wrote: > I'd appreciate some help in writing a unittest (subsequenttest?) for > https://bugs.freedesktop.org/67685 > > It is the second time such a bug crops up, I'd like to prevent it. > > Basically, we "just" need to open an .odb file, run a Basic macro (we > can set it to autorun on document load), then save the file, and > inspect the result. > > Thanks in advance! > > -- > Lionel > _______________________________________________ > LibreOffice mailing list > LibreOffice@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/libreoffice >
_______________________________________________ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
