Hello,
Having a unit tested framework would be really great. I think that would be
indeed a good reason to move code to "src" directory.
Let me summarize the changes that are being commented:
- Move code to src
- Add buildout support
- Add unit tests for the framework
What do the rest of the people think about this?
Best regards,
Javier
P.S. By the way, please take a look at the test-suite-class branch merge that I
proposed, it contains some code refactoring that I would like to be integrated
before moving the code to src.
Jason Cozens wrote:
> On Wed, 2009-04-22 at 19:45 +0200, Javier Collado wrote:
>
>> Probably some other changes are needed for a better buildout integration in
>> desktop-testing code such as moving the code under a 'src' directory (this would
>> make easier to have bin directory instead of a buildout-bin), but I would say
>> that the change could be beneficial for us.
>>
>
> I'd be interested in a change like this as I've been writing some unit
> tests using the unittest module to get a better understanding of how
> desktop-testing works. I'd normally put the tests in a test directory at
> the same level as the src directory to keep them separate, i.e.
>
> gnome-desktop-testing/
> src/
> test/
>
> I intend to create a branch from:
>
> https://code.edge.launchpad.net/~vcs-imports/gnome-desktop-testing/trunk
>
> so I can show want I've been doing. It's early stages at the moment as
> there are a few modules I'm unfamiliar with, e.g. xml.dom.minidom.
>
> Cheers,
> Jason.
>
> _______________________________________________
> http://live.gnome.org/DesktopTesting
> desktop-testing-list mailing list
> desktop-testing-list gnome org
> http://mail.gnome.org/mailman/listinfo/desktop-testing-list
Attachment:
signature.asc
Description: OpenPGP digital signature