Personal tools
  • We're Hiring!

You are here: Home Community Minutes Conference Calls 2013 2013-09-17 Tuesday Team Meeting

2013-09-17 Tuesday Team Meeting

Dundee: Remote:

17th September 2013 Dundee: Petr, Mark, Will, Simon, Jean-Marie, Helen, Andrew, Ola Remote: Josh, Seb, Chris, Carlos, Colin, Douglas, Wilma, Mark H, Ian, Curtis, Blazej, Seb Simard

Agenda - 2:30pm Start

  1. Accepting minutes from last meeting Accepted

  2. Testing report - Blazej -

    • Not much to say - Python integration test running
    • Next - rebase OmeroJava onto develop - big job, but getting there
    • Colin - also looking to rebase Python tests, first PR today hopefully.
    • Carlos - not working on this just now, but can help if needed
    • Ian - Use robot framework for matlab UI?
  3. 4.4.9 report - Mark - 14:37 UK

    • In the OMERO-4.4.9 milestone there are 47 open tickets and 70 closed tickets.
    • Over the past week,
      • the milestone grew by 9 tickets total
      • still, the open ticket count dropped by 10.
    • An early October 4.4.9 release probably requires the milestone having fewer tickets.
    • The priorities of the open tickets, largely bugs, are,
      • 7 blockers
      • 30 critical
      • 6 major
      • 4 minor.
    • All the open tickets are assigned.
    • Those owning the most open tickets are,
      • Helen owns 4 critical, 1 major
      • Ola owns 2 blockers, 3 critical, 1 major (can ignore 3 QA tickets for 4.4.9 release)
      • Jean-Marie owns 2 blockers, 4 critical, 1 major
      • Josh owns 1 blocker, 10 critical, 1 major, 1 minor.
    • Need new ticket - network checker (Kenny, for JM)
    • Josh - need to Skye re: thumbnail permissions etc.
    • Other ticket owners are Blazej, Colin, Gus, Kenny, Mark, Melissa, Roger, Sebastien, Simon, Will.
    • Ideas,
      • perhaps a few of Josh's critical tickets can go to others
        • or out of 4.4.9
        • perhaps to Blazej, Colin, Mark, but not to Jean-Marie
        • many relate to permissions, graph traversal
      • perhaps Will can take a couple of Ola's tickets.
    • Josh - need tests to assess impact. Discuss impact on clients / UI
      • next look at Delete, may be able to push.
      • Blazej - add tests where you think best.
  4. Infrastructure - Sebastien - 14:47 UK

    • Jenkins builds/servers:
      • Couple of failing builds - under control
      • Experimental view to exclude builds under construction - rationalize
      • Need to rationalize labels/names across nodes/jobs
      • Upcoming: restructuration of daily builds deployment on howe/gretzky
    • SAB infrastucture:
      • omero4-demo server used yesterday for SAB rehearsals - went fine
      • Status of Gianluigi's VM - possibility of reusing post SAB?
    • Need backup of server
    • Code management tools
      • work on SCC unrebased-prs completed- use comments in GH to manage PRs porting between development lines
    • Documentation in progress - Just ask if anything unclear. http://www.openmicroscopy.org/site/support/omero4-staging/developers/scc-scripts.html#scc-unrebased-prs
  5. http://hudson.openmicroscopy.org.uk/view/Mgmt/job/SCC-unrebased-prs/

    • Mock release (https://trac.openmicroscopy.org.uk/ome/ticket/11354)
      • mostly on-hold now (SAB work)
      • on-going work on Maven deployment using our artifactory
      • installation of OMERO dependencies on the release CI node
  6. Glencoe Update - Chris - 14:55 UK

    • No news
  7. Presentation: Introduction to Robot Framework PDF

    • robotframework.org
    • Looked at various testing tools - Robot was best
    • Keyword-driven - Nicer syntax for non-devs (and devs!)
    • 3 parts:
      • Core framework
      • Domain-specific libraries - E.g. Swing, Selenium
      • Extended with your own libraries
    • Installation stack:
      • Jython-based for Swing support (Insight)
      • Python & Selenium2 for web.
    • New tests location: components/tests/ui/
    • /library - Additional Keywords using existing keywords
      • /resources - new Keywords coded in Java / Python
      • /testcases - The tests themselves, using keywords from above
    • Can run locally using pybot / jybot
    • Integration in the main build system
    • Keywords are just functions, with cleaner syntax
    • SublimeText 2 / emacs can give sytax highlighting
    • Using non-tabular format, but aligning columns to improve readability
    • Often rely on UI component ‘name’. Requires coding changes in Insight
    • Next Steps:
    • Daily build for web
    • Publish build outputs and logs
    • Define set-up and keywords to lookup users etc
    • Improve test coverage
    • Use Tags to include, exclude, organise etc
    • Investigate integration with saucelabs.com - host tests, run on Windows etc.
  8. Any other business (<5 mins)

    • Will we cancel meeting next week due to SAB meeting? YES!
Document Actions