<meta http-equiv="content-type" content="text/html; charset=utf-8"><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 12.5px; border-collapse: collapse; ">Overall, this week went okay. It didn't speed up unfortunately, but at least it didn't slow down either (I think). Several things happened this week:<div>
<br></div><div>1. The biggest thing is that I believe I now have enough of a framework set up to begin non-trivial tests, which I began to do today, at least in the sense that I started tracing actual bugs, so far to no success.</div>
<div><br></div><div>2. We decided to put GTest on hold, and perhaps drop it altogether, mainly because it's effectiveness, given time constraints is minimal, do to how the blender kernel works). It's still in the codebase though, although it does cause some rather odd errors (as in cmake has to be run twice before a successful make will happen).</div>
<div><br></div><div>3. The starts of a hash changer has been posted, although it's not too integrated yet. I was trying earlier this week to actually build a GUI for it, which could be integrated into blender itself, but this proved futile (thusfar), do to several lacking api calls in blender's GUI api calls. Still, I think it would prove valuable to add a control panel for that sort of thing into blender itself.</div>
<div><br></div><div>4. Actual support for cdash, with a demo cdash created, type in make report to send the results of the tests to the public cdash: <a href="http://my.cdash.org/index.php?project=Leif-Blender" target="_blank" style="color: rgb(195, 57, 11); ">http://my.cdash.org/index.php?project=Leif-Blender</a> hopefully, we can set up Blender's own Cdash for this sort of thing at something like <a href="http://cdash.blender.org" target="_blank" style="color: rgb(195, 57, 11); ">cdash.blender.org</a>.</div>
<div><br></div><div>5. Removed the superfluous hashtests folder, and integrated it right into pyunit, the tests still exist in there.</div><div><br></div><div>6. Removed the binary directory's dependence on the source directory for running tests, it will now work just fine without the source directory.</div>
<div><br></div><div>7. Created a howto page, in order to help people set up and run the code: <a href="http://wiki.blender.org/index.php/User:LeifAndersen/GSoC2010/Howto" target="_blank" style="color: rgb(195, 57, 11); ">http://wiki.blender.org/index.php/User:LeifAndersen/GSoC2010/Howto</a></div>
<div><br></div><div>8. Got an account at graphical, and started uploading pre-build binaries, and linking to them from the howto page. Currently though, it's only for 64-bit linux. I'm planning on uploading 32-bit linux shortly, and hoping Andrea will upload a windows build. If anyone also is willing to make a mac build (partially to see if it works), that would be helpful.</div>
<div><br></div><div>Currently, my plans for next week consists of bug-squashing on <a href="http://projects.blender.org" target="_blank" style="color: rgb(195, 57, 11); ">projects.blender.org</a>. In particular, I intend to create pyunit based unit tests to aid in bug tracking, and while doing that, begin to make a nice little suite of regression tests, to ensure that those same bugs don't crawl back. Also, most of the tests are still in bpy.data, in intend to do a lot more with bpy.ops next week. I also hope to spare a little time for gtest, but I won't give it more than a few hours (less than a day's worth of time), in order to see if we can salvage it, or at least leave it there as part of a framework for building larger tests in the future.</div>
</span><div><br></div>~Leif Andersen<br><br>----------<br>That was easy: <a href="http://www.appbrain.com/app/net.leifandersen.mobile.android.easybutton">http://www.appbrain.com/app/net.leifandersen.mobile.android.easybutton</a><br>