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

From ParaQ Wiki
Jump to navigationJump to search
No edit summary
 
(45 intermediate revisions by 3 users not shown)
Line 1: Line 1:
==Agenda==
==Agenda==
<table cellspacing=2 bgcolor="#d0d0d0">
{| cellpadding="2" cellspacing="4" style="backround:#efefef"
<tr>
|-
  <td>KM</td>
! style="background:#abcdef" | Item
  <td>Multiview update.</td>
! style="background:#abcdef" | People
</tr>
! style="background:#abcdef" | Description
<tr>
|-
  <td>CM</td>
|-
  <td>Report on testing solution for Qt.</td>
| 1
</tr>
| KMor
<tr>
| Multiview update
  <td>&#160</td>
|-
  <td>
|-
Requirements (from Clinton Stimpson email ...)
| 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.  See [[Demo:Script]]
|-
|-
| 5
| DR
| Present Microsoft Project schedule overview</td>
|-
| 6
| BW
| Update on videocon equipment
|-
|}
 
==Qt Testing Requirements==
# Test for code coverage.
# Test for code coverage.
# Test GUI's interaction with server manager.
# Test GUI's interaction with server manager.
Line 20: Line 45:
# 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>
Possible Solutions:
<tr>
 
  <td>CM</td>
# Squish from Frog Logic
  <td>Present straw man class architecture for ParaView Server API</td>
## $3,000 per seat for license for complete application
</tr>
## $400 for license to just run tests
<tr>
## Community contribution limited because of license cost
  <td>BW,DR</td>
## Possible Difficulty integrating with VTK and Paraview testing framework
  <td>Present demo script</td>
## Application to be tested started as child process and so dynamic analysis will be difficult
</tr>
# KD Executor
<tr>
## Similar in cost and limitation to Squish
  <td>DR</td>
# KUnitTest
  <td>Present Microsoft Project schedule overview</td>
## BSD license
</tr>
## Tests must be written in C++
<tr>
## Designed for unit testing not complete application testing
  <td>BW</td>
# QTestLib
  <td>Update on videocon equipment</td>
## Dual license
</tr>
## Tests must be written in C++
<tr>
## Designed for unit testing not complete application testing
  <td>BW</td>
# QTester
  <td>Send list of people needing cvs access to Kitware.  This will include only people with valid Qt developer licenses</td>
## Written by LLNL
</tr>
## Not finished
</table>
## Not open source yet
# Python Scripting
## PyQt licensing cost.
## Limitation in PyQt in that the leaf class of C++ constructed object can't be accessed.
## Must maintain own C++ wrapped classes and utilities
 
Recommendation:
 
Begin by linking ParaQ lib with testing main built using components of KUnitTest and/or QTestLib. This would allow us to meet our initial testing goals. Then develop more complete testing framework as project progress.
 
==Decisions==
* Clinton Stimpson (ETI), Tim Shead (SNL), and Berk Geveci (KW) will serve as our 'Testing Team.'  They'll be responsible for testing enforcement at their respective workplaces.
* See [[ParaQ:Action Items]] for a list of action items handed out at this meeting (1005-09-13)

Latest revision as of 17:42, 9 November 2005

Agenda

Item People Description
1 KMor 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. See Demo:Script
5 DR Present Microsoft Project schedule overview
6 BW Update on videocon equipment

Qt Testing Requirements

  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.

Possible Solutions:

  1. Squish from Frog Logic
    1. $3,000 per seat for license for complete application
    2. $400 for license to just run tests
    3. Community contribution limited because of license cost
    4. Possible Difficulty integrating with VTK and Paraview testing framework
    5. Application to be tested started as child process and so dynamic analysis will be difficult
  2. KD Executor
    1. Similar in cost and limitation to Squish
  3. KUnitTest
    1. BSD license
    2. Tests must be written in C++
    3. Designed for unit testing not complete application testing
  4. QTestLib
    1. Dual license
    2. Tests must be written in C++
    3. Designed for unit testing not complete application testing
  5. QTester
    1. Written by LLNL
    2. Not finished
    3. Not open source yet
  6. Python Scripting
    1. PyQt licensing cost.
    2. Limitation in PyQt in that the leaf class of C++ constructed object can't be accessed.
    3. Must maintain own C++ wrapped classes and utilities

Recommendation:

Begin by linking ParaQ lib with testing main built using components of KUnitTest and/or QTestLib. This would allow us to meet our initial testing goals. Then develop more complete testing framework as project progress.

Decisions

  • Clinton Stimpson (ETI), Tim Shead (SNL), and Berk Geveci (KW) will serve as our 'Testing Team.' They'll be responsible for testing enforcement at their respective workplaces.
  • See ParaQ:Action Items for a list of action items handed out at this meeting (1005-09-13)
Retrieved from "http://www.paraview.org/ParaView/index.php?title=ParaQ:Telecon_09/13/2005_1PM_EST&oldid=4266"