[19:00] <balloons> elopio, remember this old branch? https://code.launchpad.net/~dpm/ubuntu-filemanager-app/run-ap-from-out-of-source-build/+merge/217510 We've hit the problem again about the best way to run tests inside the build environment as a developer.
[19:01] <balloons> I think I'm coming around to the mp's way of doing it..
[19:03] <elopio> balloons: I'm not sure what you mean, that's an english phrase I don't fully understand.
[19:03] <elopio> do you mean you like the idea of searching for the build dir, or that you like the idea of passing it as a parameter ?
[19:03] <balloons> elopio, hehe.. sorry about that. I'm trying to say, I think what david originally suggested, using the cmakepluginparser, is the way to go
[19:05] <elopio> I still don't agree. I think that while developing things we should always call the cmake autopilot task to run the tests.
[19:05] <elopio> but we always can do both.
[19:06] <elopio> if there's a BUILD_DIR environment variable, use it.
[19:06] <elopio> if there is not, then we can try to find it or run the installed one. Of that part I'm not really worried atm.
[19:06] <elopio> balloons: out of curiosity, what are the problems you are facing now?
[19:08] <balloons> elopio, well I'm running into the old hardcoded local source path issue.. It's a bit of the setup code we've copied about everywhere, but never really standardized beyond, you should build in tree and layout your project this way
[19:08] <balloons> folks are using make and building out of tree.. it fails in this case
[19:10] <balloons> elopio, is there a project that uses cmake autopilot successfully atm?
[19:10] <elopio> balloons: I've started following dobey's advice about CMake passing the build path on unity-click-scope
[19:11] <elopio> I like the way it works. But we still need some more fancy things, like being able to select which tests to run.
[19:11] <balloons> my concern with shoving it into cmake now is cmake build configs are reserved for mad scientists :-)
[19:12] <balloons> lol.. but seriously, I'll go check out what you did
[19:13] <elopio> balloons: it's really simple in this case, a lot more than querying the file.
[19:13] <elopio> http://bazaar.launchpad.net/~ubuntuone-control-tower/unity-scope-click/trunk/view/head:/autopilot/CMakeLists.txt#L16
[19:14] <elopio> BUILD_DIR=${CMAKE_BINARY_DIR}
[19:15] <elopio> then the logic on the launch method is also simplified
[19:15] <elopio> http://bazaar.launchpad.net/~ubuntuone-control-tower/unity-scope-click/trunk/view/head:/autopilot/unityclickscope/test_click_scope.py#L135
[19:15] <elopio> if BUILD_DIR exists, use the binaries from that dir.
[19:15] <elopio> if it doesn't, just call the installed ones.
[19:16] <elopio> well, I think it's simpler than dpm's solution. But that might be because I like it best and not being impartial.
[19:23]  * balloons looks
[19:24] <balloons> elopio, hmm.. \
[19:25] <balloons> I do like setting / reading a builddir env var
[19:25] <balloons> ok, I'll try this
[19:27] <elopio> balloons: I would prefer to pass arguments to autopilot instead of env vars, but this works for now for me.
[19:28] <elopio> what I would like to do is to standardize the way we launch apps. But it's a little hard if we are not able to stabilize the tests.
[19:28] <elopio> now that dialer app is going to be python3, that's going to be my sample app.
[19:37] <elopio> balloons: would you help me to set up autopkgtests for dialer-app?
[20:21] <balloons> elopio, yes should be REALLY simple to do so
[20:21] <balloons> yes, we mentioned in david's original mp my preference for passing an arg to autopilot, but I digress