On 19/09/12 17:09, George Kiagiadakis wrote: > And imho, we should gradually turn most of these tasks to automatic > unit tests. It is not that hard and will save us a lot of trouble. > > And here comes into play telepathy-parrot, the echo bot - unit testing > framework that I am writing, which I started writing exactly for this > purpose ;) tp-parrot is meant to automate the process of starting > temporary telepathy sessions & optionally a temporary prosody > instance, setting up accounts, running clients and setting up certain > environment conditions for those clients (ex, starting channels). This > can be useful for manual testing of handlers (call ui, text ui), but > it can also become useful for automatic testing of several components. > What needs to be done, however, is to turn components into (static) > libraries so that they can be accessed from QtTest-based unit tests. > QtTest can do wonders with UIs, it can simulate mouse clicks, key > presses, etc, but it needs access to the widget pointers where the > events should go. Ok, this may not be able to test everything, but > still many things can be tested that way. In the particular case of > ktp-send-file, for example, I believe it should be possible to > automate it fully.
That would be _really_ cool (d_ed: _underlined_, not /italics/). ktp-send-file, looks like a good component to start with, since it is very small, and doesn't have many functions to test, we could all learn a lot from it ;) Daniele _______________________________________________ KDE-Telepathy mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-telepathy
