If you will find out the bug (as you are a tester) you give the description of the bug and the location. if possible you can also take a screen shot of the bug if it is related to the GUI. and submit it than the error tracing tool will generate the bugid. and this bugid will assign to any developer to solve. it is called bug life cycle.
I think u r asking the question related to manual testing without using bug tool. so dear there is no standard to assign this bug id to this bug. The main thing is which type of bug is? how severe the bug is? in which module the bug is? the tester who reporting the bug will assign it if there is no bug tracking tool but keep in mind it should somewhat self explanatory. The bug tool does is automatically by using the information like projectname module name etc.
I think u r asking the question related to manual testing without using bug tool. so dear there is no standard to assign this bug id to this bug. The main thing is which type of bug is? how severe the bug is? in which module the bug is? the tester who reporting the bug will assign it if there is no bug tracking tool but keep in mind it should somewhat self explanatory. The bug tool does is automatically by using the information like projectname module name etc.
Hi If we user the BTS for bugs then the number for bug ids will automatically genarated.. if you are logged the bug ids manualy ( In test director or Excel sheet) then you've to follows some standards..some comps follow some standards.. For ex : Register_1Here 'Register' referes name of the page and the '1' referes ' no of the bug'.srinivasulu.B (srinivasulub1981@navayuga.co.in)
In our project we did not use any defect tracking tool during user acceptance phase as the license for Mercury quality center got expired. In such circumstances we generated the defect ID ourself. We used this convention for defect ID. Build Version_Module Name_Seq No. For example if u find the first defect in the inventory module in the build version 4.12 then the defect id generated is 4.12_INV_001. We will the defects in the excel sheet and at the end of testing we will commit it into CVS
