Ideally, our application would be an abstract state machine with well defined interfaces, and our GUI would just poke those interfaces and display the state of the machine. Then we could simulate most of the program with a test suite that would act like a user using a GUI. These days, as Jason can tell you, most of Do's code /is/ GUI code. Still, keep this state machine metaphor in mind when designing testable code.
David On Tue, Jun 23, 2009 at 5:26 PM, Nicolas Chachereau < [email protected]> wrote: > > Alex Launi wrote: > > At this I propose we require tests with new commits. > > What are existent testing solutions in Mono/C# ? > > Jason Smith wrote: > > Its a great idea but testing GTK interfaces is going to be very > > difficult. Simulating user input programaticly is difficult. > > Having at least some unit tests for parts of the code not directly > related to the UI would still make sense. You don't need to simulate > user input as long as you're not doing functional testing. > > Just my two cents... (Disclaimer: I'm not even (yet?) contributing to Do) > > Regards, > Nicolas > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "GNOME Do" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/gnome-do?hl=en -~----------~----~----~----~------~----~------~--~---
