What is Memory Leak ?

"A memory leak is the gradual loss of available computer memory when a program (an application or part of the operating system) repeatedly fails to return memory that it has obtained for temporary use. As a result, the available memory for that application or that part of the operating system becomes exhausted and the program can no longer function. For a program that is frequently opened or called or that runs continuously, even a very small memory leak can eventually cause the program or the system to terminate. A memory leak is the result of a program bug."

In bug tracking process for which we give importance for Severity or Priority?

"Severity & Priority will be given by the tester while logging the defects. and it shd be approved by his/her superior.

Severity defines how worst the functionlity is working.

Priority defines how fast the reported issues shd be fix.

(if defect is a showstopper then it will be critical&high like wise we have to assign)

and more over these will be depend on test case priority also.

while fixing the bugs developers mainly concentrate on these two areas to filter and fix the bugs. "


- Vignesh

what is the difference between bug and defect?

" Bug----->is related to internal part of code that is before the application goes to production.

Defect--->variance in expected result & actual result. or it is an error found after application goes to production. "

- Vignesh

what is the seviority if we will give the duplicate account number?


"It will come under high severity and high priority.but the account number should be the primary key here or composite key if any one is facing this type of problem please use account number as primary key or any other key to reduce inconsistancy. "


- Vignesh

who will give the bug id and bug version id?

"No one will give the bug ID explicitly. It'll be automatically generated by the bug tracking tool."


"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."


- Vignesh

What are latent bugs?

"Latent Bug: The bug which is not identified in present

version and can be able to identified in later versions."

- Vignesh

1.Create and customize fields: Integer, Float, URL, Text, Large Text, Boolean, and Pull-down types. Specify that certain fields are required fields to make sure that critical data are entered by the user.

2.Dependent (nested) Pull downs allow the set of values displayed in one pull downs to be determined by the values selected in another pull downs. For example, which items are displayed in the component field is determined by the product selected.

Regards
devarajan

__________________
Regards,
devarajan

Hi, guys

My simple tips:

1. Insure that your build process is applied to a working set of code. In other words, don't force developers to check in code prior to doing builds. Doing will likely cause developers to check in buggy code and cause issues with other developers.

2. You still want developers to check in code frequently. This is a management process, not a version control issue. If the tasks assigned to developers can be completed in a short duration, say two days max, then you can force developers to check in code when a task is complete. Scripts can be used to monitor the Repository for developers that have not checked in a defined period of time.

3. Backup your repository. Daily if not even more frequently.

4. Develop a simple nomenclature on what information should go into the comments/properties of a code checking. Best case - if you're working with SW requirements w/ ID's, then check in code with the IDs of the requirements (or bugs) that are being addressed.

Regards
devarajan

__________________
Regards,
devarajan

HI, guys

1. Tag your releases. If your staging a release, say through a QA process, then you can tag the release with a convention that includes the status (QA, PROD, etc.) and a version number for the release.

2. Whenever you cut a release to Production, archive the release and any executable builds. Although you can get the source straight from version control using the Tag, it's more convenient (especially for admins!) to have the releases archived in a folder outside of version control.

3. Make sure you have some form of release notes database (or spreadsheet) that lists the features/bugs with the release Tag and the date/time of the release.

4. Give developers the freedom to merge files. In most situations, merges are additive and the merges can be completed using tools. Even if the merge becomes complex, it's not a bad thing for developers to manage the issue by themselves via dialog and code review (tip #5).

5. Keep production parameters such as URLs, user names, passords, etc. outside of version control. Files with the production values for these resources should be managed by the Production team. The build process should have mechanisms to load in configuration files with these values.

A couple of things that you can avoid:

a) Don't worry so much about branching scenarios. In my experience, it's better to work out branching and merging branches when you're faced with that specific need.

b) Nightly builds are nice, but may be overkill for most teams. Understand why you need the nightly build and how you'll use it before scripting this out.


Regards
devarajan

__________________
Regards,
devarajan

Hi, guys

Use Virtual Folders - Mail calls them Smart Mailboxes. Outlook calls them Search Folders. In either case, the idea is the same: you can set up a folder whose contents depend on criteria you set, rather than messages you file in it. Obvious uses include folders for unread mail, old but unanswered mail, mail from particularly important people, and newsletters identified by subject line. Virtual folders are another good way to create the illusion that things are filed in more than one place.

Let Your Rules Do the Walking - You’ve got a rules engine in your e-mail client; use it. If you file every single message from Joe in the Friends folder, set up a rule to do this for you and save pointless seconds of dragging and dropping. Combine this with a virtual folder showing unread mail and you can have the rule clean out your inbox as soon as the mail arrives.

Use a Filing Assistant - If you have lots of folders, dragging and dropping messages to file them can get to be, well, a drag. It’s worth your while to find and use an application that streamlines this process. Examples include SpeedFiler for Outlook and Mail Act-On or MsgFiler for Mail on the Mac.

Regards
devarajan

__________________
Regards,
devarajan

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 "

-Vignesh

Describe Error Handling in the FRD

"FRD:: Functional Requirement Document

Error Handling in the FRD:::: In the design details there will be a ERROR HANDLING section where it will be mentioned about the error that will be present in the routine /script/code, so that by seeing error messages which be taken care and corrected.

Even while testing also.


And also ERROR HANDLING is when a routine is run for certain specification then if the specification is not present then a error will be added through a remark by the routine itself , when these remark is seen so that the specification is corrected as per the requriement "


- Vignesh

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. "

- Vignesh

How we can explain a bug which may arrive at the time of tesing. explain that bugs in details.

"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!!!


- Vignesh

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."

- Vignesh

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?

" Bug Tracking :

Any bug that is detected will have a status as New->Next Open->Assigned to developer-->Fixed-->Assigned to tester-->If pass after validation ,close the defect,if fail ,assign it back to the developer.This is the general flow of bug tracking ,either you may use a bug tracking tool or an excel sheet.It is convenient to use a bug tracking tool,but if we use an excel sheet also,we can change the status in each and every phase of bug life cycle.

Defect/Bug Format :

Bug/Defect Id:

Summary :

Steps to Reproduce/Description:xxxxxxxxxxxxxxxxxxxxxx

Detected By :abcd

Version Number :xx.0

Feature/Sub Module/Module :abcd/ab/a

Severity:Critical,High,Medium,Low

Priority :High,Medium,Low

Reproducible :Yes/No

Assigned to eveloper/Tester/QA Manager/etc

Status :New/Open/Fixed/Closed etc

Test Case Number :xx

Depending upon the company strategy we can add some extra fields in excel sheet or remove some fields which are not needed

Severity is the seriousness or the impact of the defect over the application/product functionality.It can be specified in different ways:

Critical,High,Medium and Low.

Critical :example like system halt or stuck i.e unable to proceed further testing

High :example like some main features are not working properly,where the user has a maximum usage

Medium and Low :This type of defects are not so urgent to be fixed ,but can wait for some time ,because there is impact on the functionality is not as severe as in critical and high.But should be fixed before releasing to the client.

Priority :By specifying the priority as high,medium and low ,a developer can understand which defect needs to be fixed prior to which defect.A developer will fix the defects that are having high status,next medium,next low.

To provide a priority status there is a formula as Priority=Severity (vs) Ratings

Ratings:It is decided as Always,Sometimes,Never.Always means every time defect is reproducible when a certain test case is executed.Sometimes means the defect is occuring for sometimes,but not always.Never mean the defect has occured only once ,but never occured when tried to reproduce

Example :Severity=High,Ratings=Always

Priority =High (vs) Always =High

Priority should be high,because severity is high and the defect is recurring always.This defect needs to be fixed by a developer with high priority.


- Vignesh

What are the different types of Bugs we normally see in any of the Project? Include the severity as well.


"1. User Interface Defects -------------------------------- Low
2. Boundary Related Defects ------------------------------- Medium
3. Error Handling Defects --------------------------------- Medium
4. Calculation Defects ------------------------------------ High
5. Improper Service Levels (Control flow defects) --------- High
6. Interpreting Data Defects ------------------------------ High
7. Race Conditions (Compatibility and Intersystem defects)- High
8. Load Conditions (Memory Leakages under load) ----------- High
9. Hardware Failures:-------------------------------------- High


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 re-fixing.

So this is the life cycle of a bug.

- Vignesh

What is the Difference between End to End Testing & System Testing

"System Testing:

This is the process of testing end to end business functionalities of the application(system) based on client business requirements.

End to End Testing:

This is the macro end of the testing.This testing mimics the real life situations by interacting with the real time data, network and harware etc.

In the system testing we are taking sample test data only, where as in the end to end testing we are taking real time data(for a sample) and interacting with network and hardware "

- Vignesh

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.


News reports in May of 2006 described a multi-million dollar lawsuit settlement paid by a healthcare software vendor to one of its customers. It was reported that the customer claimed there were problems with the software they had contracted for, including poor integration of software modules, and problems that resulted in missing or incorrect data used by medical personnel.# In early 2006 problems in a government's financial monitoring software resulted in incorrect election candidate financial reports being made available to the public. The government's election finance reporting web site had to be shut down until the software was repaired.# Trading on a major Asian stock exchange was brought to a halt in November of 2005, reportedly due to an error in a system software upgrade. The problem was rectified and trading resumed later the same day.# A May 2005 newspaper article reported that a major hybrid car manufacturer had to install a software fix on 20,000 vehicles due to problems with invalid engine warning lights and occasional stalling. In the article, an automotive software specialist indicated that the automobile industry spends $2 billion to $3 billion per year fixing software problems.# Media reports in January of 2005 detailed severe problems with a $170 million high-profile U.S. government IT systems project. Software testing was one of the five major problem areas according to a report of the commission reviewing the project. In March of 2005 it was decided to scrap the entire project. "

- Vignesh

what are the different methods to find all the requirements are covered other than traceability matrix ?


" Testcase Document , Test Plan ,Deployment document and configuration document ,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


- Vignesh