[smc-discuss] Automated rendering testing - Weekly status update, GSoC '13

[Nandaja Varma]

Hello,

Firstly, I have added a README in the repo that, hopefully, describes how
the framework works as of now (Thanks for the remark, Vasudev).

I have changed the framework interface from its previous form, although the
previous front end automated_rendering_testing.py is still present in the
repo. Now the new interface, rendering_testing.py, need all the file names
to be provided as command line arguments. The user gets the convenience  of
using the tab completion this way. The user will have to give as command
line arguments 6 files (font  file, test cases file, reference file,
rendering output and files to store output) and an optional directory
name(if the engine is harfbuzz).
 If the rendering engine is harfbuzz, user can run the script
generate_hb_rendering.py  along with the test cases file and font file as
parameters, to create the rendered output file. If that is not the case,
the user will have to create this file as well in the prescribed form.
Now, the algorithm that actually test the rendering was a bit buggy and was
giving certain wrong outputs for words with multiple rendering engines and
I have cleared this error. This feature gives correct output now for the
files I tried it with.
The next thing I am working on is the web interface and I am using Flask
framework. Will make this code public as soon as I get the script running
from the page.
Find the code here:
https://gitlab.com/gem/automated-rendering-testing/tree/master
-- 
Regards,
Nandaja Varma
http://nandajavarma.wordpress.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.smc.org.in/pipermail/discuss-smc.org.in/attachments/20130817/228c415c/attachment-0001.htm>