| Summary: | Quotation marks around string literals should produce descriptive error messages in case of misleading usage | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Maciej Bendkowski <maciej.bendkowski> |
| Component: | Deployment | Assignee: | Maciej Bendkowski <maciej.bendkowski> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | john.arthorne |
| Version: | unspecified | ||
| Target Milestone: | 6.0 M1 | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Maciej Bendkowski
Do we have JUnit tests for our manifest parsing and error reporting? This is the perfect kind of scenario for regression testing and making sure we handle the huge variety of errors users can make in their manifests. (In reply to John Arthorne from comment #1) > Do we have JUnit tests for our manifest parsing and error reporting? This is > the perfect kind of scenario for regression testing and making sure we > handle the huge variety of errors users can make in their manifests. Yes, we have. Each parser fix contains (and will contain) appropriate test cases. (In reply to Maciej Bendkowski from comment #2) > Yes, we have. Each parser fix contains (and will contain) appropriate test > cases. Great! I'm a big fan of this approach as you may have learned from Szymon ;) (In reply to John Arthorne from comment #4) > Great! I'm a big fan of this approach as you may have learned from Szymon ;) I'm also very keen on having fine grained unit tests and further, functional tests wherever possible. They usually hinder developers (including myself) from introducing regressions. Never too late for good practice. |