Difference between revisions of "CddBranch"
(→Old Documentation) |
(→What is the CDD extension for EiffelStudio?) |
||
| Line 5: | Line 5: | ||
== What is the CDD extension for EiffelStudio? == | == What is the CDD extension for EiffelStudio? == | ||
| − | CDD (short for Contract Driven Development) is a project developed at ETH Zurich. The extension adds full support for unit testing to EiffelStudio. It also introduces the new idea of extracting test cases automatically from failures observed via the debugger. The following | + | CDD (short for Contract Driven Development) is a project developed at ETH Zurich. The extension adds full support for unit testing to EiffelStudio. It also introduces the new idea of extracting test cases automatically from failures observed via the debugger. The following lists the main features of CDD: |
* Automated extraction of test cases from failures | * Automated extraction of test cases from failures | ||
Revision as of 06:28, 28 January 2008
Contents
What is the CDD extension for EiffelStudio?
CDD (short for Contract Driven Development) is a project developed at ETH Zurich. The extension adds full support for unit testing to EiffelStudio. It also introduces the new idea of extracting test cases automatically from failures observed via the debugger. The following lists the main features of CDD:
- Automated extraction of test cases from failures
- For every exception thrown a new test case is created
- Visualization of test cases and their outcomes
- One button creation of manual test cases
- Automated execution of test cases in the background
- Limit visible test cases via predefined filters and custom tags
- Testing occurs in the background and is completely undisruptive for the developer
If you have questions, feedback, or would like to report a bug please visit the [CDD forum]
Play Video!
(TODO: Update with more recent screenshot and video)
Documentation
- Download CDD Beta 1
- Linux: http://se.ethz.ch/people/leitner/cdd/Eiffel60_cdd_beta_1.tar.gz (Download the above file and install it just like you would install a EiffelStudio tar ball. Afterwards proceed to section "Using CDD".)
- Windows: To be released soon.
- Using CDD
- Common Problems
Old Documentation
Documentation for relase of CDD for EiffelStudio version 5.7 is available from CddOldDocumentation.
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)
- 27.01.2008: Beta 1 (feature complete version online)
- 04.02.2008: Beta 2 (designated testers test release, # > 3)
- 11.02.2008: Beta tester feedback in
- 18.02.2008: Final CDD release for experiment online
- 19.02.2008: Initial Questionnaire
- 25.03.2008: Midterm Questionnaire
- 19.05.2008: Final Questionnaire
- 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)?
- ...
Testing
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
