ParaQ:Telecon 09/13/2005 1PM EST: Difference between revisions

From ParaQ Wiki
Jump to navigationJump to search
Line 5: Line 5:
   <td>Multiview update.</td>
   <td>Multiview update.</td>
</tr>
</tr>
*[CM] Report on testing solution for Qt.
<tr>[CM] Report on testing solution for Qt.
</tr>
<tr>
  <td>&nbsp</td>
  <td>
**Requirements (from Clinton Stimpson email ...)
**Requirements (from Clinton Stimpson email ...)
*# Test for code coverage.
*# Test for code coverage.
Line 14: Line 18:
*# Integration with vtk's and paraview's testing framework (meaning leverage testing abilities already existent such as image comparisons and such)
*# Integration with vtk's and paraview's testing framework (meaning leverage testing abilities already existent such as image comparisons and such)
*# Drive demos, using the same framework.
*# Drive demos, using the same framework.
 
  </td>
</tr>
<tr>
*[CM] Present straw man class architecture for ParaView Server API
*[CM] Present straw man class architecture for ParaView Server API
</tr>
<tr>
*[BW/DR] Present demo script.
*[BW/DR] Present demo script.
</tr>
<tr>
*[DR] Present Microsoft Project schedule overview
*[DR] Present Microsoft Project schedule overview
</tr>
<tr>
*[BW] Update on videocon equipment.
*[BW] Update on videocon equipment.
</tr>
<tr>
*[BW] Send list of people needing cvs access to Kitware.  This will include only people with valid Qt developer licenses.
*[BW] Send list of people needing cvs access to Kitware.  This will include only people with valid Qt developer licenses.
</tr>
</table>
</table>

Revision as of 15:26, 7 September 2005

Agenda

[CM] Report on testing solution for Qt.
  • [CM] Present straw man class architecture for ParaView Server API
  • [BW/DR] Present demo script.
  • [DR] Present Microsoft Project schedule overview
  • [BW] Update on videocon equipment.
  • [BW] Send list of people needing cvs access to Kitware. This will include only people with valid Qt developer licenses.
[KM] Multiview update.
&nbsp
    • Requirements (from Clinton Stimpson email ...)
    1. Test for code coverage.
    2. Test GUI's interaction with server manager.
    3. Test GUI itself (e.g. button click leads to correct action & results) that's insensitive to layout.
    4. Easy to create test cases.
    5. Community's ability to test and contribute to testing.
    6. Integration with vtk's and paraview's testing framework (meaning leverage testing abilities already existent such as image comparisons and such)
    7. Drive demos, using the same framework.
Retrieved from "http://www.paraview.org/ParaView/index.php?title=ParaQ:Telecon_09/13/2005_1PM_EST&oldid=48"