I recently faced an interview in which I was asked the below questions-
If you are part of UI design for an application then would you prefer a Calender Object(just like windows calender) where in you can pick the date directly or a simple Date Text Field in which you have to manually enter the date?
Hi Joe..the position is for QA. I've answered that from an end user point of view calendar object is preferable than a normal date text field as the no. of clicks will be less when selecting date from a calendar object. The interviewer then said it may not be the case all the time. I'm basically looking for scenarios like when a calendar object is preferable and when a normal date text field is preferable.
I suppose I would have talked about control. My initial reaction is with a text field you can not control what is being entered, increasing the amount of tests to cover all the scenarios or more likely more scenarios not being tested.
On the calander object you can control what is being entered.
I'd say you probably want both: and a text control and a popup datapicker, where both controls are synchronised on update.
Assuming the form is also used for displaying the information the textual representation is much clearer to the user, while also providing the ease of use of a datepicker; also you give the user a choice: manual input or clicking.
Only caveats are localisation and parsing manually entered data.
How ever on testing part it becomes a mamoth task because as you have to check so many validations .
In my previous organisation I tested an online portal which used Calender Control, during testing I had raised defect related to the performance of the control. It used to take time to open up. I would prefer a text field and give the format next to the field.