| || |
Testing Search UI
I am involved in web-testing. The AUT is added with couple of new functionalities. One of them is Search.
The Search UI for few modules is Simple & some of them are really difficult to in terms of design.
Simple UI have 2/3 searchable fields but other ones have 6/7 fields. Fields are combinations of combo & text and checkboxes. Though I have started testing it I am not confident of how to achieve most coverage under these conditions. I am concerned about framing all possible search criterias (valid and invalid) using all fields values.
If anyone suggests me a mechanism how to cover or determine maximum possible combinations in terms of search criteria I would appreciate his help very much.
Thanks & Regards
Re: Testing Search UI
You could use Equivalence Partitioning and/or a Truth Table. If you search his forum, you will find discussion about Equivalence Partitioning.