You can use following suggestions to prioritize bug hunting in your software testing effort.1) Test things that are changed before things that are the same. Fixes and updates mean fresh risk.
2) Test core functions before contributing functions. Test the critical and the popular things that the product does. Test the functions that make the product what it is.
3) Test capability before reliability. Test whether each function can work at all before going deep into the examination of how any one function performs under many different conditions.
4) Test common situations before esoteric situations. Use popular data and scenarios of use.
5) Test common threats before exotic threats. Test with the most likely stress and error situations.
6) Test for high-impact problems before low-impact problems. Test the parts of the product that would do a lot of damage in case of failure.
7) Test the most wanted areas before areas not requested. Test any areas and for any problems that are of special interest to someone else on the team.