My opinion on regression testing priority.
1. Biggest Bang for the buck (i.e. major functionality). If you are new this is the area that you will want to make general functions that will be able to be used in other testing. **Note below for more info.
2. Errors found in production. If an error made it to production, you would want to make a script to test for it so that it doesn't happen again. Nothing in QA looks worse than an error getting into production more than once.
3. Stuff that is easy to automate (i.e. the menu funtionality, dialog functionality, etc.)
4. If time then try automating the rest.
** A assumption I have for step 1 is that a TestPlan is already in place. If this isn't true, then creating a test plan would be step one. So after a test plan is created, go through this test plan and determine the high priority test cases and these are where I would start. Also, talk to the user/support staff to find out what area's normally have issues in production.
1. Biggest Bang for the buck (i.e. major functionality). If you are new this is the area that you will want to make general functions that will be able to be used in other testing. **Note below for more info.
2. Errors found in production. If an error made it to production, you would want to make a script to test for it so that it doesn't happen again. Nothing in QA looks worse than an error getting into production more than once.
3. Stuff that is easy to automate (i.e. the menu funtionality, dialog functionality, etc.)
4. If time then try automating the rest.
** A assumption I have for step 1 is that a TestPlan is already in place. If this isn't true, then creating a test plan would be step one. So after a test plan is created, go through this test plan and determine the high priority test cases and these are where I would start. Also, talk to the user/support staff to find out what area's normally have issues in production.