Agenda&Status 070610: Difference between revisions
From KitwarePublic
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| (3 intermediate revisions by one other user not shown) | |||
| Line 16: | Line 16: | ||
** CTest runs the tests | ** CTest runs the tests | ||
** Google testing provides a framework for unit tests. | ** Google testing provides a framework for unit tests. | ||
*** [http://code.google.com/p/googletest/wiki/GoogleTestPrimer Google Test Primer] | |||
*** Test "A" should return a value of 5, verify the test produces the correct value | *** Test "A" should return a value of 5, verify the test produces the correct value | ||
**** Currently encoded in individual tests by the test writer | **** Currently encoded in individual tests by the test writer | ||
| Line 22: | Line 23: | ||
** What are the requirements for a new test framework? | ** What are the requirements for a new test framework? | ||
** How does this tie into CTest @ Home? | ** How does this tie into CTest @ Home? | ||
** How does Google Test compare to Brad's article on IJ on testing? | |||
** Luis, Dan, Hans, Brad, Brian to follow up | |||
* Wrapping (Stephen's hair brained idea) | * Wrapping (Stephen's hair brained idea) | ||
* | ** Matlab like wrapping sounds good | ||
** Microscopy people still use streaming and pipeline | |||
** Python infrastructure register modules with pipeline. Dan's design does support some of this? | |||
** Also sounds like NiPype but NiPype doesn't stream | |||
* Google Docs site for sharing proposals for ITK v4 and A2D2. Just technical sections, no business plans needed. Email Jim to get access. | * Google Docs site for sharing proposals for ITK v4 and A2D2. Just technical sections, no business plans needed. Email Jim to get access. | ||
Latest revision as of 18:20, 6 July 2010
First tcon using WebEx
- Web forums (nabble, google group)
- Needs to be mirrored on email list.
- Searching forums
- Threaded discussions
- Sharing Files (drop.io is an option)
- Try to limit the number of tools and sites that we use.
- Copyright issue on posted content.
- Nabble allows contributors to maintain ownership of material posted.
- Can also use forum mechanism to broadcast on main page.
- What about non-member postings?
- Can subscribe in mailman without being set up to receive emails?
- Google testing framework
- CDash aggregates results
- CTest runs the tests
- Google testing provides a framework for unit tests.
- Google Test Primer
- Test "A" should return a value of 5, verify the test produces the correct value
- Currently encoded in individual tests by the test writer
- Google Test Primer
- Google Test could streamline the process of writing tests and hence make it more likely that people write good tests
- What are the requirements for a new test framework?
- How does this tie into CTest @ Home?
- How does Google Test compare to Brad's article on IJ on testing?
- Luis, Dan, Hans, Brad, Brian to follow up
- Wrapping (Stephen's hair brained idea)
- Matlab like wrapping sounds good
- Microscopy people still use streaming and pipeline
- Python infrastructure register modules with pipeline. Dan's design does support some of this?
- Also sounds like NiPype but NiPype doesn't stream
- Google Docs site for sharing proposals for ITK v4 and A2D2. Just technical sections, no business plans needed. Email Jim to get access.
