Hello Scott, I have some buglettes in random notes that I wanted to eventually look
> at. I told someone else that I would organize them and post them. I > will try to do that soon. I will put the 'easyfix' keyword on them in > trac. These will be bugs that I think I will be able to guide someone > to fixing if they get stuck. I am sure that there will be several that > I misjudged and that are actually complicated bugs. But either (1) > you'll learn stuff anyway or (2) someone will let us know that a bug > is probably not an 'easyfix'. I'll try to do this within the next > week. > Thank you. If you have an idea for implementing a unit test framework, I would be > interested. I think it would be a lot of work though and that we > aren't ready for it yet. > On the contrary. From my experiance it is cheap and simple to get started with unit testing. You don't need to write all the tests at once. All you need to do is two steps: 1.) decide the testing framework i.e. googletest<http://code.google.com/p/googletest/>. 2.) decide the directory layout The directory layout is typically the layout of the sources. Similiar to this: project/src/my/superfeature/superclass.cpp project/tests/unit/my/superfetures/superclassTest.cpp Now everybody can create test classes. With every bugfix a new test is added. Regards Elmar -- Elmar Hinz Freiherr-vom-Stein-Str. 1 33014 Bad Driburg TYPO3 community contact: [email protected] personal contact: [email protected]
