On Sat, Apr 27, 2013 at 6:06 AM, Elmar Hinz <[email protected]> wrote: > Hello, > > I practiced to complie the code with cmake. > > I set up my own LyX-mirror on github: https://github.com/t3elmar/Lyx
By mirror do you mean that it will be updated automatically? > Now I would like to fix some bugs. > > I am experienced with OOP and design patterns. I am not experienced with > C++. > Hence it should be some rather easy bugs just to get started. 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. > By the way, I is there an infrastucture for unit tests? Not really. There is structure for other kinds of tests though. There are export tests and autotests. Export tests test that a certain .lyx file can be exported in several formats (pdf via latex, pdf via pdflatex, pdf via luatex, and lyxhtml) with a zero error code return. Autotests try to simulate a user session. I think you need X installed. They open LyX and execute commands just like a user would. Since you are using CMake, maybe you can run the tests, although I don't know of anyone on a Mac who has done so. To try, run <<ctest>>. If the autotests fail, try to run only the export tests with <<ctest -R "export">>. 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. Scott
