== Meeting information == * #ubuntu-touch-meeting: Ubuntu Touch App Sudoku meeting, 03 Jul at 16:33 — 16:59 UTC * Full logs at [[http://ubottu.com/meetingology/logs/ubuntu-touch-meeting/2013/ubuntu-touch-meeting.2013-07-03-16.33.log.html]] == Meeting summary == == Vote results == == Action items == * (none) == People present (lines said) == * popey (35) * fredoust (27) * balloons (17) * meetingology (3) == Full Log == 16:33 #startmeeting Ubuntu Touch App Sudoku meeting 16:33 Meeting started Wed Jul 3 16:33:38 2013 UTC. The chair is popey. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 16:33 16:33 Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired 16:34 dinko isn't here 16:34 blueprint: https://blueprints.launchpad.net/ubuntu-phone-commons/+spec/sudokotouch-coreapps-development 16:35 bugs: https://bugs.launchpad.net/stock-ticker-mobile-app 16:35 oops 16:35 bugs: https://bugs.launchpad.net/sudoku-app 16:35 ☻ 16:35 better :p 16:35 reviews: https://code.launchpad.net/sudoku-app/+activereviews 16:36 burndown: http://status.ubuntu.com/coreapps-13.10/ 16:36 hows it going fredoust ? 16:36 I was fixing some bugs 16:37 yeah, i saw. 16:37 great ☻ 16:37 I enjoyed playing the game on the train, and it was a very useful exercise to focus on the app 16:37 also, fun 16:37 cool 16:37 any of the bugs not make sense? 16:38 I doesn't have device so I didn't play a real party 16:38 no all of them are almost fixed I think 16:39 Great! 16:39 sorry for my bad merging 16:39 do I have to create a branch for all bugs ? 16:40 even if it is a little bug ? 16:40 yes. ☻ 16:40 There's a good reason for this. 16:40 We have autolanding / CI setup 16:40 ok 16:40 so as you propose it gets tested before it actually lands 16:41 so even if it's a small bug fix, it could potentially break something, and our tests (cue balloons) should discover that 16:41 ok I just fixed the bug 1196468 "Incorrect buttons don't fix themselves" so I hope I will do a perfect merge 16:41 ok I understand 16:42 indeed.. autopilot tests are now part of autolanding.. But we need to get some written for this app :-) 16:42 You may have seen me announcing several workshops towards this.. I also highlighted sudoku as a core app ready for testing 16:42 yes I read the discussion between dinko and you last time but I don't understand everything I thought Dinko wrote them 16:43 Dinko was going to look at them; we 16:43 we'll keep pushing towards adding more tests to help ensure we don't have regressions and the bugs you've fixed stay fixed :-) 16:44 ok 16:45 can I see an example of autopilot test ? 16:45 sure.. would you like to run one? 16:45 yes it would be great 16:49 * popey wonders if balloons is looking for one? 16:49 yes, lol, sorry 16:50 fredoust, bzr branch lp:~ubuntu-clock-app 16:50 since I highlighted clock today, let's have you just run one of those ;-) 16:50 cd ubuntu-clock-app/tests/autopilot 16:51 now a 2 min tutorial for autopilot, though I happily recommend coming out to the workshop if your curious: http://www.theorangenotebook.com/2013/07/automated-testing-workshops.html 16:51 autopilot list ubuntu_clock_app lists the tests 16:51 I see 2 at the moment 16:52 next, autopilot run ubuntu_clock_app will run them 16:52 you'll see the app is launched once for each test, the test is run, then you should get feedback on pass or fail :-) 16:52 ls 16:52 oups 16:53 fredoust, if your curious how they are put together and work have a look at http://developer.ubuntu.com/resources/cookbook/mobile/how-to-write-autopilot-tests/ 16:53 that's enough derailing for now I think :-) 16:53 yes I will read this 16:53 ping me anytime with questions.. like anything there's a learning curve, but you'll get it! 16:53 Thanks balloons 16:54 ok thanks 16:54 Another piece of information for you before we wrap up 16:54 I see test_clock.py and test_stopwatch.py 16:55 Over the next few days we are going to start pushing people to be testing these apps more on a regular basis as part of their daily routine. 16:55 "dogfooding" 16:55 as part of that we will likely be filing a bunch of bugs over the next two weeks. I just wanted you to have a pre-warning 16:55 because you're likely to get a bunch of bugs and you may wonder where they're all coming from ☻ 16:56 lol ok 16:56 We will also be adding some work items to the blueprint. 16:56 These will be ones which are higher priority to ensure the app is robust, well tested, reliable.. 16:57 We're keen for people to feel like the app is something they can trust. 16:57 ok 16:57 of course 16:57 Ok, we're almost out of time. Did you have any questions / issues? 16:58 no it's ok for me 16:58 ok. great! Thanks for taking care of the bug reports 16:58 and if you get stuck with autopilot, balloons is your man! 16:58 ok perfect 16:58 thanks both of you 16:58 thanks ! 16:59 #endmeeting Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)