| Author |
search in GUI:
|
Sigrid Kajdan
Ranch Hand
Joined: Jan 14, 2007
Posts: 72
|
|
Hi all, in my spec it says about GUI search:
It must allow the user to search the data for all records, or for records where the name and/or location fields exactly match values specified by the user.
"exactly match" - I wonder if this means I may not even use equalsIgnoreCase() here? Normally I would just use it and write this in the choices.txt, but considering it's a MUST requirement I'm afraid it could cause automatic failure before... What do you think, is this "overly paranoid" or should I really refrain from using case-insensitive matching here? Thanks for your opinions (experiences?) Sigrid
|
 |
Tom Doyle
Greenhorn
Joined: Apr 23, 2002
Posts: 9
|
|
|
I think this is a design decision that would be argued either way. I chose to ignore case and qualified that approach by documenting it among my design decision points.
|
Best regards<br />Tom<br /> <br />SCJP4<br />SCJD6 (B&S in progress)
|
 |
Sigrid Kajdan
Ranch Hand
Joined: Jan 14, 2007
Posts: 72
|
|
Hi Tom, thanks for your answer. I think I'll stick to the case-sensitive version now as it fits nicely with my equals() method, but it's good to know other's opinions! Ciao, Sigrid
|
 |
 |
I agree. Here's the link: jrebel
|
|
subject: search in GUI:
|
|
|