Comment 6 for bug 368157

Jason, I agree with you, "testing" in "testing_framework" is redundant, just "desktoptesting.framework" makes sense.

let's talk about the "testsuites" again. I'm new to this project, so maybe my understanding is not correct or I'm missing some ideas: There are two possible places for such testsuites, one somewhere in the ubuntu-desktop-testing project and one in "~/.ubuntu-desktop-test". This places are searched for testcases and matching testcases are loaded, and run. So for me there are basically two types of testcases: "core-testcases" (placed in u-d-t) and "non-core-testcases" (placed in $HOME)
The question which comes in my mind here is: why not making the "core-testcases" a project for its own, this would have several advantages, like you can give testcase contributors commit access only to "core-testcases" and not to the framework itself, or if a user only wants to test an application which has not testcase in "core-testcases" he/she can install the framework without the testcases and places the related testcases in $HOME

I somehow have the feeling that the testcases itself do not fit into the desktoptesting package.

But I might be completely wrong and missed some important points,
Markus