ParaQ:Telecon 09/13/2005 1PM EST: Difference between revisions
From ParaQ Wiki
Jump to navigationJump to search
(→Agenda) |
|||
| Line 38: | Line 38: | ||
| 7 | | 7 | ||
| BW | | BW | ||
| Send list of people needing cvs access to Kitware. | | Send list of people needing cvs access to Kitware. Those with valid Qt developer licenses</td> | ||
|- | |- | ||
|} | |} | ||
Revision as of 16:08, 7 September 2005
Agenda
| Item | People | Description |
|---|---|---|
| 1 | KM | Multiview update |
| 2 | CM | Report on testing solution for Qt. See #Qt Testing Requirements |
| 3 | CM | Present straw man class architecture for ParaView Server API |
| 4 | BW,DR | Present demo script |
| 5 | DR | Present Microsoft Project schedule overview |
| 6 | BW | Update on videocon equipment |
| 7 | BW | Send list of people needing cvs access to Kitware. Those with valid Qt developer licenses |
Pre-Meeting Information
Qt Testing Requirements
- Test for code coverage.
- Test GUI's interaction with server manager.
- Test GUI itself (e.g. button click leads to correct action & results) that's insensitive to layout.
- Easy to create test cases.
- Community's ability to test and contribute to testing.
- 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.
