ParaQ:Telecon 09/13/2005 1PM EST: Difference between revisions
From ParaQ Wiki
Jump to navigationJump to search
No edit summary |
|||
(17 intermediate revisions by 3 users not shown) | |||
Line 2: | Line 2: | ||
{| cellpadding="2" cellspacing="4" style="backround:#efefef" | {| cellpadding="2" cellspacing="4" style="backround:#efefef" | ||
|- | |- | ||
! style="background:# | ! style="background:#abcdef" | Item | ||
! style="background:# | ! style="background:#abcdef" | People | ||
! style="background:# | ! style="background:#abcdef" | Description | ||
|- | |- | ||
|- | |- | ||
Line 24: | Line 24: | ||
| 4 | | 4 | ||
| BW,DR | | BW,DR | ||
| Present demo script. See [[ | | Present demo script. See [[Demo:Script]] | ||
|- | |- | ||
|- | |- | ||
Line 37: | Line 37: | ||
|} | |} | ||
==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 171: | 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. | ||
Possible Solutions: | |||
# Squish from Frog Logic | |||
## $3,000 per seat for license for complete application | |||
## $400 for license to just run tests | |||
## Community contribution limited because of license cost | |||
## Possible Difficulty integrating with VTK and Paraview testing framework | |||
## Application to be tested started as child process and so dynamic analysis will be difficult | |||
# KD Executor | |||
## Similar in cost and limitation to Squish | |||
# KUnitTest | |||
## BSD license | |||
## Tests must be written in C++ | |||
## Designed for unit testing not complete application testing | |||
# QTestLib | |||
## Dual license | |||
## Tests must be written in C++ | |||
## Designed for unit testing not complete application testing | |||
# QTester | |||
## Written by LLNL | |||
## Not finished | |||
## 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
- 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.
Possible Solutions:
- Squish from Frog Logic
- $3,000 per seat for license for complete application
- $400 for license to just run tests
- Community contribution limited because of license cost
- Possible Difficulty integrating with VTK and Paraview testing framework
- Application to be tested started as child process and so dynamic analysis will be difficult
- KD Executor
- Similar in cost and limitation to Squish
- KUnitTest
- BSD license
- Tests must be written in C++
- Designed for unit testing not complete application testing
- QTestLib
- Dual license
- Tests must be written in C++
- Designed for unit testing not complete application testing
- QTester
- Written by LLNL
- Not finished
- 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)