Difference between revisions of "CddBranch"
(→Meeting Minutes) |
|||
| Line 53: | Line 53: | ||
**** ... | **** ... | ||
| − | |||
| − | |||
== Specifications == | == Specifications == | ||
Revision as of 06:31, 8 January 2008
Contents
Summary
CDD is an extension to EiffelStudio that provides support for both automatic test case extraction and test execution. It is undisruptive to the development process of the user. The tool is in its early stages. Feedback and bug reports are very much appreciated. Please send them to mailto:andreas.leitner@inf.ethz.ch and or use the discussion page for this article.
Play Video!
Old Documentation
At this point there is only outdated documentation. It is available from CddOldDocumentation
Testing
Development (Todo's):
Schedule
- 04.01.2008: Final experiment definition (questions to ask, how to conduct experiment)
- 08.01.2008: Finalized list of features to go in release (including logging and log submission)
- 25.01.2008: Beta 1 (feature complete version online)
- 04.02.2008: Beta 2 (designated testers test release, # > 3)
- 18.02.2008: Final CDD release for experiment online
- 20.05.2008: Having all data
- 06.06.2008: Finished analysis
Stefans Master Plan
- MA Start ca 17.12.2007
- MA End ca 17.6.2008
- Testing the tester
- System level test for CDD (incl. framework)
- Recreating existing unit test suite with CDD
- Large scale validation of CDD
- Info 4 and/or Software Engineering
- Questions
- Does testing (manual/extracted) increase developer productivity?
- How many tests do ppl end up with (manual/extracted)?
- ...
Specifications
Things we need from estudio
- Invariants should be checked during debugging equally to pre- and post conditions (they could also be visualised in the flat view the same way like pre- and post conditions are)
- The information whether some call is a creation call or a normal routine call (Not sure if this is really necessary, what if we assume every call to some creation procedure is always a creation call?)
- Support for multiple open targets
