Jump to: navigation, search

Difference between revisions of "Meetings/MuranoAgenda"

m
(Agenda)
Line 7: Line 7:
 
=== Agenda ===
 
=== Agenda ===
 
* Action Items Review
 
* Action Items Review
** katyafervent to investigate how unit testing is done in Django (and perhaps use that approach for muranodashboard unit testing); consult with drupalmonkey if needed
+
* Katya to provide an update on horizon/dashboard/selenium tests research
* Discuss proposal to impose stricter testing requirements (https://blueprints.launchpad.net/murano/+spec/improve-testing)
+
* Current state of Murano testing
* Other plans for juno-2
+
** Current status of murano-ci
** Would like to briefly discuss adding post-deploy information (https://blueprints.launchpad.net/murano/+spec/post-deployment-information); it's of interest to HP, want to gauge interest to others
+
** Current status of unit test coverage
** Current state of error handling for engine; should I file specific bugs (for instance, where I get a SyntaxError with no context) or is this still being dealt with as part of Stan's general changes
+
** What can be improved?
 
* Open discussion
 
* Open discussion
  

Revision as of 14:27, 1 July 2014

We have meetings in #openstack-meeting-alt weekly on Tuesdays at 17:00 UTC.

Next meetings

  • June 17, 2014, 17:00 UTC

Agenda

  • Action Items Review
  • Katya to provide an update on horizon/dashboard/selenium tests research
  • Current state of Murano testing
    • Current status of murano-ci
    • Current status of unit test coverage
    • What can be improved?
  • Open discussion

Checklist for the meeting organizer

  • Publish the agenda 24h in advance.
  • Ask each person responsible for an action from the previous meeting to prepare a line of the form, for each action item: . #info nickname description of the action link to the diff / mailing list thread etc. describing the implementation of the action.
  • Use http://meetbot.debian.net/Manual.html to get an automatic summary.
  • Prepare an outline for the meeting to speed things up.
  • Record decisions and commitments; review in the next meeting.

Previous meetings

http://eavesdrop.openstack.org/meetings/murano/