Docstoc

bug tracking

Document Sample
bug tracking Powered By Docstoc
					How to post a BUG

We can post the bug by email to developer and project manager.we can write the details about the bug, the situation and the condition in which it gets reproduce.
What is the difference between a Bug and a Defect?

Bug- Conformed defected is called bug. It is said to be bug only at developer place. Defect- Any Functionality is wrong then it is said to be defect by testers. It turns to bug in developers place
What are the difference between rational clearquest and testdirector?

Both are Test Mangement tools. Rational clearquest is from IBM. Test Director from Mercury. Most of the difference are unknown as features wise they have different features as rarely any company will be using both tools. One differnce is cost wise, two product from different company can not have same cost.
what is AUT???

AUT is "Application under test".After designing and coding phase of development cycle,when the application(build) comes under testing then at that time application state is under test,so at that time period that application(build) is called "Application Under test".
How would you say that a bug is 100 % fixed ???

In quality world you can't say Bug is 100 % fix or 50 % fix . If Bug is fixed than in new verssion we do regression testing to make sure that Bug fix doesn't have any impact on old functionality.
What is the Difference between End to End Testing & System Testing

End to End Testing: From first smoke test build to release of software to end of maintanence Complete Cycle of testing: From Reqts to Testing to release of software to end of maintanence system testing: Ex: There are 7 modules in project 1+2 = Integration testing (1+2)+3 = Integration testing ................................. (1+2...)+..+7= End of Integration testing = System Testing
How to give BUG Title & BUG Description for ODD Division?

Assumption: ODD number divison fails Bug Tile: Odd number divison fails Bug Description: 1. Open calc window 2. Enter an odd number. 3. click divide by(/) button. 4. Enter another odd number 5. Hit Enter or click "=" button in calc window

6. Observe the result
What is the difference between Bug Resolution Meeting and Bug Review Commitee? Who are the participants in Bug Resolution Meeting and Bug Review Commitee?

Bug resolution meeting: It is conducted in presence of Test lead and Developers where developers gives his/her comment wheather to correct the bug at this time or later and test leader accepts or rejects developers comments and even they decide what methods should be chosen to correct the error so that in regression test no bug should be reported and it should not effect other application. Bug review commitee:It is often conducted by test lead, project managers in presence on client, where they all decide as to what errors should be considered as bug and what severity level it shuld be treated as.
Can anyone please tell me "what will be the role of tester if bug is reproduce "This question was asked in the Interview.

Whenever the bug is reproduced, tester can send it back to the Developer and ask him to fix it again. If the developer cannot fix the bug once again and if the tester sends the bug back to developer, the third time, the tester can make the bug as Defered ie he can reject the build (.exe)
How to do database testing by using automation tool. How to check runtime database checkpoints. i want to check that wheather the current record is added in database table after execute the adding a record

This is depends upon which automation tool u are using ok.. Suppose let us take WinRunner in WinRunner we have the check point in Database checkpoint in that u have the Runtime record check using that we can compare the Runtime record is there in database or not
What do u mean by "Reproducing a bug"? If the bug was not reproducable, what is the next step?

Reproducing Bug means the defect/Bug reappears at dev environment then they will resolve and fix the Bug. Bug is not reproducable at dev environment then we will send the Execution steps with appropriate Screen shots clearly.
what is build interval period? in simple words plz

It is the period of bug life. Starts when tester finds a bug & Ends when Tester marks it as closed
Top Ten Tips for Bug Tracking

I recommend adding small comments to the main pieces of codes and using debug messages. You can also implement a "debug mode", which can be a global variable. If that mode is enabled, the variables values will be shown in the critical places of the application. This should help tracking the variables and seing when the problem occurs. (this method can be useful when the development environment does not have a 'watch')
What are the different types of Bugs we normally see in any of the Project? Include the severity as well.

The Life Cycle of a bug in general context is: Bugs are usually logged by the development team (While Unit Testing) and also by

testers (While system or other type of testing). So let me explain in terms of a tester's perspective: A tester finds a new defect/bug, so using a defect tracking tool logs it. 1. Its status is 'NEW' and assigns to the respective dev team (Team lead or Manager). 2. The team lead assign's it to the team member, so the status is 'ASSIGNED TO' 3. The developer works on the bug fixes it and re-assings to the tester for testing. Now the status is 'RE-ASSIGNED' 4. The tester, check if the defect is fixed, if its fixed he changes the status to 'VERIFIED' 5. If the tester has the autority (depends on the company) he can after verifying change the status to 'FIXED'. If not the test lead can verify it and change the status to 'fixed'. 6. If the defect is not fixed he re-assign's the defect back to the dev team for refixing. So this is the life cycle of a bug.
How do we track a bug?plz send format of excel sheet in which we write the bug details?how do we give the severithy and priority to the bugs?

Tracking a bug is much easier and communicative when done through a tool. format of the tool: BUG ID TEST CASE ID DESCRIPTION SEVEORITY PRIORITY ASSIGNED TO STATUS REMARKS

(bug id is usually generated by the tool) outside the excel sheet we might need to fill the fields like: tester name (uasually genrated with the login name) date of execution etc. a <submit> and < cancel> button
How to post a BUG

Posting a bug through EMail is not done anywhere these days in real-time , as it would lead to miscommunication and creates lot of confusion at the long run..Hence a tool bought by the company or a tool built by our own company will be used. The tools features would be almost same even though their GUI might vary. Some tools will have a format like Excel sheet where we can enter the details of a bug and save it ,where an email is sent to the assigned person (name and ID will be set in the tool) , when ever status of the bug is changed you will recieve an another mail..
What is the difference between a Bug and a Defect?

Bug- Conformed defected is called bug. It is said to be bug only at developer place. Defect- Any Functionality is wrong then it is said to be defect by testers. It turns to bug in developers place
How we can explain a bug which may arrive at the time of tesing. explain that bugs in details.

Explaining a BUG is an ART for a TESTER... So...it has lot of things inside From my learning...I do this! 1. Moment you get the bug, just double check in the bug DB for duplicates. I mean from the earlier build, it might've been uncovered and recorded as a bug and the release manager might've decided to fix it in later builds. 2. Not there in DB, then analyse the bug for confirmation. If you are strongly recomand that as a bug, you can proceed OR please reconfirm with peers 3. Still BUG? So, go ahead use the Bug Tracking database (if any) or use the excel bug reporting format (whatever you have) But, tell everything clear. a. Bug Title, Bug Description, The setup you have to reproced, the Priority, Impact b. H/W and S/W used c. Screen shots, Log file (if any), SQL Qurey statements...If possible record the entire steps in a movie file and send the clip!!!
Whats the difference between usecase,testcase,testplan,and scenario and their templates.

use case - Desighned before the project started. Test Case - which contains the test data. test plan - A detailed plan to outline when to start and when to stop and constriants for automation or manual and about human resources. Scenario - scenario's will be identified while testing.
What are the difference between rational clearquest and testdirector?

Test Director is Defect Tracking Tool.It also supports Test Process Management i.e it allows creating test plans,running test cases and tracking defects. Rational Clear Quest is customized defect tracking and change request tracking tool.We can submit change requests and track change requests.
Could any one Explain,What is Difeerance Between Tracability Matrix & Cross referance Matrix

Tracability Matrix: The traceability matrix ties individual requirements in the SRS both to specific paragraphs in the SDS and to specific lines in the pseudocode. The objective of the traceability matrix is to assure that all requirements listed in the SRS have been addressed in the design.A good method for presenting the traceability matrix is as a table. Use the paragraph numbering from the documents to make the references to individual requirements and parts of the SDS unambiguous. Ideally, there will be a straightforward relationship between SRS contents and the SDS contents, with all parts of the SDS motivated by requirements in the SRS and every part of the SRS corresponding to something in the SDSCross Referance Matrix: The test-requirements cross-reference matrix shows how every requirement listed in the SRS will be tested. In some cases, this can be arranged in the form of a table. In other cases, bullet lists provide a better approach to presenting the information in a readable form. Ideally, there will be a straightforward relationship between requirements in the SRS and the tests, with every test motivated by requirements in the SRS and every part of the SRS corresponding to one or more of the tests.To ensure all functional requirements have been captured in the detailed design, cross-reference each functional requirement with it’s associated Detailed Design element.
How is traceability of bug follow?

The traceability of bug can we followed in so many ways. *Mapping the Functional requirements scenarios (FS Doc) - test cases(ID) -- Failed test cases (Bugs) Mapping between requirements (RS Doc) - test case (ID) - Failed Test Case Maping between Test plan (TP Doc)- test case (ID) - Failed Test case mapping between business requirements (BR Doc) - test Case (ID) - Failed Test case Mapping between High Level Design (Design doc) - Test Case (ID) - Failed test case. Usually the traceability matrix is mapping between the requirements, client requirements, function specification, test plan and test cases. Typically, in test situations, traceability matrices are used to trace requirements to test cases in order to ensure that there are test cases for all the requirements. Some easily aviailable commercial tools like Rational Suite Enterprise, will help testing engineer/ test lead to trace requirements and then to trace from the use cases and/or requirements to test cases. Of course, usually many types of traceability matrices may be created a just simple concept of REVERSE ENGINEERING. For example, you may trace Bug--> identify that test cases-->use cases and vice versa. The default term likely applies to tracing requirements to test cases though.
What is the difference between SQA Robot and Rational Robot or does both are same?

SQA robot and Ratinal Robot are the products of IBM Products.Noramally used for testing IBM application. SQA robot and Rational Robot are one and same .But only differneces is the advanced verion of SQA Robot is Rational Robot.
On what basis the planned testing efforts is calculated for the entire project?

The Planned testing efforts can be calculated with 2 different techniques. 1. Function Point Analysis 2. Testing Point Analysis These methods involves the calculation on the number of functional points present in the application. I have not performed any analysis, but in our company we are following these methods.
How would you say that a bug is 100 % fixed ???

Successful Retesting the defect will ensure you that the defect is fixed and after doing successful regression for the related failed/on which defect was raised in next passes/phase will enusre that the defect is fixed.
What are the different methods to find all the requirements are covered other than traceability matrix ?

one more method is Testing Matrix, which is nothing but a table index, which shows the result of Equivalence Range methods results, for example assume that your application is behaving as similar for some range of values, then take the range of values on columns side and test cases on row side, show the result in matrix form diagram range1 range2 range3 Test CaseA Pass Fail Fail Test CaseB Fail Pass Fail

Test CaseC Fail Fail Pass

What are some recent major computer system failures caused by software bugs?

Y2kbug was recent bug which caused failed in computersystem in europe y2k bug means after 1999 ,2000 as to come but there was a problem in system & due this bug europe had to face lot of problems in train time management system.
What is build interval period?

In some companies specially in J2EE domain, builds are delivered from development team to the testing team to start the system testing. For example a new product XXX is being released to the testing team so the dev team will deliver a build to the Testing team. Now Testing team will do the testing and then will release the product to the client. Now there is a new version of the product coming up with the name XXX.1 and is being released to the testing team, so this will be the second build and the time between these 2 builds will be called as build interval.
What is Defect Life Cycle in Manual Testing?

Defect Life Cycle is the Cycle thru which a defect goes starts when defect found & ends when defect is closed after ensuring its not reproduced.Defect Life cycle is related to Bug found during testing so it doesn depend on Manual & Automated Testing. Phases of Defect Life Cycle is 1. New : When Defect disccovered. 2.Open: When defect is addressed to the developer. It may then be Rejected, said to be duplicate or deferred. 3. Fix : when it is fixed or defect solved by developer. 4.Close : After defect addressed by developer it comes to Tester to Test, once assured its no more a defect its is Close phase. There are more phases to this if it is to be discussed in too details but on primary level this is the right answere.
Write the equivalence classes for 1-99 range of value write test case and testdata for a triangle After closing a bug we can open it again or not why do u like testing than development what is meant by join,different types of join what are the different types of files saved in the folder along with the test results what r the test activities u may want to automate performance test comes under which type of testing Resource bugs,timely bugs comes under which type of testing can we do performance testing manually

Performance testing is a kind of non functional testing,it comes under system testing. performance test can be done manually...but it is not in practice. test data for triangle sides,angles,
On what basis we give priority and severity for a bug and give me one example for high priority and low severity and high severity and low priority?

Always the Priority is given by our T.L Tester will never give the priority ... Ok I will some example for High Severity :- H/W Bugs Application crash. Low Severity :- User Interface Bugs

High Priority :- Error message is not comming on time, caculation Bugs etc.. Low Priority :- Wrong Alighment, Final Output Wrong.
What do u mean by "Reproducing a bug"? If the bug was not reproducable, what is the next step?

Reproducing Bug means the defect/Bug reappears at dev environment then they will resolve and fix the Bug. Bug is not reproducable at dev environment then we will send the Execution steps with appropriate Screen shots clearly.
How can we know bug is reproduceable or not?

If the bug is getting simulated in all the environments available with same simulation steps then we can say the bug is reproduceable otherwise not.


				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:821
posted:1/8/2008
language:English
pages:7