16:33 <popey> #startmeeting Ubuntu Touch App Sudoku meeting
16:33 <meetingology> 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 <meetingology> 
16:33 <meetingology> 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 <fredoust> dinko isn't here
16:34 <popey> blueprint: https://blueprints.launchpad.net/ubuntu-phone-commons/+spec/sudokotouch-coreapps-development
16:35 <popey> bugs: https://bugs.launchpad.net/stock-ticker-mobile-app
16:35 <popey> oops
16:35 <popey> bugs: https://bugs.launchpad.net/sudoku-app
16:35 <popey>16:35 <fredoust> better :p
16:35 <popey> reviews: https://code.launchpad.net/sudoku-app/+activereviews
16:36 <popey> burndown: http://status.ubuntu.com/coreapps-13.10/
16:36 <popey> hows it going fredoust ?
16:36 <fredoust> I was fixing some bugs
16:37 <popey> yeah, i saw.
16:37 <popey> great ☻
16:37 <popey> I enjoyed playing the game on the train, and it was a very useful exercise to focus on the app
16:37 <popey> also, fun
16:37 <fredoust> cool
16:37 <popey> any of the bugs not make sense?
16:38 <fredoust> I doesn't have device so I didn't play a real party
16:38 <fredoust> no all of them are almost fixed I think
16:39 <popey> Great!
16:39 <fredoust> sorry for my bad merging
16:39 <fredoust> do I have to create a branch for all bugs ?
16:40 <fredoust> even if it is a little bug ?
16:40 <popey> yes. ☻
16:40 <popey> There's a good reason for this.
16:40 <popey> We have autolanding / CI setup
16:40 <fredoust> ok
16:40 <popey> so as you propose it gets tested before it actually lands
16:41 <popey> so even if it's a small bug fix, it could potentially break something, and our tests (cue balloons) should discover that
16:41 <fredoust> ok I just fixed the bug 1196468 "Incorrect buttons don't fix themselves" so I hope I will do a perfect merge
16:41 <fredoust> ok I understand
16:42 <balloons> indeed.. autopilot tests are now part of autolanding.. But we need to get some written for this app :-)
16:42 <balloons> You may have seen me announcing several workshops towards this.. I also highlighted sudoku as a core app ready for testing
16:42 <fredoust> yes I read the discussion between dinko and you last time but I don't understand everything I thought Dinko wrote them
16:43 <balloons> Dinko was going to look at them; we
16:43 <balloons> 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 <fredoust> ok
16:45 <fredoust> can I see an example of autopilot test ?
16:45 <balloons> sure.. would you like to run one?
16:45 <fredoust> yes it would be great
16:49 * popey wonders if balloons is looking for one?
16:49 <balloons> yes, lol, sorry
16:50 <balloons> fredoust, bzr branch lp:~ubuntu-clock-app
16:50 <balloons> since I highlighted clock today, let's have you just run one of those ;-)
16:50 <balloons> cd ubuntu-clock-app/tests/autopilot
16:51 <balloons> 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 <balloons> autopilot list ubuntu_clock_app lists the tests
16:51 <balloons> I see 2 at the moment
16:52 <balloons> next, autopilot run ubuntu_clock_app will run them
16:52 <balloons> 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 <fredoust> ls
16:52 <fredoust> oups
16:53 <balloons> 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 <balloons> that's enough derailing for now I think :-)
16:53 <fredoust> yes I will read this
16:53 <balloons> ping me anytime with questions.. like anything there's a learning curve, but you'll get it!
16:53 <popey> Thanks balloons
16:54 <fredoust> ok thanks
16:54 <popey> Another piece of information for you before we wrap up
16:54 <fredoust> I see test_clock.py and test_stopwatch.py
16:55 <popey> 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 <popey> "dogfooding"
16:55 <popey> 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 <popey> because you're likely to get a bunch of bugs and you may wonder where they're all coming from ☻
16:56 <fredoust> lol ok
16:56 <popey> We will also be adding some work items to the blueprint.
16:56 <popey> These will be ones which are higher priority to ensure the app is robust, well tested, reliable..
16:57 <popey> We're keen for people to feel like the app is something they can trust.
16:57 <fredoust> ok
16:57 <fredoust> of course
16:57 <popey> Ok, we're almost out of time. Did you have any questions / issues?
16:58 <fredoust> no it's ok for me
16:58 <popey> ok. great! Thanks for taking care of the bug reports
16:58 <popey> and if you get stuck with autopilot, balloons is your man!
16:58 <fredoust> ok perfect
16:58 <fredoust> thanks both of you
16:58 <popey> thanks !
16:59 <popey> #endmeeting