Hi Arpita, HUGE apologies, but I still haven't had time to provide you feedback on test cases you provided last week.
In case you are short on work to do since most of the test cases that you are working are awaiting review, you can look at the list of bugs that have been marked as 'resolved' in the issue tracker and work on verifying them to see if they have actually been fixed. We will formalize this process eventually (e.g. who is responsible for testing which bugs and when this should be done), but for now, feel free to spend some time on this if you are finding that you do not have enough to do. Here is the list of bugs that need to be verified: https://mifos.dev.java.net/issues/buglist.cgi?resort=1&issue_type=DEFECT ;component=mifos;issue_status=RESOLVED;resolution=FIXED;email1=;emailtyp e1=exact;emailassigned_to1=1;email2=;emailtype2=exact;emailreporter2=1;i ssueidtype=include;issue_id=;changedin=;votes=;chfieldfrom=;chfieldto=No w;chfieldvalue=;short_desc=;short_desc_type=fulltext;long_desc=;long_des c_type=fulltext;issue_file_loc=;issue_file_loc_type=fulltext;status_whit eboard=;status_whiteboard_type=fulltext;keywords=;keywords_type=anytoken s;field0-0-0=noop;type0-0-0=noop;value0-0-0=;namedcmd=GK%20v1.0%20bugfix es;newqueryname=;Submit%20query=Submit%20query&order=issues.priority%2C% 20issues.issue_id Here are some brief guidelines: * Unfortunately, the issue tracker doesn't allow you to assign a bug to someone after it has been marked as 'resolved'. If you reassign it, the bug gets opened again. So, if you are going to work on verifying a bug and there are other testers on your team that are also verifying bugs from this list, you should probably just check with them that they are not already working on the issue you have chosen to verify (so no efforts are duplicated). * When possible, include details of what you tested and how you tested things, if the way you went about things is not so obvious (or the bug does not have a simple repro). * If you have any questions on how you should go about testing things and need feedback from the developer who fixed the issue or a PM on the team, feel free to email the listserv with your questions. Of course, if you are still finding yourself busy enough already, do not worry about taking on any of the bug regressions for now. Thanks, Aliya ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
