Bug 388029 - Cleanup and make consistent test framework parameters
Summary: Cleanup and make consistent test framework parameters
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Releng (show other bugs)
Version: 4.2   Edit
Hardware: PC Linux
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-Releng-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-24 16:09 EDT by David Williams CLA
Modified: 2013-04-25 21:29 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description David Williams CLA 2012-08-24 16:09:28 EDT 
As noted in bug 381896 comment 18, there are are inconsistencies in how parameters are handled, some allowing any case, (e.g. user could specify "className", "claSSnamE" or "CLASSNAME" and they'd all be interpreted as "classname", but other cases do not ignore case. 

Myself I'd prefer to never "ignore case". But, this would sort of be like an API breaking change. I guess its not an "official" deliverable, but ... would be inconvenient to break others for only case issues. 

But, there are other issues in that command line handling, IMHO. Nothing functionally wrong, per se, but hard to understand. Some command expect arguments and advance the index (though little reason to) ... others do not, but base "reading the parameters" on a specific number of characters (instead of a true parse). 

So ... just opening this to track various potential "cleanup" issues. 

While relatively minor, if we really wanted to revamp the test framework for "production use", this is one area that could use some work.