[TIMOB-10925] CodeProcessor: Validate against well known complex samples and fix bugs that come up
| GitHub Issue | n/a |
|---|---|
| Type | Story |
| Priority | Low |
| Status | Closed |
| Resolution | Won't Do |
| Resolution Date | 2016-08-24T19:25:34.000+0000 |
| Affected Version/s | Release 3.0.0 |
| Fix Version/s | n/a |
| Components | Code Processor |
| Labels | n/a |
| Reporter | Bryan Hughes |
| Assignee | Chris Barber |
| Created | 2012-09-14T15:14:31.000+0000 |
| Updated | 2016-08-24T19:25:40.000+0000 |
Description
We need to run the code processor against some well known, complex code samples. We can use the data for debugging and planning new features in the code processor.
Most complex samples rely on modules, so we can't validate until module support has been implemented.
The unknown/ambiguous reporter will be essential in determining why the known samples are not being fully analyzed
The updated analysis coverage plugin will be really useful in narrowing down what is not being analyzed
Changing this ticket to a placeholder ticket that will eventually contain subtasks. The nature of the subtasks will be dependent on how other tickets go.
This seems like an open ended ticket for a product that is dead.