[16:52] <SidPayton> QUESTION: hello, balloons is there a way I can help you guys in some easy to learn ways? Maybe just adding a few lines in a new test (not writing a complete one myself). Would love to learn this in baby steps.
[16:54] <balloons> SidPayton, certainly
[16:54] <balloons> let's see if I can find a simple bug for you to tackle
[16:56] <balloons> SidPayton, I'm just looking through https://bugs.launchpad.net/ubuntu-phone-coreapps/+bugs?field.tag=needs-autopilot-test
[16:57] <SidPayton> please make it simple as possible :D
[16:59] <balloons> SidPayton, hmm
[17:02] <SidPayton> I do understand if you don't have time for such a beginner.  I just would love to learn how to use autopilot and contribute back
[17:03] <balloons> SidPayton, of course we do! I'm just hesitant to put you on reminders as it requires you to compile the app and some other things.  There's plenty of options, I'm just reading bugs to find the right one :-)
[17:04] <balloons> SidPayton, I'm thinking this might be a good one: https://bugs.launchpad.net/dropping-letters/+bug/1317214
[17:09] <balloons> so SidPayton dropping letters is a simple qml game and should be easy to play with and add the test for
[17:11] <SidPayton> hehe. easy for you maybe
[17:11] <SidPayton> trying to figure out how to open it via qmlscene
[17:11] <balloons> SidPayton, I think it was amongst the first apps I wrote tests for as well ;-)
[17:12] <balloons> ok, so the tests are inside tests/autopilot
[17:12] <balloons> this is typical for all the core apps
[17:13] <balloons> from the root of the branch 'qmlscene dropping-letters.qml' should launch the game
[17:14] <SidPayton> it doesn't somehow
[17:14] <balloons> SidPayton, ahh, well let's troubleshoot. What happens?
[17:14] <balloons> but first, do you have the ubuntu-sdk metapackage installed? and what version of ubuntu are you on again?
[17:15] <SidPayton> I'm in the directory with droppimg-letters.png and test (Folder) inside
[17:16] <SidPayton> I'm on 14.04. And I don't have the sdk metapackage installed
[17:16] <balloons> SidPayton, ahh, well let's fix that
[17:16] <balloons> and then the app will launch :-)
[17:17] <balloons> you actually should use the sdk team ppa since you are on 14.04. That will make sure you have the updated sdk
[17:17] <SidPayton> could you give me the ppa name?
[17:17] <balloons> sudo add-apt-repository ppa:ubuntu-sdk-team/ppa
[17:17] <balloons> sudo apt-get update && sudo apt-get install ubuntu-sdk
[17:22] <SidPayton> balloons: it would be nice if https://wiki.ubuntu.com/Touch/CoreApps/Testing/ContributeAutopilotTestcase would meantion the metapackage. This is the site I followed blindly ;)
[17:26] <balloons> SidPayton, excellent point
[17:28]  * balloons updated requirements
[17:30] <SidPayton> wow you're really quick
[17:30] <SidPayton> module "QtQuick" version 2.3 is not installed
[17:30] <SidPayton> this isn't in the SDK?
[17:32] <balloons> SidPayton, do you have ubuntu-ui-toolkit-autopilot installed?
[17:32] <balloons> that might also need to be specified.. I'm curious
[17:32] <balloons> SidPayton, yes I would think so..
[17:33] <SidPayton> I've only followed the instructions
[17:33] <SidPayton> otherwise this system is clean
[17:33] <balloons> SidPayton, and you are launching by using qmlscene?
[17:34] <SidPayton> yes
[17:34] <SidPayton> but it stops because of QtQuick missing
[17:35] <balloons> SidPayton, what does sudo apt-get install ubuntu-ui-toolkit-autopilot do?
[17:35] <SidPayton> balloons: installation of ubuntu-ui-toolkit-autopilot didn't solve the issue with QtQuick missing
[17:36] <balloons> SidPayton, yes, I was curious if you had it
[17:36] <balloons> the qtquick issue relates to qt5 version
[17:36] <SidPayton> ah, now I have it
[17:36] <balloons> trusty shipped with an older version of qt, 5.0 or 5.1 I'd guess
[17:37] <SidPayton> hmm, I'm really looking foreward to the app-confinement (click) coming to the desktop
[17:41] <balloons> SidPayton, so anyways, I'm unsure of how to solve the qtquick issue. However, I believe it will run if we tell it to use the older version
[17:41] <SidPayton> how we do that?
[17:41] <balloons> ready for some fun? open the dropping-letters.qml file and change the import to be import QtQuick 2.0 from import QtQuick 2.3
[17:42] <SidPayton> okay
[17:42] <balloons> SidPayton, ohh, one thing.. Did you dist-upgrade after installing from the ppa?
[17:42] <balloons> that might be the issue
[17:42] <SidPayton> module "Ubuntu.Components" version 1.1 is not installed
[17:43] <balloons> change the components version to 1.0
[17:43] <SidPayton> also not installed
[17:45] <SidPayton> is there a way to get all of these new versions for 14.04?
[17:47] <balloons> SidPayton, that's what the ppa should have done
[17:47] <balloons> SidPayton, ohh right, the version should be 0.1 sorry
[17:48] <balloons> SidPayton, does sudo apt-get dist-upgrade show any pending upgrades?
[17:49] <SidPayton> 34 Cannot assign to non-existent property "audioRole"
[17:49] <SidPayton> yes it had 5 to update, but I did apt-get update earlier
[17:51] <balloons> what did it update? does it work now?
[17:52] <SidPayton> several packages including ui-toolkit
[17:53] <balloons> ahh, that sounds like the ticket
[17:54] <SidPayton> I'll revert the changes to the qml-file ant try it again as soon as the update is complete
[17:55] <balloons> kk.
[17:55] <balloons> bzr revert is handy to revert
[17:56] <SidPayton> thx
[17:58] <SidPayton> it's back with QtQuick 2.3
[18:00] <balloons> SidPayton, right, heh, so try asking for version 2.0. I believe it should work after that
[18:00] <balloons> (though I'm curious why 5.3 is being asked for
[18:00] <SidPayton> 34 Cannot assign to non-existent property "audioRole"
[18:01] <SidPayton> maybe I have the wrong dropping letters
[18:02] <SidPayton> hmm
[18:04] <balloons> SidPayton, I don't think so :-) So I'm running vivid, and most folks run utopic or even vivd as well who are doing this development. The reason for this is the app development platform was under heavy development through the utopic cycle
[18:04] <balloons> hence the ppa, but it's not bringing qt5.3 to trusty
[18:04] <SidPayton> so I'll be needing vivid as well?
[18:05] <SidPayton> would rather stay on lts
[18:05] <balloons> what's odd for me is why dropping letters is requiring it as it was written much earlier
[18:05] <balloons> SidPayton, ohh wait
[18:06] <balloons> so the app also has dependencies listed in it's debian/control file. I'm sure I have them, but you probably don't
[18:06] <balloons> sudo apt-get install qtdeclarative5-qtmultimedia-plugin qtdeclarative5-xmllistmodel-plugin qtdeclarative5-particles-plugin
[18:06] <balloons> my guess is you are simply missing for example the multimedia plugin
[18:07] <ahayzen> ... remember they added audio roles to media-hub
[18:07] <balloons> hai ahayzen :-)
[18:07] <ahayzen> o/
[18:08] <SidPayton> were all installed already
[18:08] <ahayzen> ..but then desktop doesn't have media-hub so how does the role get set? i assume in the qtmultimedia thing?
[18:09] <balloons> one more, but I'll guess you do have it
[18:09] <balloons> qtdeclarative5-ubuntu-ui-toolkit-plugin
[18:09] <SidPayton> yes I have it
[18:11] <balloons> running utopic would solve these issues, but I'm still quite surprised we're hitting them
[18:12] <SidPayton> maybe it's just me.
[18:13] <balloons> SidPayton, try something for me
[18:13] <balloons> bzr revert -r 65
[18:13] <balloons> then try running the game again
[18:14] <SidPayton> 36 Cannot assign to non-existent property "audioRole"
[18:14] <balloons> if it still fails, try bzr revert -r 60.
[18:14] <balloons> and finally, bzr revert -r 54
[18:15] <balloons> I'm pushing you back in time to older app versions :-)
[18:15] <SidPayton> 60 works
[18:16] <balloons> 60 was the last revision before the addition of the audio change
[18:17] <SidPayton> ah okay
[18:18] <balloons> anyways, it won't affect the tests so you can still write and push an MP for them :-)
[18:18] <SidPayton> and this hasn't landed in the ppa yet?
[18:18] <balloons> what hasn't landed in the ppa?
[18:18] <SidPayton> whatever is needed so that the audio changes work again :)
[18:20] <SidPayton> anyway, 60 is working and if you say that I can write a test for this version I'm happy to try something new
[18:21] <ahayzen> oh interest which version of the qtmultimedia plugin is in the PPA?
[18:21] <balloons> SidPayton, ahh :-) It seems backporting the full qt stack is problematic for a few reasons, so 14.04 isn't going to get desktop support. The idea from a developer prospective is you would run inside a chroot.. that kind of doesn't work well for our testing purposes
[18:24] <balloons> So to run the tests for newer core apps you will need utopic or better, or you'll be limited to running the tests on device (which is OK too, but harder for someone new I think)
[18:25] <balloons> SidPayton, but yes, hack against rev 60, should all be great
[18:26] <SidPayton> hmm, thats annoying. But maybe I this PC is powerfull enough for vivid in a virtualbox. A container (docker) version with everything ready to use would be even better ;)
[18:30] <balloons> SidPayton, yea, I'm wondering about having just an execution environment. If you have a device it more or less matters not, but it's easier when you are new to have vis available to you and to be able to iterate on the desktop
[18:32] <balloons> SidPayton, seems like nik90_ has done this via lxc container, which was my thought. He has a writeup: it seems to run the tests for newer core apps you will need utopic or better
[18:32] <balloons> bah copy paste buffers: http://nik90.com/fiddling-around-with-lxc-containers/
[18:33] <SidPayton> yea I guess it for most new guys it would be convinient to have as less requirements as possible
[18:34] <SidPayton> wow, haven't read this yet, thanks
[18:34] <balloons> you are welcome. Fortunately you can hack on things for now as-is. So does the bug make sense to you SidPayton ?
[18:34] <balloons> you can run the current testsuite from tests/autopilot
[18:35] <balloons> autopilot3 list dropping_letters_app
[18:35] <balloons> should list all the tests
[18:35] <balloons> autopilot3 run -v dropping_letters_app
[18:35] <balloons> should run them
[18:36] <SidPayton> give me a moment, was trying to open autopilot vis.
[18:36] <balloons> SidPayton, ahh, yes, you should explore that too :-)
[18:38] <SidPayton> okay, they all work
[18:42] <SidPayton> balloons: how do I best check it one row has reached the top?
[18:45] <SidPayton> for some reason autopilot vis won't start
[18:45] <SidPayton> autopilot: error: argument mode: invalid choice: 'vis' (choose from 'run', 'list', 'launch')
[18:51] <balloons> SidPayton, autopilot3 vis
[18:51] <balloons> autopilot is the legacy python2 version, so you should use autopilot3
[18:51] <balloons> easy mistake to make ;-)
[18:51] <balloons> there's a python2 version of vis too, but you would have to install it
[18:51] <balloons> python-autopilot-vis
[18:52] <balloons> the py2 version isn't as nice
[18:55] <balloons> SidPayton, as far as how to check one row has reached the top, I'd have to look into the source a bit myself. Each block is an object, and there should be an object that contains them
[19:00] <SidPayton> autopilot3 vis should be updated in the tutorial as well ;)
[19:00] <balloons> SidPayton, awesome, I'm on it
[19:04] <balloons> SidPayton, so looking at the qml, you can see each game tile has an objectname assigned of gametilebox
[19:05] <SidPayton> so I have vis open, but the dropdown doesn't contain anything like in the video tutorial
[19:05] <balloons> SidPayton, they are qml Rectangle types. And they are inside a column Repeater
[19:05] <balloons> SidPayton, you should see comubuntudropping-letters and unity
[19:06] <balloons> the video tutorial was with the python2 version so there will be some more goodies
[19:06] <SidPayton> balloons: yeah
[19:07] <SidPayton> balloons: vis is waiting for a dbus connection
[19:07] <balloons> SidPayton, ohh.. did you launch dropping letters via autopilot first?
[19:07] <SidPayton> hmm, via qmlscene
[19:07] <balloons> SidPayton,
[19:07] <balloons> http://paste.ubuntu.com/9543009/
[19:07] <SidPayton> did I miss that in the video?
[19:08] <balloons> mm perhaps.. heck the video is dropping letters isn't it?
[19:10] <SidPayton> it's sudoko
[19:10] <balloons> ahh, k
[19:13] <SidPayton> balloons: it's working
[19:13] <balloons> :-)
[19:14] <SidPayton> now I just need to understand how these things work :D
[19:15] <balloons> right, glad the setup piece is all done
[19:15] <SidPayton> me too
[19:34] <SidPayton> balloons: did you use vis to find out that each tile has the objectname of gametilebox?
[19:37] <balloons> SidPayton, I looked inside the qml file, dropping-letters.qml
[19:37] <balloons> SidPayton, I looked at this section: http://paste.ubuntu.com/9543278/
[19:38] <SidPayton> I think I just found the collums. but vis keeps crashing
[19:38] <balloons> ohh, that's no good. So there's another way to get dbus dump data. That's to use the print_tree command
[19:38] <balloons> SidPayton, http://unity.ubuntu.com/autopilot/api/introspection.html#autopilot.introspection.dbus.DBusIntrospectionObject.print_tree
[19:39] <balloons> so you can select an object or even the entire page or mainview and print it's tree and all children
[19:39] <balloons> that let's you effectively save a dump of the tree you can browse and search
[19:41] <balloons> SidPayton, so you can do something like this inside of test_dropping_letters.py, then run the new test_dump test. http://paste.ubuntu.com/9543337/
[19:41] <balloons> now in your case you are interested in the object data during the game, so we can tweak the test to load a new game, and then dump. make sense?
[19:43] <SidPayton> I would rather try it the official way. vis seems to work now. had to restart the whole thing. but now I don't seem to be able to find the right collums anymore
[19:45] <balloons> SidPayton, I use print_tree all the time; it's quite handy and "official".  So this is what I did: http://paste.ubuntu.com/9543375/
[19:46] <balloons> I find it handy to be able to visually see all the data in text format like that.. it's not quite the same as vis, but it may come in handy to use both
[19:51] <SidPayton> this is my dump output http://paste.ubuntu.com/9543439/
[19:54] <balloons> SidPayton, ahh, so you need to run in the directory containing the tests. For the core apps that's always tests/autopilot
[19:54] <balloons> you can check by running autopilot3 list dropping_letters_app
[19:54] <balloons> the folder called dropping_letters_app should exist as a subdirectory
[19:54] <balloons> good evening Letozaf_
[19:56] <Letozaf_> balloons, good evening to you :)
[19:56] <balloons> so you have some big MPs for docviewer ;-) it's odd jenkins didn't run on themn
[19:56] <balloons> ohh there's a pre-req
[19:56] <Letozaf_> balloons, yeah true, wounder why
[19:56] <Letozaf_> balloons, yes on one of them
[19:57] <balloons> I approved the first, that should trigger the second
[19:58] <Letozaf_> balloons, good, hope everything is ok
[19:59] <balloons> Letozaf_, on the second, where you going to add a test for it?
[19:59] <Letozaf_> balloons, yes I added a test to go to page on a pdf documente
[19:59] <Letozaf_> document
[19:59] <balloons> and it's also weird it's showing a diff for the pdf
[19:59] <balloons> do you know why?
[19:59] <balloons> Letozaf_, I don't see a test added here: https://code.launchpad.net/~carla-sella/ubuntu-docviewer-app/test-go-to-page-pdf-file/+merge/244690
[19:59] <balloons> unless I'm missing it :-)
[20:00] <Letozaf_> balloons, let me check
[20:02] <Letozaf_> balloons, if I browse the code the test is :  test_go_to_page_pdf_file in test_docviewer.py, do not know why it's not in the diff
[20:03] <balloons> Letozaf_, probably because you didn't commit and push the latest version of what you have locally..  it's a big diff though, so it might just be truncated actually
[20:03] <balloons> ahh I see it in the bracnh, it's truncated on the site
[20:04] <Letozaf_> balloons, yes because I added a pdf document with more than one page otherwise I could not test the go to page
[20:04] <balloons> yep yep, makes sense
[20:04] <Letozaf_> balloons, on a pdf with only one page
[20:04] <balloons> Letozaf_, looks cool
[20:04] <Letozaf_> balloons, :)
[20:05] <balloons> you are really really getting good at these things, haha
[20:05] <Letozaf_> balloons, thank you
[20:05]  * Letozaf_ blushes
[20:07] <balloons> SidPayton, get it running properly?
[20:10] <SidPayton> balloons: been trying to figure this out http://paste.ubuntu.com/9543544/
[20:12] <balloons> SidPayton, it's a good idea to go ahead and try and run the original test suite and make sure it works (so you know your setup works :-) )
[20:12] <balloons> so try another test first and see if it runs
[20:14] <SidPayton> they are working just fine
[20:19] <balloons> SidPayton, ok that's good
[20:25] <SidPayton> balloons: is it possible to search for objectnames in vis?
[20:27] <balloons> SidPayton, sadly no. The search just looks for objecttype names
[20:34] <SidPayton> http://paste.ubuntu.com/9543667/ so as I understand it the number of letters in one row is saved in model: letters for each row in the repeater. How do I access that information?
[20:37] <balloons> SidPayton, the way autopilot works, it has access via dbus introspection, to all the objects created and there properties
[20:37] <balloons> to 'find' an object during runtime, we issue selects
[20:37] <balloons> that's the select_single calls you see
[20:38] <balloons> select_many('QQuickRectangle') would return all the QQuickRectangle objects the app has
[20:43] <SidPayton> balloons: okay, I will remember this and try to continue at this point next time. Have nice holidays and thank you very much for your help. see you soon
[20:47] <balloons> SidPayton, same to you. Thanks so much for going through everything, helped me clean it up a little :-)