Difference between revisions of "CddMeeting01042008"
(→Tasks) |
(→Tasks) |
||
Line 31: | Line 31: | ||
* Install CDD in student labs | * Install CDD in student labs | ||
* Pause test execution and compilation during regular compilation and execution | * Pause test execution and compilation during regular compilation and execution | ||
+ | * Add most important convenience routine to CDD_TEST_CASE | ||
== Software Engineering Project == | == Software Engineering Project == |
Revision as of 07:19, 7 January 2008
Next Meeting
- Tuesday, 8.1.2008, 10:00
Tasks
- Define views for release (Andreas)
- Make manual test cases work (Arno)
- Fix extraction for generics (Stefan)
- Fix extraction for tuples (Stefan)
- Add non-commited test cases (Stefan)
- Interpreter compilation opens console on Windows (Andreas, Stefan)
- "New manual test case" Button (?)
- Better Icons for GUI (http://www.famfamfam.com/lab/icons/silk/) (?)
- Status / Progress bar (?)
- Port to 6.1 (?, probably only after Beta 1)
- Manual re-run to find true prestate (Jocelyn, ?)
- Executing TC in debugger (aka fg-execution) (Arno)
- Logging
- What data to log?
- Implement storing
- Define how students should submit logs
- Forumulate Experiment Hypothesis (Andreas)
- Define Project for SoftEng (Manu)
- User must be able to restrict what test cases get executed (?)
- Parse indexing clause of feature to gather feature tags (?)
- Restore open nodes and selection after grid update (Arno)
- Maybe better/easier solved via incremental updates from tree
- Data Gathering
- Define what data to gather
- Define how to process gather data
- Automate CDD System level tests
- Install CDD in student labs
- Pause test execution and compilation during regular compilation and execution
- Add most important convenience routine to CDD_TEST_CASE
Software Engineering Project
- One large project, but divided into testable subcomponents
- Students required to write test cases
- Fixed API to make things uniformly testable
- Public/Secret test cases (similar to Zeller course)
- Competitions:
- Group A test cases applied to Group A project
- Group A test cases applied to Groupt B project
Data to harvest
- Test Case Source (just final version, or all versions?)
- TC Meta Data
- TC Added/Removed
- TC Outcome
- TC execution time
- Questionnairs
- Initial
- Final