Whoisexpert

Test cases for ATM Transactions

2010-01-26T10:21:00.000-08:00

1. Successful insertion of card
2. Unsuccessful operation duto insertion of wrong angle
3. Unsuccessful operation duto insertion of wrong card(invalid card)
4. Successful entry of PIN number
5. Unsuccessful operation duto of wrong PIN enter 3times
6. Successful selection of languages
7. Successful selection of Acc Type
8. Unsuccessful operation duto of wrong Acc Type
9. Successful Selection of withdraw option
10. Successful entry of amount
here every one discussion about with drawing money, the given question was money transactions .
1.verify ATM card insertion
2.verify card insertion when card in invalid card ( other bank card,scratches on card)
3.verify card insertion with other angles .
4.verify language selection.
5.verify entry of pin number
6.verify operation when you enter wrong pin more than 3 times
7.verify opration with selection of account type.
8.verify operation with selection of wrong account type.
9.verify balance enqiry
10.verify the entered transaction account number
11.verify when entered the transaction accont number is wrong
12. Verify when cancell button click while transfering money.
13.verify after exit

TC 1:- succesful card insertion.
TC 2:- unsuccessful operation due to wrong angle card insertion
TC 3:- unsuccesssful operation due to invalid account card.
TC 4:- successful entry of pin number.
TC 5:- unsuccessful operation due to wrong pin number entered 3 times.
TC 6:- successful selection of language.
TC 7:- successful selection of account type.
TC 8:- unsuccessful operation due to wrong account type selected w/r to that inserted card.
TC 9:- successful selection of withdrawl option.
TC 10 :- successful selection of amount.
TC 11:- unsuccessful operation due to wrong denominations.
TC 12:- successful withdrawl operation.
Tc 13 :- unsuccessful withdrawl operation due to amount greater than possible balance.
TC 14 :- unsucceful due to lack of amount in ATM.
TC 15 :-un due to amount greater than the day limit.
TC 16 :- un due to server down.
TC 17 :- un due to click cancel after insert card.
TC 18:- un due to click cancel after indert card and pin no.
TC 19:- un due to click cancel after language selection,account type selection,withdrawl selection, enter amount

Test cases for Telephone

2010-01-26T10:20:00.000-08:00

Tc1
Action: check the interface of telephone , here interface means all buttons are available and should place on proper place.
Expected result: Interface of telephone is correct
Tc2
Action: check the functionality of each button like press the button redial
Expected result : all the buttons works properly.
TC 3
Action : check the volume level of phone
Expected result. volume level is available in the phone.
Tc4
Action : randomly enter the long number
Expected result : give some message like no is not valid
TC5
Action: check for the ringer
Expected result : Telephone have ringer tone.
TC6
Action: check for the dial tone
Expected result : telephone have dial tone
TC7:
check for the connection
TC8:
Check at the receiverside he receive the message properly or not.
1. To check connectivity of telephone line or cable
2. To check the modem to determine whether it is functioning or not
3. To check dial tone of the phone
4. To check the keypad while you dial any valid number on the phone
5. To check ring tone with it’s volume levels
6. To check voice of both sides (from and to) of the phone
7. To check display monitor if the phone has
8. To check redial option whether its functioning or not
10. To check the company standard of phone
11. To check the weight and color of the phone
12. To check loud speaker whether it is functioning or notany missing above then you can add any more test cases

Test cases for Electric Bulb

2010-01-26T10:19:00.000-08:00

The buld should be of reqd shape and size
- Should be able to be fitted and removed from the holder .
- Should sustain the voltage for which it is designed for
- Should glow on switching on
- Should not glow on switching off
- Should glow with reqd illumination(correct me if wrong)
- Life of the bulb should meet the reqrmt
1) The bulb should be of required shape and size
2) Should be able to be fitted and removed from the holder
3) Should sustain the voltage for which it is designed for
4) Should glow on switching on
5) Should not glow on switching off
6) Should glow with reqd illumination (correct me if wrong)
7) Life of the bulb should meet the requirement
1.Holder and sachet should be present to test the bulb
2.Check electricity connection should be there for that holder.
3.Check whether electricity is passing through that wire or not
1)check the colour appearance of the bulb
2) check the colour of light which it makes (illuminates)
3)check the time it takes to blow
4) check the max life of bulb
5) check if switch on and switch off suddenly what will happen
6) check the power consumption
7) check the initial voltage it takes to blow
8) check if voltage vary suddenly what will happen (increase or decrease)
9) check what will happen when switch on bulb in less voltage
10) check max heat dissipate when bulb is on

Test cases for Elevator (LIFT)

2010-01-26T10:18:00.000-08:00

Some of the use cases would be:
1) Elevator is capable of moving up and down.
2) It is stopping at each floor.
3) It moves exactly to that floor when corresponding floor no is pressed.
4) It moves up when called from upward and down when called from downward.
5) It waits until 'close' button is pressed.
6) If anyon steps inbetween the door at the time of closing, door should open.
7) No break points exists
8) More usecases for the load that the elevator can carry (if required)
Capacity of the lift
usability (whether its easy to operate or not)
Functionality( whether it functions properly or not)
comfort (whether a person is comfortable in it or not)
height
weight
volume
time it takes to reach every floor
test for maximum capacity of the lift
test for more than max capacity
check the working in case of a power failure
Yes, when a senario is given to us i think it would be most appropriate to ask the Interviewr what is he expecting? This would actually show our attitude towards testing.
The lift could be tested for various issues.
1) Usability:
- whether it can be entered, exited easily
- is the door height appropriate.
- is there enough of space in the lift to accomodate the people as described in its requirements. ex: the lift is designed for 5 ppl & the space in the lift is just enough for 3 ppl to squeeze in.
- are the buttons to present & at visible place.
- How easy is it to operate the lift. etc
2) Functionality:
- Does the lift move on to the right floor. ex. if a person presses 2nd floor he should land on the 2nd floor not on the 4th.
- What speed is the lift moving at.
- Is the landing, taking off appropriate.
- Does it land at the right floor when a lift is called.
- Does it take the weight as per it is designed.
- Does it move as sequenced. ie if a call is made to the lift from the 5th floor while the lift is on the 3rd floor & is already moving downwards towards ground. If the lift would go down or up.
1.Capacity of lift
2.Height of lift
3,Width of lift
4.Security provided(red indicator,alarm)
5.Name of the company.
6.Space provided
7.Number exceeds than specified what security is provided
8.Wheather it comes to ground floor,top floor
9. programming provided by using PLC(top-down or can again come down)
10.If it is empty.
Capacity of the lift
usability (whether its easy to operate or not)
Functionality( whether it functions properly or not)
comfort (whether a person is comfortable in it or not)
height
weight
volume
time it takes to reach every floor
test for maximum capacity of the lift
test for more than max capacity
check the working in case of a power failure

Test cases for Pen

2010-01-26T10:17:00.000-08:00

Dimension of the pen,

Color of the pen,

GUI testing: logo of the pen maker,

Load testing

Total length that pen can write,

Strength of the nib,

Usability testing: grip of the pen.

Against the surface it can write.

Hanger provided in the cap,

Integration testing: body of the pen should perfectly fit with the cap of the pen,

Ink in the pen, at what temp does the ink get blocked.
Size of the nib like 0.5mm/0.6mm

Load test: when pen is pressed hard against the hard surface then refill should not come out of the pen from the backside.
check the look appearnce of the pen
check the cap of the pen
check the tip of the pen
Remove the pen body
it should be slick.
it should not be too large.
it should not be too small.
it should not have sharp edges.
it should be light
it should be strong.
it should have protection from ink pour out.
Ink colour should be dark
ballpoint should be strong so it should not break if pen strikes with hard surface.
it should have cap.
pen ink should not contain harmfull chemical.
Ink should not dry if pen is not used for long time.
User inter face :
1. Check look of the pen
2. Check Pen colour As per specification
3. Check whether cap is presented
4. Check whether pen is ball or ink as per specification
5. Check pen size as per specification

functional :
1. Check whether pen is writing
2. check whether pen z writing as per specification (.5,.6)
3. Check whether pen is writing only on papers or something as per specifications

Performence:

Check whether pen is writing in any climate
Check how much of time pen able to write continuosly with out rest on same way

Recovery

1. If pen is fall down then check whether pen able to write
To check the pen company
to check the pen type
to check the pen cap is present or not
to check the pen ink is filled or not
to check the pen writing or not
to check the ink color i.e black ro blue
to check the pen color
to check weather the pen is used to write all types of papers or not
to check the ink capacity of the pen
to check the pen product by fiber or plastic
Functional test cases (here we test the functionality of pen e.g. writing in flow or not etc.)
User-Interface test caes ( look n feel of pen e.g. cap facility, easy to hold, should be attractive etc.)
Stress Testing ( check the temperature dependency e.g can it work if temp is high or low etc.)
Performance Testing
Type of pen (ink,ball,dot etc.).
Able to write (bold/thin)
Grip of the in hand (how comforting is it to hold and write with it?)
Type of ink required (ink,gel, fluid, refillable??)
Color of the ink (red, black etc.).
Does it have a cap to protect the tip of the pen.
Does it have a pocket holding gripe for better carriage.
Kind of surface it can be used upon (hard,soft,glass, etc)
For how long can the pen be able to write non stop
Does the ink leaks in hot conditions or it seizes to flow in cold conditions
What type of body does the pen have (sleek,thick,etc.)
Is the pen branded?
I will intentionaly throw the pen down on floor..to check how much brittle it is ,is it broke down or not.

to check weather the pen is used to write all types of papers or not

to check the ink capacity of the pen

to check the pen product by fiber or plastic

Test cases for Calculator

2010-01-26T10:11:00.000-08:00

1 Check for the visibiltiy of all buttons (0-9, Backspace, CE, C, M+, MS, MR,MC,1/x,sqrt, .,%, +,-,*,/,=,+/-,
All buttons must be visible
2 Check addition button in calcultor
Click on button '2' then click on addition(+) button press '3' then click on Equal (=) button.
It must display 5.
3 Check substraction button.
Click '6' then click on Substraction(-) button press '3' then click on Equal (=) button.
It must display 3.
Click '3' then click on Substraction(-) button press '6' then Click on Equal(=) button.
It must display -3.
4 Check Multiply(*) button
Click '3' then click on Multiply(*) button press '3' then Click on Equal(=) button.It must display multiplication result as 9.
5 Check Division(/) button.
Click '6' then click on Division(/) button press '2' then Click on Equal(=) button.
It must display division result as 3.
Click '6' then click on Division(/) button press '0' then Click on Equal(=) button.
It must display Error messeage as "Cannot divide by Zero".

6 Check 1/x button function.
Click on '2' then press 1/x button then click on Equal(=) button
It must display "0.5" as rusult because 1 divide by 2 it must display 0.5

Click on '1/x' directly
It must show error message as Cannot divide by zero because it takes 0 as a x value.

7 Check "%" button Function.
check 500*10 then click on "%" button.
It must display 10% value of 500 i.e 50.

8 Check "CE" button functionality
Click '4' and click on "+" button then Click on '2' and then click on CE button
It must Clear the last value we enter so it must clear '2' and if we enter '3' and click on Equal(=) button it must display 7.

9 Check "C" button Functionality.
Click '4' and click on "+" button then Click on '2' and then click on "C" button. It must clear all values.

10 Check MS Button functionality
Click on '4' then click on MS button
It must store '4' in memory and display M as flag in left hand corner label.

11 Check MR Button functionality
Check Flag for Memory button if it shows 'M' then click on MR button.
It must show the memory value.

12 Check MC Button functionality
Click on MC button.
It must clear the value of memory. And Clear the label Flag 'M' to blank.

13 Check M+ Button functionality
Click on '4' then click on MS button then click on '5' and press M+ button.
It must display '9' as result when we click on MR button because it must add the current value '5' into the memory value. i.e '9'.

14 Check Backspace button functionality.
Enter '123456' in calculator and click on backspace button.
It must clear last value enter i.e. 6'

15 Check status of calulator
It must display '0' by default when we open a calulator.

Linux Interview Questions For software testers

2010-01-26T10:06:00.000-08:00

1. Q. How do you list files in a directory?
A. ls - list directory contents
ls ï¿½l (-l use a long listing format)

2. Q. How do you list all files in a directory, including the hidden files?
A. ls -a (-a, do not hide entries starting with .)

3. Q. How do you find out all processes that are currently running?
A. ps -f (-f does full-format listing.)

4. Q. How do you find out the processes that are currently running or a particular user?
A. ps -au Myname (-u by effective user ID (supports names)) (a - all users)

5. Q. How do you kill a process?
A. kill -9 8 (process_id 8) or kill -9 %7 (job number 7)
kill -9 -1 (Kill all processes you can kill.)
killall - kill processes by name most (useful - killall java)

6. Q. What would you use to view contents of the file?
A. less filename
cat filename
pg filename
pr filename
more filename
most useful is command: tail file_name - you can see the end of the log file.

7. Q. What would you use to edit contents of the file?
A. vi screen editor or jedit, nedit or ex line editor

8. Q. What would you use to view contents of a large error log file?
A. tail -10 file_name ( last 10 rows)

9. Q. How do you log in to a remote Unix box?
A. Using telnet server_name or ssh -l ( ssh - OpenSSH SSH client (remote login program))

10.Q. How do you get help on a UNIX terminal?
A. man command_name
info command_name (more information)

11.Q. How do you list contents of a directory including all of its
subdirectories, providing full details and sorted by modification time?
A. ls -lac
-a all entries
-c by time

12.Q. How do you create a symbolic link to a file (give some reasons of doing so)?
A. ln /../file1 Link_name
Links create pointers to the actual files, without duplicating the contents of
the files. That is, a link is a way of providing another name to the same file.
There are two types of links to a file:Hard link, Symbolic (or soft) link;

13.Q. What is a filesystem?
A. Sum of all directories called file system.
A file system is the primary means of file storage in UNIX.
File systems are made of inodes and superblocks.

14.Q. How do you get its usage (a filesystem)?
A. By storing and manipulate files.

15.Q. How do you check the sizes of all usersï¿½ home directories (one command)?
A. du -s
df

The du command summarizes disk usage by directory. It recurses through all subdirectories and shows disk usage by each subdirectory with a final total at the end.

Q. in current directory
A. ls -ps (p- directory; s - size)

16.Q. How do you check for processes started by user 'pat'?

A. ps -fu pat (-f -full_format u -user_name )

17.Q. How do you start a job on background?

A. bg %4 (job 4)

18 Q. What utility would you use to replace a string '2001' for '2002' in a text file?

A. Grep, Kde( works on Linux and Unix)

19. Q. What utility would you use to cut off the first column in a text file?
A. awk, kde

20. Q. How to copy file into directory?
A. cp /tmp/file_name . (dot mean in the current directory)

21. Q. How to remove directory with files?
A. rm -rf directory_name

22. Q. What is the difference between internal and external commands?
A. Internal commands are stored in the; same level as the operating system while external
commands are stored on the hard disk among the other utility programs.

23. Q. List the three main parts of an operating system command:
A. The three main parts are the command, options and arguments.

24 Q. What is the difference between an argument and an option (or switch)?
A. An argument is what the command should act on: it could be a filename,
directory or name. An option is specified when you want to request additional
information over and above the basic information each command supplies.

25. Q. What is the purpose of online help?
A. Online help provides information on each operating system command, the
syntax, the options, the arguments with descriptive information.

26. Q. Name two forms of security.
A. Two forms of security are Passwords and File Security with permissions specified.

27. Q. What command do you type to find help about the command who?
A. $ man who

28. Q. What is the difference between home directory and working directory?
A. Home directory is the directory you begin at when you log into the
system. Working directory can be anywhere on the system and it is where you are currently working.

29. Q. Which directory is closer to the top of the file system tree, parent directory or current directory?
A. The parent directory is above the current directory, so it is closer to the root or top of the file system.

30. Q. Given the following pathname:
$ /business/acctg/payable/supplier/april
a) If you were in the directory called acctg, what would be the relative
pathname name for the file called april?
b) What would be the absolute pathname for april?
A.
a) $ payable/supplier/april
b) $ /business/acctg/payable/supplier/april

31. Q. Suppose your directory had the following files:
help. 1 help.2 help.3 help.4 help.O1 help.O2
aid.O1 aid.O2 aid.O3 back. 1 back.2 back.3
a) What is the command to list all files ending in 2?
b) What is the command to list all files starting in aid?
c) What is the command to list all "help" files with one character extension?
A.
a) ls *2
b) ls aid.*
c) ls help.?

32. Q. What are two subtle differences in using the more and the pg commands?
A. With the more command you display another screenful by pressing
the spacebar, with pg you press the return key.
The more command returns you automatically to the UNIX
shell when completed, while pg waits until you press return.

33. Q. When is it better to use the more command rather than cat command?
A. It is sometimes better to use the more command when you are viewing
a file that will display over one screen.

34. Q. What are two functions the move mv command can carry out?
A. The mv command moves files and can also be used to rename a file or directory.

35. Q. Name two methods you could use to rename a file.
A. Two methods that could be used:
a. use the mv command
b. copy the file and give it a new name and then remove the original file if no longer needed.

36. The soccer league consists of boy and girl teams. The boy file names begin
with B, the girl teams begin with G. All of these files are in one directory
called "soccer", which is your current directory:
Bteam.abc Bteam.OOl Bteam.OO2 Bteam.OO4
Gteam.win Gteam.OOl Gteam.OO2 Gteam.OO3
Write the commands to do the following:
a) rename the file Bteam.abc to Bteam.OO3.
b) erase the file Gteam. win after you have viewed the contents of the file
c) make a directory for the boy team files called "boys", and one for the girl team files
called" girls"
d) move all the boy teams into the "boys" directory
e) move all the girl teams into the "girls" directory
f) make a new file called Gteam.OO4 that is identical to Gteam.OOl
g) make a new file called Gteam.OO5 that is identical to Bteam.OO2
A.
a) mv Bteam.abc Bteam.OO3.
b) cat Gteam.win -or- more Gteam.win
rm Gteam. win
c) mkdir boys
mkdir girls
d) mv Bteam* boys
e) mv Gteam* girls
f) cd girls
cp Gteam.OO1 Gteam.OO4
g) There are several ways to do this. Remember that we are currently in the directory
/soccer/girls.
cp ../boys/Bteam.OO2 Gteam.OO5
or
cd ../boys
cp Bteam.OO2 ../girls/Gteam.OO5

37. Q. Draw a picture of the final directory structure for the "soccer"
directory, showing all the files and directories.

38. Q. What metacharacter is used to do the following:
1.1 Move up one level higher in the directory tree structure
1.2 Specify all the files ending in .txt
1.3 Specify one character
1.4 Redirect input from a file
1.5 Redirect the output and append it to a file
A.
1. 1.1 double-dot or ..
1.2 asterisk or *
1.3 question or ?
1.4 double greater than sign: >>
1.5 the less than sign or <

39. Q. List all the files beginning with A
A. To list all the files beginning with A command: ls A*

40. Q. Which of the quoting or escape characters allows the dollar sign ($) to retain its special meaning?
A. The double quote (") allows the dollar sign ($) to retain its special meaning.
Both the backslash (\) and single quote (') would remove the special meaning of the dollar sign.

41. Q. What is a faster way to do the same command?
mv fileO.txt newdir
mv filel.txt newdir
mv file2.txt newdir
mv file3.txt newdir
A. A shortcut method would be: mv file?.txt newdir

42. Q. List two ways to create a new file:
A.
a. Copy a file to make a new file.
b. Use the output operator e.g. ls -l > newfile.txt

43. Q. What is the difference between > and >> operators?
A. The operator > either overwrites the existing file (WITHOUT WARNING) or creates a new file.
The operator >> either adds the new contents to the end of an existing file or creates a new file.

44. Write the command to do the following:
44.1 Redirect the output from the directory listing to a printer.
44.2 Add the file efg.txt to the end of the file abc.txt.
44.3 The file testdata feeds information into the file called program
44.4 Observe the contents of the file called xyz.txt using MORE.
44.5 Observe a directory listing that is four screens long.
A.
44.1 ls > lpr
44.2 cat efg.txt >> abc.txt
44.3 program < testdata
44.4 more < xyz.txt
44.5 ls > dirsave | more

45. Q. How do you estimate file space usage
A. Use du command (Summarize disk usage of each FILE, recursively for
directories.) Good to use arguments du -hs
(-h, --human-readable print sizes in human readable format (e.g., 1K 234M 2G)
(-s, --summarize display only a total for each argument)

46. Q. How can you see all mounted drives?
A. mount -l

47. Q. How can you find a path to the file in the system?
A. locate file_name (locate - list files in databases that match a pattern)

48. Q. What Linux HotKeys do you know?
A. Ctrl-Alt-F1 Exit to command prompt
Ctrl-Alt-F7 or F8 Takes you back to KDE desktop from command prompt
Crtl-Alt-Backspace Restart XWindows
Ctrl-Alt-D Show desktop

49. Q. What can you tell about the tar Command?
A. The tar program is an immensely useful archiving utility. It can combine an entire directory tree into one large file suitable for transferring or compression.

50. Q. What types of files you know?
A. Files come in eight flavors:
Normal files
Directories
Hard links
Symbolic links
Sockets
Named pipes
Character devices
Block devices

51. Q. How to copy files from on PC to another on the same network
A. Use the following command:scp yur_file you_login@your_IP
example: copy .conf file from your PC to alex computer-
scp /etc/X11/xorg.conf alex@10.0.10.169:

52. Q. Please describe information below:

-rw-rw-r-- 1 dotpc dotpc 102 Jul 18 2003 file.buf
drwxr-xr-x 9 dotpc dotpc 4096 Oct 21 09:34 bin
lrwxrwxrwx 1 dotpc dotpc 20 Mar 21 15:00 client -> client-2.9.5
drwxrwxr-x 11 dotpc dotpc 4096 Sep 2 2005 client-2.8.9
drwxrwxr-x 7 dotpc dotpc 4096 Dec 14 12:13 data
drwxr-xr-x 12 dotpc dotpc 4096 Oct 21 09:41 docs
drwxr-xr-x 5 dotpc dotpc 4096 Dec 7 14:22 etc
drwxr-xr-x 11 dotpc dotpc 4096 Mar 21 15:54 client-2.9.5
-rw-r--r-- 1 dotpc dotpc 644836 Mar 22 09:53 client-2.9.5.tar.gz

A. This is a result of command $ls -l
we have two files, 6 directories and one link to client-2.9.5 directory.
There is number of files in every directory, size and data of last change.

53. Q. If you would like to run two commands in sequence what operators you can use?

A. ; or && the difference is:
if you separate commands with ; second command will be run automatically.
if you separate commands with && second command will be run only in the case
the first was run successfully.

54. Q. How you will uncompress the file?
A. Use tar command (The GNU version of the tar archiving utility):
tar -zxvf file_name.tar.gz

55. Q.How do you execute a program or script, my_script in your current directoty?
A. ./my_script

56. Q.How to find current time configuration in the file my_new.cfg
A. grep time my_new.cfg
Grep searches the named input files (or standard input if
no files are named, or the file name - is given) for lines
containing a match to the given pattern.

Q. What does grep() stand for?
A. General Regular Expression Parser.

57. Q. What does the top command display?
A. Top provides an ongoing look at processor activity in real
time. It displays a listing of the most CPU-intensive
tasks on the system, and can provide an interactive interÂ
face for manipulating processes. (q is to quit)

58. Q. How can you find configuration on linux?
A. by using /sin/ifconfig
If no arguments are given, ifconfig displays the status of the cur-
rently active interfaces. If a single interface argument is given, it displays the status of the given interface only; if a single -a argu-
ment is given, it displays the status of all interfaces, even those
that are down. Otherwise, it configures an interface.

59. Q. How to find difference in two configuration files on the same server?
A. Use diff command that is compare files line by line
diff -u /usr/home/my_project1/etc/ABC.conf /usr/home/my_project2/etc/ABC.conf

60. Q. What is the best way to see the end of a logfile.log file?
A. Use tail command - output the last part of files
tail -n file_name ( the last N lines, instead of the last 10 as default)

61. Q. Please write a loop for removing all files in the current directory that contains a word 'log'
A. for i in *log*; do rm $i; done

62. Question: How to switch to a previously used directory?
Answer: cd -

1. Q.How many VI editor modes do you know?
A.Three modes -
Command mode: letters or sequence of letters interactively command vi.
Insert mode: Text is inserted.
Command line mode: enter this mode by typing ":" and entry command line at the foot of the screen.

2. Q. How can you terminate VI session?
A.
Use command: ZZ that is save changes and quit.
Use command line: ":wq" that is write changes and quit.
Use command line: ":q!" to ignore changes and quit.

3. Q. How can you copy lines into the buffer in command mode?
A.
yy - copy a single line defined by current cursor position
3yy - copy 3 lines. Current line and two lines below it.

Software testing resume Sample 2

2010-01-26T10:05:00.000-08:00

MyNameXyz
Email : Mynamedtgfr@ghyun.com
Mobile : 00000 00000

Objective:

To seek a Professional career with an established organization in the realm of Test Engineer, looking for a long-term association where Individual skills, hard work and Honesty are recognized and conductive work culture is provided.

Professional Summary:

• Having Exposure in testing various Software applications.
• expertise in Manual Testing
• Capable of testing the functionality of different applications using Win Runner.
• Good knowledge in different types of Testing.
• Having good knowledge in SDLC, STLC.
• Involved in peer reviews and group previews,
• Knowledge in ISO standards, SEI - CMM levels.

Educational Qualification:

• B.C.A (Bachelor of Computers Applications) from Xyz University.

Technical Skills:

Testing Tools Win Runner, Test Director
Languages C, C++, HTML
Database Oracle8, SQL
Operating Systems DOS, Windows Family
MS-Suite: MS-Office

PROJECT HISTORY

Project # 1 (Duration Start date to End date)

Title : XyzProjectTitleCustomerSupport
Team Size : 1
Tools : Manual and Win Runner tool
Environment : C++, windows 2000/NT.

Project Description : This is online customer support tool. The main purpose of the tool is to build a quick communication between support team and online customer in order to address their queries. This application consists of Site Administrator, Agent login, Password reset and Password change. Site Administrator is to login to administrator mode and do the changes. Agent login procures

Involved in:
I
• Understanding the product using software requirement specification and the prototype model.
• Requirement analysis in co-ordination with development..
• Preparation of test cases (user interface function and cross triggering cases mapping).
• Updation of test cases based on review comments.
• Test case execution in terms of sanity system performance regression and user interface.
• Bug reporting and tracking.
• Participating in team meetings and peer to peer reviews.

Project # 2 (Duration Start Date & Year to End Date & Year)

Title : Xyz Medical Kit Vgtyhj
Role : Test Engineer
Team Size : 3
Tools : Manual
Environment : Win2k, DHML, Java scrip, ASP, MS-SQL server IIS

Project Description : This project consists of online appointment with the doctor, details of the patient and his/her registration with the Hospital, patient problems/symptoms, characteristics, past history, family history, drug allergies etc. Patients related images like x-ray, scanning reports could be viewed in this. This project will be help full to the doctor for viewing the detail information of the patient and for the patients it will help to get contact to the doctor easily with out waste of their time.

In a team of 3, involved in –
• Preparation of Acceptance Test Cases, Functional Test Cases.
• Testing the application.
• Tracking the defects using defect-tracking system.
• Filling the work tracker regarding the work I had done.
• Involved in review meetings.

(Signature )

Software testing Resume sample 1

2010-01-26T10:03:00.000-08:00

MyNameXYZ

Experience Summary
• 1.5 Years of experience in Software Testing currently working as a Test engineer for XYZ , Ltd, XYZ.
• Experienced in Test cases development using Excel sheet and Test Director.
• Experienced in Execution of Test Cases and Preparation of Test Data Manually.
• Experienced in all types of Test Documentation: Test Scenarios, Test Cases etc. (both
manual and automated).
• Well acquainted with Software Development Life Cycle, Testing Life Cycle, Concepts
and Methodologies like Integration testing, Regression testing, System testing,
Acceptance testing, Dynamic, Static, Security, Load and Performance of testing.
• Executed the Scripts features like Data Driven, Database Checks, GUI checks, and
Batch using Win Runner.
• Ensure the successful delivery of a solution according to business requirements on
time, within the budget, and to the appropriate quality bar.
• Communicates with customers and offshore team members effectively.
• Experienced in Testing on Linux .
• Excellent Team Player possessing Good Communication and Interpersonal Skills.

Work Experience

• Working as a Testing Engineer for XYZ.,Ltd

Educational Qualifications

• B.Tech from XYZ June-2000, Xyz

Technical Qualifications:

Testing Tools : Win Runner, QTP, Load Runner, Test Director.
Languages : C, C++
Packages : VB
Database : Oracle, MySql, MS Access2000.
Operating System : Windows 9X/NT/2000
Project Experience:

Project#1

Title : MyProjectXyz
Domain : NetWorking Logs
Technologies : Java,C,C++, MySql, Tomcat, CGI Server
Operating System : Linux(Cent OS)
Role : Test Engineer
Team Size : 3

Description:
This is an integrated tool of LogQuest VF, LogCenter, WebQuest, FireQuest and OLAP Viewer. The purpose of the XYZ is to analyze the different kind of LogFiles and give the valuable information about the logfiles to the users.
This is a Tool . applies an easily farsighted log of a server and network equipment that puts a singularly existence and non-existence in a brush kind among the high-capacity farsighted log sword, which works as the sword. It consists of Client means the local method of verifying a log file, where a log file is stored on your computer and then analyzed.
The is collecting logs from network devices like switch, router, firewall, VPN and systems(Unix, Linux, Windows.LogCenter Agent will used for collect Windows event logs, system web logs and other application logs.Collected logs by LogCenter will used by system administrator, security mananger commonly for find out system vulnerability,hacking indications thourgh using User can search, make reports with specific conditions.
Responsibilities:
• Understanding the client requirements and Functionalities
• Installing LogQuest VF,LogCenter,WebQuest,FireQuest on Linux
• Installing Tomcat on Linux
• Testing All the Innerbus Products using with Linux
• Prepared the Test Cases by covering the entire product functionality
• Updating the test cases to the latest enhancements/requirements of the tool
• Testing of the configuration Tool involves the preparation of the Test Cases for business configuration, This covers the different features of the tool.
• Reported the bugs to the bug tracking system and prepared the bug reports
• Bug fix testing was done on different releases of the tool.
• Conducted various types of testing like Functionality Testing, Data Integrity Testing, GUI
Testing, Regression Testing, System Testing and Testing of Installation.
• Extensively performed Manual testing process to ensure the quality of the software

Project # 2
Title : MyProjectXyz
Environment : Java, Oracle 8i, Windows NT
Tools Used : Win Runner, Test Director
Duration : 7 Months
Team size : 2
Description:
The project is being developed for automation of various material management activities performed Account Payable is the process of preparing and entering the source documents like Supplier invoices, credit Notes and Employee expense reports require for payment of goods and services purchased from suppliers external to the organization. The Internal requisition is a system that has been implemented to help, organize and manage inventory. All orders of inventory from the stores and procurement center will now be done via Internal Requisitions. Invoices module used for complete billing and receipting information details like creating invoices, creating the Credit
Responsibilities:
• Designed Test cases for various modules using Test Director.
• Participated in Peer Review of Test Cases.
• Conducted Functional, Regression and System Testing for Various Modules.
• Reported and tracked the bugs using Test Cases.

( Signature )

Mercury LoadRunner FAQ

2010-01-26T10:01:00.000-08:00

1. What is load testing?
Load testing is to test that if the application works fine with the loads that result from large number of simultaneous users, transactions and to determine weather it can handle peak usage periods.

2. What is Performance testing?
Timing for both read and update transactions should be gathered to determine whether system functions are being performed in an acceptable timeframe. This should be done standalone and then in a multi user environment to determine the effect of multiple transactions on the timing of a single transaction.

3. What is LoadRunner?
LoadRunner works by creating virtual users who take the place of real users operating client software, such as sending requests using the HTTP protocol to IIS or Apache web servers. Requests from many virtual user clients are generated by Load Generators in order to create a load on various servers under test
These load generator agents are started and stopped by Mercury's Controller program. The Controller controls load test runs based on Scenarios invoking compiled Scripts and associated Run-time Settings.
Scripts are crafted using Mercury's "Virtual user script Generator" (named "V U Gen"), It generates C-language script code to be executed by virtual users by capturing network traffic between Internet application clients and servers.
With Java clients, VuGen captures calls by hooking within the client JVM. During runs, the status of each machine is monitored by the Controller.
At the end of each run, the Controller combines its monitoring logs with logs obtained from load generators, and makes them available to the "Analysis" program, which can then create run result reports and graphs for Microsoft Word, Crystal Reports, or an HTML webpage browser.

Each HTML report page generated by Analysis includes a link to results in a text file which Microsoft Excel can open to perform additional analysis.
Errors during each run are stored in a database file which can be read by Microsoft Access.

4. What is Virtual Users?
Unlike a WinRunner workstation which emulates a single user's use of a client, LoadRunner can emulate thousands of Virtual Users.
Load generators are controlled by VuGen scripts which issue non-GUI API calls using the same protocols as the client under test. But WinRunner GUI Vusers emulate keystrokes, mouse clicks, and other User Interface actions on the client being tested.
Only one GUI user can run from a machine unless LoadRunner Terminal Services Manager manages remote machines with Terminal Server Agent enabled and logged into a Terminal Services Client session.
During run-time, threadedvusers share a common memory pool.
So threading supports more Vusers per load generator.
The Status of Vusers on all load generators start from "Running", then go to "Ready" after going through the init section of the script. Vusers are "Finished" in passed or failed end status. Vusers are automatically "Stopped" when the Load Generator is overloaded.
To use Web Services Monitors for SOAP and XML, a separate license is needed, and vUsers require the Web Services add-in installed with Feature Pack (FP1).
No additional license is needed for standard web (HTTP) server monitors Apache, IIS, and Netscape.

5. Using Windows Remote Desktop Connection
To keep Windows Remote Desktop Connection sessions from timing out during a test, the Terminal Services on each machine should be configured as follows:
1. Click Start, point to Programs (or Control Panel), Administrative Tools and choose Terminal Services
2. Configuration.
3. Open the Connections folder in tree by clicking it once.
4. Right-click RDP-Tcp and select Properties.
5. Click the Sessions tab.
6. Make sure "Override user settings" is checked.
7. Set Idle session limit to the maximum of 2 days instead of the default 2 hours.
8. Click Apply.
9. Click OK to confirm message "Configuration changes have been made to the system registry; however, the user session now active on the RDP-Tcp connection will not be changed."
6. Explain the Load testing process? Version 7.2
Step 1: Planning the test. Here, we develop a clearly defined test plan to ensure the test scenarios we develop will accomplish load-testing objectives.
Step 2: Creating Vusers. Here, we create Vuser scripts that contain tasks performed by each Vuser, tasks performed by Vusers as a whole, and tasks measured as transactions.
Step 3: Creating the scenario. A scenario describes the events that occur during a testing session. It includes a list of machines, scripts, and Vusers that run during the scenario. We create scenarios using LoadRunner Controller. We can create manual scenarios as well as goal-oriented scenarios. In manual scenarios, we define the number of Vusers, the load generator machines, and percentage of Vusers to be assigned to each script. For web tests, we may create a goal-oriented scenario where we define the goal that our test has to achieve. LoadRunner automatically builds a scenario for us.
Step 4: Running the scenario. We emulate load on the server by instructing multiple Vusers to perform tasks simultaneously. Before the testing, we set the scenario configuration and scheduling. We can run the entire scenario, Vuser groups, or individual Vusers.
Step 5: Monitoring the scenario. We monitor scenario execution using the LoadRunner online runtime, transaction, system resource, Web resource, Web server resource, Web application server resource, database server resource, network delay, streaming media resource, firewall server resource, ERP server resource, and Java performance monitors.
Step 6: Analyzing test results. During scenario execution, LoadRunner records the performance of the application under different loads. We use LoadRunner’s graphs and reports to analyze the application’s performance.

7. When do you do load and performance Testing?
We perform load testing once we are done with interface (GUI) testing. Modern system architectures are large and complex. Whereas single user testing primarily on functionality and user interface of a system component, application testing focuses on performance and reliability of an entire system. For example, a typical application-testing scenario might depict 1000 users logging in simultaneously to a system. This gives rise to issues such as what is the response time of the system, does it crash, will it go with different software applications and platforms, can it hold so many hundreds and thousands of users, etc. This is when we set do load and performance testing.

8. What are the components of LoadRunner?
The components of LoadRunner are The Virtual User Generator, Controller, and the Agent process, LoadRunner Analysis and Monitoring, LoadRunner Books Online.

9. What Component of LoadRunner would you use to record a Script?
The Virtual User Generator (VuGen) component is used to record a script. It enables you to develop Vuser scripts for a variety of application types and communication protocols.

10. When do you do load and performance Testing?
We perform load testing once we are done with interface (GUI) testing. Modern system architectures are large and complex. Whereas single user testing primarily on functionality and user interface of a system component, application testing focuses on performance and reliability of an entire system. For example, a typical application-testing scenario might depict 1000 users logging in simultaneously to a system. This gives rise to issues such as what is the response time of the system, does it crash, will it go with different software applications and platforms, can it hold so many hundreds and thousands of users, etc. This is when we set do load and performance testing.

11. What are the components of LoadRunner?
The components of LoadRunner are The Virtual User Generator, Controller, and the Agent process, LoadRunner Analysis and Monitoring, LoadRunner Books Online. What Component of LoadRunner would you use to record a Script? - The Virtual User Generator (VuGen) component is used to record a script. It enables you to develop Vuser scripts for a variety of application types and communication protocols.

12. What Component of LoadRunner would you use to play Back the script in multi user mode?
The Controller component is used to playback the script in multi-user mode. This is done during a scenario run where a vuser script is executed by a number of vusers in a group.

13. What is a rendezvous point?
You insert rendezvous points into Vuser scripts to emulate heavy user load on the server. Rendezvous points instruct Vusers to wait during test execution for multiple Vusers to arrive at a certain point, in order that they may simultaneously perform a task. For example, to emulate peak load on the bank server, you can insert a rendezvous point instructing 100 Vusers to deposit cash into their accounts at the same time.

14. What is a rendezvous point?
A scenario defines the events that occur during each testing session. For example, a scenario defines and controls the number of users to emulate, the actions to be performed, and the machines on which the virtual users run their emulations.
15. Explain the recording mode for web Vuser script?
We use VuGen to develop a Vuser script by recording a user performing typical business processes on a client application. VuGen creates the script by recording the activity between the client and the server. For example, in web based applications, VuGen monitors the client end of the database and traces all the requests sent to, and received from, the database server. We use VuGen to: Monitor the communication between the application and the server; Generate the required function calls; and Insert the generated function calls into a Vuser script.

16. Why do you create parameters?
Parameters are like script variables. They are used to vary input to the server and to emulate real users. Different sets of data are sent to the server each time the script is run. Better simulate the usage model for more accurate testing from the Controller; one script can emulate many different users on the system.

17. What is correlation? Explain the difference between automatic correlation and manual correlation?
Correlation is used to obtain data which are unique for each run of the script and which are generated by nested queries. Correlation provides the value to avoid errors arising out of duplicate values and also optimizing the code (to avoid nested queries). Automatic correlation is where we set some rules for correlation. It can be application server specific. Here values are replaced by data which are created by these rules. In manual correlation, the value we want to correlate is scanned and create correlation is used to correlate.

18. How do you find out where correlation is required?
Two ways: First we can scan for correlations, and see the list of values which can be correlated. From this we can pick a value to be correlated. Secondly, we can record two scripts and compare them. We can look up the difference file to see for the values which needed to be correlated.

19. Where do you set automatic correlation options?
Automatic correlation from web point of view can be set in recording options and correlation tab. Here we can enable correlation for the entire script and choose either issue online messages or offline actions, where we can define rules for that correlation. Automatic correlation for database can be done using show output window and scan for correlation and picking the correlate query tab and choose which query value we want to correlate. If we know the specific value to be correlated, we just do create correlation for the value and specify how the value to be created.

20. What is a function to capture dynamic values in the web Vuser script?
Web_reg_save_param function saves dynamic data information to a parameter.

21. VuGen Recording and Scripting?
LoadRunner script code obtained from recording in the ANSI C language syntax, represented by icons in icon view until you click Script View.
22. What is Scenarios ?
Scenarios encapsulate the Vuser Groups and scripts to be executed on load generators at run-time.
Manual scenarios can distribute the total number of Vusers among scripts based on the analyst-specified percentage (evenly among load generators).
Goal Oriented scenarios are automatically created based on a specified transaction response time or number of hits/transactions-per-second (TPS). Test analysts specify the % of Target among scripts.

23. What are the typical settings for each type of run scenario ?

24. When do you disable log in Virtual User Generator, When do you choose standard and extended logs?
Once we debug our script and verify that it is functional, we can enable logging for errors only. When we add a script to a scenario, logging is automatically disabled. Standard Log Option: When you select Standard log, it creates a standard log of functions and messages sent during script execution to use for debugging. Disable this option for large load testing scenarios. When you copy a script to a scenario, logging is automatically disabled Extended Log Option: Select extended log to create an extended log, including warnings and other messages. Disable this option for large load testing scenarios. When you copy a script to a scenario, logging is automatically disabled. We can specify which additional information should be added to the extended log using the Extended log options.

25. How do you debug a LoadRunner script?
VuGen contains two options to help debug Vuser scripts-the Run Step by Step command and breakpoints. The Debug settings in the Options dialog box allow us to determine the extent of the trace to be performed during scenario execution. The debug information is written to the Output window. We can manually set the message class within your script using the lr_set_debug_message function. This is useful if we want to receive debug information about a small section of the script only.

26. How do you write user defined functions in LR?
Before we create the User Defined functions we need to create the external library (DLL) with the function. We add this library to VuGen bin directory. Once the library is added then we assign user defined function as a parameter. The function should have the following format: __declspec (dllexport) char* (char*, char*)

27. What are the changes you can make in run-time settings?
The Run Time Settings that we make are:
1. Pacing - It has iteration count.
2. Log - Under this we have Disable Logging Standard Log and
3. Extended Think Time - In think time we have two options like Ignore think time and Replay think time.
4. General - Under general tab we can set the vusers as process or as multithreading and whether each step as a transaction.
28. Where do you set Iteration for Vuser testing?
We set Iterations in the Run Time Settings of the VuGen. The navigation for this is Run time settings, Pacing tab, set number of iterations.

29. How do you perform functional testing under load?
Functionality under load can be tested by running several Vusers concurrently. By increasing the amount of Vusers, we can determine how much load the server can sustain.

30. Using network drive mappings
If several load generators need to access the same physical files, rather than having to remember to copy the files each time they change, each load generator can reference a common folder using a mapped drive. But since drive mappings are associated with a specific user:
1. Logon the load generator as the user the load generator will use
2. Open Windows Explorer and under Tools select Map a Network Drive and create a drive. It saves time and hassle to have consistent drive letters across load generators, so some organizations reserver certain drive letters for specific locations.
3. Open the LoadRunner service within Services (accessed from Control Panel, Administrative Tasks),
4. Click the "Login" tab.
5. Specify the username and password the load generator service will use. (A dot appears in front of the username if the userid is for the local domain).
6. Stop and start the service again.

31. What is Ramp up? How do you set this?
This option is used to gradually increase the amount of Vusers/load on the server. An initial value is set and a value to wait between intervals can be specified. To set Ramp Up, go to ‘Scenario Scheduling Options’

32. What is the advantage of running the Vuser as thread?
VuGen provides the facility to use multithreading. This enables more Vusers to be run pergenerator. If the Vuser is run as a process, the same driver program is loaded into memory for each Vuser, thus taking up a large amount of memory. This limits the number of Vusers that can be run on a single generator. If the Vuser is run as a thread, only one instance of the driver program is loaded into memory for the given number of Vusers (say 100). Each thread shares the memory of the parent driver program, thus enabling more Vusers to be run per generator.

33. If you want to stop the execution of your script on error, how do you do that?
The lr_abort function aborts the execution of a Vuser script. It instructs the Vuser to stop executing the Actions section, execute the vuser_end section and end the execution. This function is useful when you need to manually abort a script execution as a result of a specific error condition. When you end a script using this function, the Vuser is assigned the status "Stopped". For this to take effect, we have to first uncheck the Continue on error option in Run-Time Settings.

34. What is the relation between Response Time and Throughput?
The Throughput graph shows the amount of data in bytes that the Vusers received from the server in a second. When we compare this with the transaction response time, we will notice that as throughput decreased, the response time also decreased. Similarly, the peak throughput and highest response time would occur approximately at the same time.
35. Explain the Configuration of your systems?
The configuration of our systems refers to that of the client machines on which we run the Vusers. The configuration of any client machine includes its hardware settings, memory, operating system, software applications, development tools, etc. This system component configuration should match with the overall system configuration that would include the network infrastructure, the web server, the database server, and any other components that go with this larger system so as to achieve the load testing objectives.

36. How do you identify the performance bottlenecks?
Performance Bottlenecks can be detected by using monitors. These monitors might be application server monitors, web server monitors, database server monitors and network monitors. They help in finding out the troubled area in our scenario which causes increased response time. The measurements made are usually performance response time, throughput, hits/sec, network delay graphs, etc.

37. If web server, database and Network are all fine where could be the problem?
The problem could be in the system itself or in the application server or in the code written for the application.

38. How did you find web server related issues?
Using Web resource monitors we can find the performance of web servers. Using these monitors we can analyze throughput on the web server, number of hits per second that occurred during scenario, the number of http responses per second, the number of downloaded pages per second.

39. How did you find database related issues?
By running Database monitor and help of Data Resource Graph we can find database related issues. E.g. You can specify the resource you want to measure on before running the controller and than you can see database related issues .

40. What is the difference between Overlay graph and Correlate graph?
Overlay Graph: It overlay the content of two graphs that shares a common x-axis. Left Y-axis on the merged graph show’s the current graph’s value & Right Y-axis show the value of Y-axis of the graph that was merged. Correlate Graph: Plot the Y-axis of two graphs against each other. The active graph’s Y-axis becomes X-axis of merged graph. Y-axis of the graph that was merged becomes merged graph’s Y-axis.

41. How did you plan the Load? What are the Criteria?
Load test is planned to decide the number of users, what kind of machines we are going to use and from where they are run. It is based on 2 important documents, Task Distribution Diagram and Transaction profile. Task Distribution Diagram gives us the information on number of users for a particular transaction and the time of the load. The peak usage and off-usage are decided from this Diagram. Transaction profile gives us the information about the transactions name and their priority levels with regard to the scenario we are deciding.

42. What does vuser_init action contain?
Vuser_init action contains procedures to login to a server.

43. What does vuser_end action contain?
Vuser_end section contains log off procedures.
44. What is think time? How do you change the threshold?
Think time is the time that a real user waits between actions. Example: When a user receives data from a server, the user may wait several seconds to review the data before responding. This delay is known as the think time. Changing the Threshold: Threshold level is the level below which the recorded think time will be ignored. The default value is five (5) seconds. We can change the think time threshold in the Recording options of the Vugen.

45. What is the difference between standard log and extended log?
The standard log sends a subset of functions and messages sent during script execution to a log. The subset depends on the Vuser type Extended log sends a detailed script execution messages to the output log. This is mainly used during debugging when we want information about: Parameter substitution. Data returned by the server. Advanced trace.

46. What is lr_debug_message ?
The lr_debug_message function sends a debug message to the output log when the specified message class is set.

47. What is lr_output_message ?
The lr_output_message function sends notifications to the Controller Output window and the Vuser log file.

48. What is lr_error_message ?
The lr_error_message function sends an error message to the LoadRunner Output window.

49. What is lrd_stmt?
The lrd_stmt function associates a character string (usually a SQL statement) with a cursor. This function sets a SQL statement to be processed.
50. What is lrd_fetch?
The lrd_fetch function fetches the next row from the result set.

51. What is Throughput?
If the throughput scales upward as time progresses and the number of Vusers increase, this indicates that the bandwidth is sufficient. If the graph were to remain relatively flat as the number of Vusers increased, it would be reasonable to conclude that the bandwidth is constraining the volume of data delivered.

52. Types of Goals in Goal-Oriented Scenario
Load Runner provides you with five different types of goals in a goal oriented scenario:
1. The number of concurrent Vusers
2. The number of hits per second
3. The number of transactions per second
4. The number of pages per minute
The transaction response time that you want your scenario Analysis Scenario (Bottlenecks): In Running Vuser graph correlated with the response time graph you can see that as the number of Vusers increases, the average response time of the check itinerary transaction very gradually increases. In other words, the average response time steadily increases as the load increases. At 56 Vusers, there is a sudden, sharp increase in the average response time. We say that the test broke the server. That is the mean time before failure (MTBF). The response time clearly began to degrade when there were more than 56 Vusers running simultaneously.

53. What is correlation? Explain the difference between automatic correlation and manual correlation?
Correlation is used to obtain data which are unique for each run of the script and which are generated by nested queries. Correlation provides the value to avoid errors arising out of duplicate values and also optimizing the code (to avoid nested queries). Automatic correlation is where we set some rules for correlation. It can be application server specific. Here values are replaced by data which are created by these rules. In manual correlation, the value we want to correlate is scanned and create correlation is used to correlate.

54. Where do you set automatic correlation options?
Automatic correlation from web point of view, can be set in recording options and correlation tab. Here we can enable correlation for the entire script and choose either issue online messages or offline actions, where we can define rules for that correlation. Automatic correlation for database, can be done using show output window and scan for correlation and picking the correlate query tab and choose which query value we want to correlate. If we know the specific value to be correlated, we just do create correlation for the value and specify how the value to be created.

55. Where do you set automatic correlation options?
What is a function to capture dynamic values in the web vuser script? - Web_reg_save_param function saves dynamic data information to a parameter.

BugZilla Interview Questions

2010-01-26T10:00:00.000-08:00

1. What is Bugzilla?
Bugzilla is Defect Tracking Systems allow individual or groups of developers to keep track of outstanding bugs in their product effectively. Bugzilla is a open-source bug-tracking software.
Bugzilla offers superior performance on commodity hardware, better price (free!), more developer- friendly features (such as stored queries, email integration, and platform independence), improved scalability, open source code, greater flexibility, and superior ease-of-use.

2. What is Bugzilla's features?
• integrated, product-based granular security schema
• inter-bug dependencies and dependency graphing
• advanced reporting capabilities •
• a robust, stable RDBMS back-end
• extensive configurability •
• a very well-understood and well-thought-out natural bug resolution protocol
• email, XML, console, and HTTP APIs •
• available integration with automated software configuration management systems, including Perforce and CVS (through the Bugzilla email interface and checkin/checkout scripts)

3. why should you use Bugzilla?
Bugzilla can dramatically increase the productivity and accountability of individual employees by providing a documented workflow and positive feedback for good performance.

4. Bugzilla Components
• Administration of a bugzilla:
(editcomponents.cgi, editgroups.cgi, editkeywords.cgi, editparams.cgi, editproducts.cgi, editusers.cgi, editversions.cgi, and sanitycheck.cgi.)
• Bugzilla-General: (Creating/Changing Bugs, Creating, changing, and viewing bugs. enter_bug.cgi, post_bug.cgi, show_bug.cgi and process_bug.cgi.)
• The bugzilla documentation
• Email, Anything to do with email sent by Bugzilla. processmail
• The installation process of Bugzilla
• Query/Buglist, Anything to do with searching for bugs and viewing the buglists. query.cgi and buglist.cgi
• Reporting/Charting, Getting reports from Bugzilla. reports.cgi and duplicates.cgi
• User Accounts, Anything about managing a user account from the user's perspective. userprefs.cgi, saved queries, creating accounts, changing passwords, logging in, etc.
• User Interface, General issues having to do with the user interface cosmetics (not functionality) including cosmetic issues, HTML templates, etc.

5. How to create a Bugzilla Account?
1. Enter your "E-mail address" and "Real Name" (or whatever name you want to call yourself) in the spaces provided, then select the "Create Account" button.
2. Within moments, you should receive an email to the address you provided above, which contains your login name (generally the same as the email address), and a password you can use to access your account. This password is randomly generated, and should be changed at your nearest opportunity (we'll go into how to do it later).
3. Click the "Log In" link in the yellow area at the bottom of the page in your browser, then enter your "E-mail address" and "Password" you just received into the spaces provided, and select "Login".

6. How do I change my user name in Bugzilla??
You can't. However, the administrative account can, by simply opening your user account in editusers.cgi and changing the login name.

7. What is The Bugzilla Query Page?
The Bugzilla Query Page is the heart and soul of the Bugzilla user experience. It is the master interface where you can find any bug report, comment, or patch currently in the Bugzilla system.

The first thing you need to notice about the Bugzilla Query Page is that nearly every box you see on your screen has a hyperlink nearby, explaining what it is or what it does. Near the upper-left-hand corner of your browser window you should see the word "Status" underlined. Select it.

Here is a example that how to make a few successful queries to find out what there are in the Bugzilla bug-tracking system itself.
1. Ensure you are back on the "Bugzilla Query Page". Do nothing in the boxes marked "Status", "Resolution", "Platform", "OpSys", "Priority", or "Severity". The default query for "Status" is to find all bugs that are NEW, ASSIGNED, or REOPENED, which is what we want. If you don't select anything in the other 5 scrollboxes there, then you are saying that "any of these are OK"; we're not locking ourselves into only finding bugs on the "DEC" Platform, or "Windows 95" OpSys (Operating System).
2. Basically, selecting anything on the query page narrows your search down. Leaving stuff unselected, or text boxes unfilled, broadens your search.
You see the box immediately below the top six boxes that contains an "Email" text box, with the words "matching as", a drop-down selection box, then some checkboxes with "Assigned To" checked by default? This allows you to filter your search down based upon email address. Let's put my email address in there, and see what happens.
Type "yourname@gmail.com" in the top Email text box.
3. Let's narrow the search some more. Scroll down until you find the box with the word "Program" over the top of it. This is where we can narrow our search down to only specific products (software programs or product lines) in our Bugzilla database. Please notice the box is a scrollbox. Using the down arrow on the scrollbox, scroll down until you can see an entry called "Bugzilla". Select this entry.
4. Did you notice that some of the boxes to the right changed when you selected "Bugzilla"? Every Program (or Product) has different Versions, Components, and Target Milestones associated with it. A "Version" is the number of a software program.
5. OK, now let's select the "Bugzilla" component from its scrollbox. 6. Skip down the page a bit -- do you see the "submit query" button? Select it, and let's run this query!
7. Congratulations! You've completed your first Query.

8. What is about the Bug List page?
Change Columns: by selecting this link, you can show all kinds of information in the Bug List
Change several bugs at once: If you have sufficient rights to change all the bugs shown in the Bug List, you can mass-modify them. This is a big time-saver.
Send mail to bug owners: If you have many related bugs, you can request an update from every person who owns the bugs in the Bug List asking them the status.
Edit this query: If you didn't get exactly the results you were looking for, you can return to the Query page through this link and make small revisions to the query you just made so you get more accurate results.

9. How to Write a Useful Bug Report with Bugzilla
Useful bug reports are ones that get bugs fixed. A useful bug report normally has two qualities:
Reproducible. If an engineer can't see it or conclusively prove that it exists, the engineer will probably stamp it WORKSFORME or INVALID, and move on to the next bug. Every relevant detail you can provide helps.
Specific. The quicker the engineer can isolate the issue to a specific problem, the more likely it'll be expediently fixed. If you're crashing on a site, please take the time to isolate what on the page is triggering the crash, and include it as an HTML snippet in the bug report if possible. (Specific bugs have the added bonus of remaining relevant when an engineer actually gets to them; in a rapidly changing web, a bug report of "foo.com crashes my browser" becomes meaningless after the site experiences a half-dozen redesigns and hundreds of content changes.)

1. Go back to http://landfill.tequilarista.org/bugzilla-tip/ in your browser.
2. Select the Enter a new bug report link.
3. Select a product.
4. Now you should be at the "Enter Bug" form. The "reporter" should have been automatically filled out for you (or else Bugzilla prompted you to Log In again -- you did keep the email with your username and password, didn't you?).
5. Select a Component in the scrollbox.
6. Bugzilla should have made reasonable guesses, based upon your browser, for the "Platform" and "OS" drop-down boxes. If those are wrong, change them -- if you're on an SGI box running IRIX, we want to know!
7. Fill in the "Assigned To" box with the email address you provided earlier. This way you don't end up sending copies of your bug to lots of other people, since it's just a test bug.
8. Leave the "CC" text box blank. Fill in the "URL" box with "http://www.mozilla.org".
9. Enter "The Bugzilla Guide" in the Summary text box, and place any comments you have on this tutorial, or the Guide in general, into the Description box.

Voila! Select "Commit" and send in your bug report! Next we'll look at resolving bugs.

10. How to Enter your Useful Bug Report into Bugzilla
From the Bugzilla main page (http://bugzilla.mozilla.org), choose "Enter a new bug".
Select the product that you've found a bug in.
Now, fill out the form. Here's what it all means:
Where did you find the bug? --- which product,which product version,which component, which hardware platform ,which Operating System

How important is the bug? -- Severity

Who will be following up on the bug? -- Which engineer should be responsible for fixing this bug? Who else should receive e-mail updates on changes to this bug?

What else can you tell the engineer about the bug? -- On what URL did you discover this bug? How would you describe the bug, in approximately 60 or fewer characters?

11. How to manage a Bug Reports with Bugzilla
You should have a link to the bug you just created near the top of your page. It should say "Bug XXXX posted", with a link to the right saying "Back to BUG# XXXX". Select this link.
1.Scroll down a bit on the subsequent page, until you see the "Resolve bug, changing resolution to (dropdown box). Normally, you would "Accept bug (change status to ASSIGNED)", fix it, and then resolve. But in this case, we're going to short-circuit the process because this wasn't a real bug. Change the dropdown next to "Resolve Bug" to "INVALID", make sure the radio button is marked next to "Resolve Bug", then click "Commit".
2. Hey! It said it couldn't take the change in a big red box! That's right, you must specify a Comment in order to make this change. Select the "Back" button in your browser, add a Comment, then try Resolving the bug with INVALID status again. This time it should work.

12. Where can I find my user preferences?
Customized User Preferences offer tremendous versatility to your individual Bugzilla experience. Let's plunge into what you can do! The first step is to click the "Edit prefs" link at the footer of each page once you have logged in to Landfill.

13. What about Account Settings page?
On this page, you can change your basic Account Settings, including your password and full name. For security reasons,

14. What about Email Settings page?
Here you can reduce or increase the amount of email sent you from Bugzilla.

15. What about "Watching" Users functionality?
By entering user email names into the "Users to watch" text entry box, delineated by commas, you can watch bugs of other users. This powerful functionality enables seamless transitions as developers change projects, managers wish to get in touch with the issues faced by their direct reports, or users go on vacation.

16. What about Page Footer ?
By default, this page is quite barren. However, go explore the Query Page some more; you will find that you can store numerous queries on the server, so if you regularly run a particular query it is just a drop-down menu away. On this page of Preferences, if you have many stored queries you can elect to have them always one-click away!

17. How does Bugzilla stack up against other bug-tracking databases?
Still can't find any head-to-head comparisons of Bugzilla against other defect-tracking software.

18. Is Bugzilla web-based or do you have to have specific software or specific operating system on your machine?
It is web and e-mail based. You can edit bugs by sending specially formatted email to a properly configured Bugzilla, or control via the web.

19. Does Bugzilla allow the user to track multiple projects?
Absolutely! You can track up to a "soft-limit" of around 64 individual "Products", that can each be composed of as many "Components" as you want. Check the Administration section of the Bugzilla Guide for more information regarding setting up Products and Components.

20. If I am on many projects, and search for all bugs assigned to me, will Bugzilla list them for me and allow me to sort by project, severity etc?
Yes.

21. Does Bugzilla allow attachments (text, screenshots, urls etc)? If yes, are there any that are NOT allowed?
Yes. There are many specific MIME-types that are pre-defined by Bugzilla, but you may specify any arbitrary MIME-type you need when you upload the file. Since all attachments are stored in the database, however, I recommend storing large binary attachments elsewhere in the web server's file system and providing a hyperlink as a comment, or in the provided "URL" field in the bug report.

22. Does Bugzilla allow us to define our own priorities and levels? Do we have complete freedom to change the labels of fields and format of them, and the choice of acceptable values?
Yes. However, modifying some fields, notably those related to bug progression states, also require adjusting the program logic to compensate for the change. There is no GUI for adding fields to Bugzilla at this time.

23. Does Bugzilla provide any reporting features, metrics, graphs, etc?
Yes. Look at http://link.fyicenter.com/view.php?ID=919 for basic reporting facilities.
For more advanced reporting, I recommend hooking up a professional reporting package, such as Crystal Reports, and use ODBC to access the MySQL database. You can do a lot through the Query page of Bugzilla as well, but right now Advanced Reporting is much better accomplished through third-party utilities that can interface with the database directly.
Advanced Reporting is a Bugzilla 3.X proposed feature.

24. The index.html page doesn't show the footer. It's really annoying to have to go to the querypage just to check my "my bugs" link. How do I get a footer on static HTML pages?
It's possible to get the footer on the static index page using Server Side Includes (SSI). The trick to doing this is making sure that your web server is set up to allow SSI and specifically, the #exec directive. You should also rename index.html to index.shtml.
After you've done all that, you can add the following line to index.shtml:
< !--#exec cmd="/usr/bin/perl -e "require 'CGI.pl'; PutFooter();"" -->
This line will be replaced with the actual HTML for the footer when the page is requested, so you should put this line where you want the footer to appear.
Because this method depends on being able to use a #exec directive, and most ISP's will not allow that, there is an alternative method. You could have a small script (such as api.cgi) that basically looks like:
#!/usr/bonsaitools/bin/perl -w
require 'globals.pl';
if ($::FORM{sub} eq 'PutFooter') {
PutFooter();
} else {
die 'api.cgi was incorrectly called';
}
and then put this line in index.shtml.

25. Is there email notification and if so, what do you see when you get an email? Do you see bug number and title or is it only the number?
Email notification is user-configurable. The bug id and Topic of the bug report accompany each email notification, along with a list of the changes made.

26. Can email notification be set up to send to multiple people, some on the To List, CC List, BCC List etc?
Yes.

27. Can email notification be set up to send to multiple people, some on the To List, CC List, BCC List etc?
Yes.

28. If there is email notification, do users have to have any particular type of email application?
Bugzilla email is sent in plain text, the most compatible mail format on the planet.

29. If I just wanted to track certain bugs, as they go through life, can I set it up to alert me via email whenever that bug changes, whether it be owner, status or description etc.?
Yes. Place yourself in the "cc" field of the bug you wish to monitor. Then change your "Notify me of changes to" field in the Email Settings tab of the User Preferences screen in Bugzilla to the "Only those bugs which I am listed on the CC line" option.

30. Does Bugzilla allow data to be imported and exported? If I had outsiders write up a bug report using a MS Word bug template, could that template be imported into "matching" fields? If I wanted to take the results of a query and export that data to MS Excel, could I do that?
Mozilla allows data export through a custom DTD in XML format. It does not, however, export to specific formats other than the XML Mozilla DTD. Importing the data into Excel or any other application is left as an exercise for the reader.
If you create import filters to other applications from Mozilla's XML, please submit your modifications for inclusion in future Bugzilla distributions.
As for data import, any application can send data to Bugzilla through the HTTP protocol, or through Mozilla's XML API. However, it seems kind of silly to put another front-end in front of Bugzilla; it makes more sense to create a simplified bug submission form in HTML.

31. Has anyone converted Bugzilla to another language to be used in other countries? Is it localizable?
Currently, no.

32. Can a user create and save reports? Can they do this in Word format? Excel format?
Can a user create and save reports? Yes. Can they do this in Word format? No. Excel format? No.

33. Can a user re-run a report with a new project, same query?
Yes.

34. Can a user modify an existing report and then save it into another name?
You can save an unlimited number of queries in Bugzilla. You are free to modify them and rename them to your heart's desire.

35. Does Bugzilla have the ability to search by word, phrase, compound search?
You have no idea. Bugzilla's query interface, particularly with the advanced Boolean operators, is incredibly versatile.

36. Can the admin person establish separate group and individual user privileges?
Yes.

37. Does Bugzilla provide record locking when there is simultaneous access to the same bug? Does the second person get a notice that the bug is in use or how are they notified?
Bugzilla does not lock records. It provides mid-air collision detection, and offers the offending user a choice of options to deal with the conflict.

38. Are there any backup features provided?
MySQL, the database back-end for Bugzilla, allows hot-backup of data.

39. Can users be on the system while a backup is in progress?
Yes. However, commits to the database must wait until the tables are unlocked. Bugzilla databases are typically very small, and backups routinely take less than a minute.

40. Are there any security problems with Bugzilla?
The Bugzilla code has not undergone a complete security audit. It is recommended that you closely examine permissions on your Bugzilla installation, and follow the recommended security guidelines.

41. I don't like/want to use Procmail to hand mail off to bug_email.pl. What alternatives do I have?
You can call bug_email.pl directly from your aliases file, with an entry like this: bugzilla-daemon: "|/usr/local/bin/bugzilla/contrib/bug_email.pl"

42. How do I set up the email interface to submit/change bugs via email?
You can find an updated README.mailif file in the contrib/ directory of your Bugzilla distribution that walks you through the setup.

43. Bugzilla can be used with Oracle?
The current version does not have this capability.

44. Bugs are missing from queries, but exist in the database (and I can pull them up by specifying the bug ID). What's wrong?
You've almost certainly enabled the "shadow database", but for some reason it hasn't been updated for all your bugs. This is the database against which queries are run, so that really complex or slow queries won't lock up portions of the database for other users. You can turn off the shadow database in editparams.cgi. If you wish to continue using the shadow database, then as your "bugs" user run "./syncshadowdb -syncall" from the command line in the bugzilla installation directory to recreate your shadow database. After it finishes, be sure to check the params and make sure that "queryagainstshadowdb" is still turned on. The syncshadowdb program turns it off if it was on, and is supposed to turn it back on when completed; that way, if it crashes in the middle of recreating the database, it will stay off forever until someone turns it back on by hand. Apparently, it doesn't always do that yet.

45. I think my database might be corrupted, or contain invalid entries. What do I do?
Run the "sanity check" utility (./sanitycheck.cgi in the Bugzilla_home directory) from your web browser to see! If it finishes without errors, you're probably OK. If it doesn't come back OK (i.e. any red letters), there are certain things Bugzilla can recover from and certain things it can't. If it can't auto-recover, I hope you're familiar with mysqladmin commands or have installed another way to manage your database. Sanity Check, although it is a good basic check on your database integrity, by no means is a substitute for competent database administration and avoiding deletion of data. It is not exhaustive, and was created to do a basic check for the most common problems in Bugzilla databases.

46. I want to manually edit some entries in my database. How?
There is no facility in Bugzilla itself to do this. It's also generally not a smart thing to do if you don't know exactly what you're doing. However, if you understand SQL you can use the mysqladmin utility to manually insert, delete, and modify table information. Personally, I use "phpMyAdmin". You have to compile a PHP module with MySQL support to make it work, but it's very clean and easy to use.

47. I try to add myself as a user, but Bugzilla always tells me my password is wrong.
Certain version of MySQL (notably, 3.23.29 and 3.23.30) accidentally disabled the "crypt()" function. This prevented MySQL from storing encrypted passwords. Upgrade to the "3.23 stable" version of MySQL and you should be good to go.

48. I think I've set up MySQL permissions correctly, but bugzilla still can't connect.
Try running MySQL from its binary: "mysqld --skip-grant-tables". This will allow you to completely rule out grant tables as the cause of your frustration. However, I do not recommend you run it this way on a regular basis, unless you really want your web site defaced and your machine cracked.

49. How do I synchronize bug information among multiple different Bugzilla databases?
Well, you can synchronize or you can move bugs. Synchronization will only work one way -- you can create a read-only copy of the database at one site, and have it regularly updated at intervals from the main database.
MySQL has some synchronization features builtin to the latest releases. It would be great if someone looked into the possibilities there and provided a report to the newsgroup on how to effectively synchronize two Bugzilla installations.
If you simply need to transfer bugs from one Bugzilla to another, checkout the "move.pl" script in the Bugzilla distribution.

50. Why do I get bizarre errors when trying to submit data, particularly problems with "groupset"?
If you're sure your MySQL parameters are correct, you might want turn "strictvaluechecks" OFF in editparams.cgi. If you have "usebugsentry" set "On", you also cannot submit a bug as readable by more than one group with "strictvaluechecks" ON.

51. How come even after I delete bugs, the long descriptions show up?
This should only happen with Bugzilla 2.14 if you are using the "shadow database" feature, and your shadow database is out of sync. Try running syncshadowdb -syncall to make sure your shadow database is in synch with your primary database.

52. I can't upload anything into the database via the "Create Attachment" link. What am I doing wrong?
The most likely cause is a very old browser or a browser that is incompatible with file upload via POST. Download the latest Netscape, Microsoft, or Mozilla browser to handle uploads correctly.

53. How do I change a keyword in Bugzilla, once some bugs are using it?
In the Bugzilla administrator UI, edit the keyword and it will let you replace the old keyword name with a new one. This will cause a problem with the keyword cache. Run sanitycheck.cgi to fix it.

54. Bugzilla Database Basics
1. To connect to your database: bash#mysql-u root
2. To see all the "spreadsheets" (tables): mysql>show tables from bugs;
3. To see columns from table: mysql> show columns from table;
4. To see all the data in a table: mysql> select * from table;
5. others:
mysqlgt; select * from table where (column = "some info");
mysqlgt; select * from table where (column != "some info");
mysqlgt; show columns from bugs
(exceedingly long output truncated here)
| bug_status| enum('UNCONFIRMED','NEW','ASSIGNED','REOPENED','RESOLVED','VERIFIED'
mysqlgt; ALTER table bugs CHANGE bug_status bug_status

55. Step-by-step Install Bugzilla
Installation of bugzilla is pretty straightforward, particularly if your machine already has MySQL and the MySQL-related perl packages installed.

The software packages necessary for the proper running of bugzilla are:
1. MySQL database server and the mysql client (3.22.5 or greater)
2. Perl (5.004 or greater, 5.6.1 is recommended if you wish to use Bundle::Bugzilla)
3. DBI Perl module
4. Data::Dumper Perl module
5. Bundle::Mysql Perl module collection
6. TimeDate Perl module collection
7. GD perl module (1.8.3) (optional, for bug charting)
8. Chart::Base Perl module (0.99c) (optional, for bug charting)
9. DB_File Perl module (optional, for bug charting) 9. 10.The web server of your choice. Apache is recommended.
11.MIME::Parser Perl module (optional, for contrib/bug_email.pl interface)

You should untar the Bugzilla files into a directory that you're willing to make writable by the default web server user (probably "nobody"). You may decide to put the files off of the main web space for your web server or perhaps off of /usr/local with a symbolic link in the web space that points to the Bugzilla directory. At any rate, just dump all the files in the same place, and make sure you can access the files in that directory through your web server.

Once all the files are in a web accessible directory, make that directory writable by your webserver's user. This is a temporary step until you run the post-install checksetup.pl script, which locks down your installation.
Lastly, you'll need to set up a symbolic link to /usr/bonsaitools/bin/perl for the correct location of your perl executable (probably /usr/bin/perl). Otherwise you must hack all the .cgi files to change where they look for perl, or use The setperl.csh Utility, found in Useful Patches and Utilities for Bugzilla. I suggest using the symlink approach for future release compatability.
After you've gotten all the software installed and working you're ready to start preparing the database for its life as a the back end to a high quality bug tracker.
First, you'll want to fix MySQL permissions to allow access from Bugzilla. For the purpose of this Installation section, the Bugzilla username will be "bugs", and will have minimal permissions.
Next, we create the "bugs" user, and grant sufficient permissions for checksetup.pl, which we'll use later, to work its magic. This also restricts the "bugs" user to operations within a database called "bugs", and only allows the account to connect from "localhost". Modify it to reflect your setup if you will be connecting from another machine or as a different user.
Remember to set bugs_password to some unique password.

mysql > GRANT SELECT,INSERT,UPDATE,DELETE,INDEX,
ALTER,CREATE,DROP,REFERENCES ON bugs.* TO bugs@localhost IDENTIFIED BY
'bugs_password';
mysql> FLUSH PRIVILEGES;

Next, run the magic checksetup.pl script.
It will make sure Bugzilla files and directories have reasonable permissions, set up the data directory, and create all the MySQL tables.
bash# ./checksetup.pl
The first time you run it, it will create a file called localconfig.

What's localconfig for ?
This file contains a variety of settings you may need to tweak including how Bugzilla should connect to the MySQL database.

The connection settings include:
1. server's host: just use "localhost" if the MySQL server is local
2. database name: "bugs" if you're following these directions
3. MySQL username: "bugs" if you're following these directions
4. Password for the "bugs" MySQL account above

You should also install .htaccess files that the Apache webserver will use to restrict access to Bugzilla data files. Once you are happy with the settings, re-run checksetup.pl. On this second run, it will create the database and an administrator account for which you will be prompted to provide information. When logged into an administrator account once Bugzilla is running, if you go to the query page (off of the Bugzilla main menu), you'll find an "edit parameters" option that is filled with editable treats. Should everything work, you will have a nearly empty Bugzilla database and a newly-created localconfig file in your Bugzilla root directory.

The second time you run checksetup.pl, you should become the user your web server runs as, and that you ensure that you set the "webservergroup" parameter in localconfig to match the web server's group name, if any. I believe, for the next release of Bugzilla, this will be fixed so that Bugzilla supports a "webserveruser" parameter in localconfig as well.
Red Hat Bugzilla FAQ

1. What is it?
Bugzilla is a bug tracking system developed at mozilla.org. It was originally used to track the bugs in the Mozilla web browser. Red Hat has customized it to track bugs in our Linux products.

2. How do I enter a bug?
To enter a bug, select Enter a new bug from the main bugzilla page. This will take you to a product selection screen.
From this screen you select the product that you wish to enter a bug for, by selecting the hightlighted product name. This will take you to a bug entry screen.
Example: Red Hat Linux
From the bug entry screen, you need to select the version of the product that you are entering a bug on, along with which component of the product that is having a problem. Components are based on the source rpm that the offending binary rpm is derived from. To find the proper component do you can use one of two common methods:
$ rpm -qip 'binary rpm name'
This should work fine if you already know which rpm the failing binary belongs to.
$ rpm -qif /failing/binary
This will tell you which rpm the binary belongs to and also the source rpm.
After using one of the above methods look for a line that says Source RPM: This is the name of the component you should choose from the list of components in Bugzilla. If still unsure of which component to choose or you are filing a bug to request a new component be added to Bugzilla itself, then choose distribution.
Example: 5.2 and acm
Next, select the Severity of your bug.
Example: Normal.
Then you will select which Architecture your bug occurs on.
Example: If you are using an Intel x86 platform, you will choose i386.
The Cc: field can be used to add someone to the carbon-copy list for all email related to this bug. As the reporter of the bug, you will automatically be copied on any mail, so you do not need to add yourself to this.
Enter a one line description of the bug into the Summary field, and the full description of the bug into the Description field.

3. What happens once I enter a bug?
After you enter a bug, mail is sent both to you and the QA department of Red Hat. A member of the QA department will verify that they can reproduce your bug, and may contact you to get additional information.
After the bug has been verified, it will be assigned to a developer to look into a resolution for the bug.
Once a resolution has been found, the bug will be marked CLOSED with a resolution status.
At each step of the process, you will get an email message that will tell you what has been updated on your bug report.

4. How do I search for a bug?
To search for a bug, select Go to the query page from the main bugzilla page.
The bugzilla search uses an "OR" within each field, with an "AND" between fields. So, if you were to select NEW and VERIFIED from the Status field and normal from the Priority field, you would be asking for all normal priority bugs that are new or verified.

5. How do I submit a patch?
The new Bugzilla system supports the attachment of patches, test cases, and various other forms of file types directly from the bug report screen. Just click on "Create an attachment". You will then be asked for the file name, a one line description, and the file type. After that it will be uploaded to server so that it can be displayed later from the same bug report.

6. Are cookies required?
Yes. If you do not have cookies enabled or are using a browser that does not support cookies, you will be prompted to re-login for each screen. It also allows for special features like stored queries and keeping track of your last query result list.

Bugzilla FAQ - Camino Project <1>

Q. What to do with a bug or feature request?
If you want your bug or feature request to be considered, it’s important to follow the right process. Doing so ensures that it will be seen and considered by the Camino developers.

Q. I found a bug. What should I do?
A. Bugs for Camino are managed through a system called Bugzilla. To report a bug, just go to the bug reporting helper and follow the instructions. Be sure to take the time to search for duplicates in step 1, since repeated reports of the same issue waste both your and developers’ time.
If you’ve never used the system before, you’ll need to create an account first. Creating an account is extremely quick and easy.

Q. Camino crashed! What do I do now?
A. If you can reproduce the crash, file a bug. When reporting a crashing bug, be sure to set the severity to “critical”, add “crash” in the keyword field, and have the following things handy: the URL on which the crash occurred (if the crash was browsing-related), detailed steps to reproduce the crash (if some action was required), and a crash log.
Mac OS X ships with a very helpful tool called Crash Reporter. When Camino crashes and you see a dialog stating “The application Camino has unexpectedly quit”, click the “Submit Report…” button. Copy the entire contents of the “Crash Report:” text field into a new plain-text document (in TextEdit, create a new document and choose Make Plain Text from the Format menu). Once you have saved the text file, you can dismiss the Crash Report dialog. Note: The wording of the dialogs varies slightly between major Mac OS X versions.
If the “The application Camino has unexpectedly quit” dialog fails to appear, you have most likely disabled Crash Reporter and you will have to extract the crash log from the system’s crash logs manually.
After you have filed your initial bug report, attach the file containing the crash log to the bug using the “Create a New Attachment” link. Please do not paste crash reports into the “Comments” field of the bug report.
In addition to taking these steps to obtain the crash report, you should let the Talkback application run and file a report with mozilla.org; this report is used to aggregate crash data and often helps identify causes of crashes that are otherwise not reproducible.

Q. Camino keeps displaying the “spinning beachball” and does not respond.
A. Camino has entered a “hung” state; the only way to end this state is to “force quit” Camino. If you can reproduce the situation, file a bug. Be sure to set the severity to “critical”, add “hang” in the keyword field, and have the following things handy: the URL on which the hang occurred (if the hang was browsing-related), detailed steps to reproduce the hang (if some action was required), and a sample of Camino while it is in the hung state.
Before you force quit Camino, open the Activity Monitor application located in the Utilities subfolder of the Applications folder. On launch, the application should display a window listing various “processes” that are running on your Mac. Select Camino from the list and then click the “Inspect” button. In the window that opens, click the “Sample” button; this will generate a log that will help the developers determine why Camino entered the hung state. When the sample is complete, save the file; you may now close the sample window and force quit Camino.
After you have filed your initial bug report, attach the sample file to the bug using the “Create a New Attachment” link. Please do not paste samples into the “Comments” field of the bug report.

Bugzilla FAQ - Camino Project <2>

Q. There’s a problem with a page that requires a login.
A. In most cases the Camino developers and bug triage team members won’t have access to the site in question. However, there are still ways to generate a bug report that will allow the Camino team to assess the problem and hopefully fix it. When you are on the problematic page, take a screenshot (be sure to obscure any personal or confidential information before attaching the screenshot to your bug); a screenshot is most useful for situations where the page does not display properly.
After taking a screenshot, choose Save As… from the File menu and then select HTML Complete from the Format: drop-down menu at the bottom of the Save dialog. This will save a copy of the page and a folder containing all of the files referenced by that page (if the page is saved as my_page.html, the folder will be called my_page Files). If the page displayed any personal or confidential information (like a password or an account number), drag the saved .html file onto TextEdit and replace that information with a string of X or other characters. Be careful not to edit any of the HTML. It’s probably a good idea to check all of the associated files in the folder to make sure none of them contain personal information, either.
When you’re sure there’s no personal information remaining, select both the folder and the .html file in the Finder, ctrl-click, and choose Create Archive of 2 items from the Finder’s context menu. After you file your bug report, attach this archive and the screenshot (if needed) to the bug using the “Create a New Attachment” link. Make sure to include the URL to the page (again, removing any personal information that might be contained in the URL) in your bug report for reference.

Q. I want a new feature. What should I do?
A. Follow the instructions above for reporting a bug, but pick “Enhancement” as the severity at the last step.

Q. Can’t I just post a message about the bug/feature in the forum instead?
A. You could, but it’s extremely unlikely to be fixed if you don’t file a bug. Developers use Bugzilla to track everything that needs to be done, and anything that isn’t in that system can easily be forgotten. There’s no guarantee a forum post will even be seen by a developer.

Q. Why hasn’t my bug been fixed yet?
A. Camino is developed entirely by a small group of volunteers, working in their free time. Limited developer time means that some bugs and feature requests can wait for months, or even years, until someone has time to address them. The order bugs are fixed in depends on overall project priorities, as well as the difficulty of bugs and the skills and interests of individual developers. Do not complain in a bug or ask why it hasn’t been fixed yet—see the Bugzilla etiquette. The only way to get bugs fixed faster is to contribute in some way (such as fixing them yourself, helping to recruit new developers, or helping out in some other way that frees up developers to spend more time on coding).
Demanding that a bug be fixed, whining, threatening to switch browsers, etc., is always counter-productive. Fixing bugs is simply a question of manpower and complaining in a bug wastes the time of everyone reading bug reports or following the progress of a bug via email.

Q. Why was my bug marked WONTFIX?
A. Camino’s goal is to be lightweight and easy to use. That means that it can’t include every feature that is ever requested. Invariably, some people will be unhappy with the decisions that are made regarding which features aren’t included, but strong leadership is necessary to keep Camino true to its vision. WONTFIX decisions are made by the Camino lead, are made for good reason (even if not explained in the bug), and as such are final. Do not complain or argue in a bug that has been marked WONTFIX. Unless you have new, compelling information to add, do not comment in the bug. Please remember that “x people I talked to said this is really important” is not compelling information. Unless you have have done a statistically valid sample of Camino’s entire target user base (and neither Bugzilla nor online forums are representative samples), you aren’t going to convince anyone.

Q. If only some people want a feature, couldn’t it just be a preference?
A. In general, no. First, every piece of code needs to be written and maintained, both of which take developer time away from bugs and other features. Second, each added preference makes all other preferences slightly less accessible. Camino’s goal is to be lightweight, which means keeping the number of preferences down as well.

Test Plan Template

2010-01-26T09:45:00.000-08:00

Test Plan Template

(Name of the Product)

TABLE OF CONTENTS

1.0 INTRODUCTION
2.0 OBJECTIVES AND TASKS
2.1 Objectives
2.2 Tasks
3.0 SCOPE
4.0 Testing Strategy
4.1 Alpha Testing (Unit Testing)
4.2 System and Integration Testing
4.3 Performance and Stress Testing
4.4 User Acceptance Testing
4.5 Batch Testing
4.6 Automated Regression Testing
4.7 Beta Testing
5.0 Hardware Requirements
6.0 Environment Requirements
6.1 Main Frame
6.2 Workstation
7.0 Test Schedule
8.0 Control Procedures
9.0 Features to Be Tested
10.0 Features Not to Be Tested
11.0 Resources/Roles & Responsibilities
12.0 Schedules
13.0 Significantly Impacted Departments (SIDs)
14.0 Dependencies
15.0 Risks/Assumptions
16.0 Tools
17.0 Approvals
18.0 References Appendices

Web-based Application Testing

2010-01-26T09:25:00.001-08:00

1. Browser functionality: • Is the browser compatible with the application design? • There are many different types of browsers available. • GUI design components • Are the scroll bars, buttons, and frames compatible with the browser and functional? • To check the functionality of the scroll bars on the interface of the Web page to make sure the the user can scroll through items and make the correct selection from a list of items. • The button on the interface need to be functional and the correct hyperlink should go to the correct page. • If frames are used on the interface, they should be checked for the correct size and whether all of the components fit within the viewing screen of the monitor.
2. User InterfaceOne of the reasons the web browser is being used as the front end to applications is the ease of use. Users who have been on the web before will probably know how to navigate a well-built web site. While you are concentrating on this portion of testing it is important to verify that the application is easy to use. Many will believe that this is the least important area to test, but if you want to be successful, the site better be easy to use. 3.InstructionsYou want to make sure there are instructions. Even if you think the web site is simple, there will always be someone who needs some clarification. Additionally, you need to test the documentation to verify that the instructions are correct. If you follow each instruction does the expected result occur?
4. Site map or navigational barDoes the site have a map? Sometimes power users know exactly where they want to go and don't want to wade through lengthy introductions. Or new users get lost easily. Either way a site map and/or an ever-present navigational bar can help guide the user. You need to verify that the site map is correct. Does each link on the map actually exist? Are there links on the site that are not represented on the map? Is the navigational bar present on every screen? Is it consistent? Does each link work on each page? Is it organized in an intuitive manner?
5. ContentTo a developer, functionality comes before wording. Anyone can slap together some fancy mission statement later, but while they are developing, they just need some filler to verify alignment and layout. Unfortunately, text produced like this may sneak through the cracks. It is important to check with the public relations department on the exact wording of the content.You also want to make sure the site looks professional. Overuse of bold text, big fonts and blinking (ugh) can turn away a customer quickly. It might be a good idea to consult a graphic designer to look over the site during User Acceptance Testing. You wouldn't slap together a brochure with bold text everywhere, so you want to handle the web site with the same level of professionalism.Finally, you want to make sure that any time a web reference is given that it is hyperlinked. Plenty of sites ask you to email them at a specific address or to download a browser from an address. But if the user can't click on it, they are going to be annoyed.
6. Colors/backgroundsEver since the web became popular, everyone thinks they are graphic designers. Unfortunately, some developers are more interested in their new backgrounds, than ease of use. Sites will have yellow text on a purple picture of a fractal pattern. (If you've never seen this, try most sites at GeoCities or AOL.) This may seem "pretty neat", but it's not easy to use.Usually, the best idea is to use little or no background. If you have a background, it might be a single color on the left side of the page, containing the navigational bar. But, patterns and pictures distract the user.
7. ImagesWhether it's a screen grab or a little icon that points the way, a picture is worth a thousand words. Sometimes, the best way to tell the user something is to simply show them. However, bandwidth is precious to the client and the server, so you need to conserve memory usage. Do all the images add value to each page, or do they simply waste bandwidth? Can a different file type (.GIF, .JPG) be used for 30k less?In general, you don't want large pictures on the front page, since most users who abandon a page due to a large load will do it on the front page. If you can get them to see the front page quickly, it will increase the chance they will stay.
8. Tables You also want to verify that tables are setup properly. Does the user constantly have to scroll right to see the price of the item? Would it be more effective to put the price closer to the left and put miniscule details to the right? Are the columns wide enough or does every row have to wrap around? Are certain columns considerably longer than others?
9. Wrap-aroundFinally, you will want to verify that wrap-around occurs properly. If the text refers to "a picture on the right", make sure the picture is on the right. Make sure that widowed and orphaned sentences and paragraphs don't layout in an awkward manner because of pictures.
10. FunctionalityThe functionality of the web site is why your company hired a developer and not just an artist. This is the part that interfaces with the server and actually "does stuff".
11. Links A link is the vehicle that gets the user from page to page. You will need to verify two things for each link: that the link brings you to the page it said it would and that the pages you are linking to actually exists. It may sound a little silly but I have seen plenty of web sites with internal broken links.
12. FormsWhen a user submits information through a form it needs to work properly. The submit button needs to work. If the form is for an online registration, the user should be given login information (that works) after successful completion. If the form gathers shipping information, it should be handled properly and the customer should receive their package. In order to test this, you need to verify that the server stores the information properly and that systems down the line can interpret and use that information.
13. Data verification
If the system verifies user input according to business rules, then that needs to work properly. For example, a State field may be checked against a list of valid values. If this is the case, you need to verify that the list is complete and that the program actually calls the list properly (add a bogus value to the list and make sure the system accepts it).
14. CookiesMost users only like the kind with sugar, but developers love web cookies. If the system uses them, you need to check them. If they store login information, make sure the cookies work. If the cookie is used for statistics, verify that totals are being counted properly. And you'll probably want to make sure those cookies are encrypted too, otherwise people can edit their cookies and skew your statistics.Application specific functional requirements Most importantly, you want to verify the application specific functional requirements. Try to perform all functions a user would: place an order, change an order, cancel an order, check the status of the order, change shipping information before an order is shipped, pay online, ad naseum. This is why your users will show up on your doorstep, so you need to make sure you can do what you advertise.
Black Box testing for web-based application: (3)
16. Interface TestingMany times, a web site is not an island. The site will call external servers for additional data, verification of data or fulfillment of orders.
16. Server interfaceThe first interface you should test is the interface between the browser and the server. You should attempt transactions, then view the server logs and verify that what you're seeing in the browser is actually happening on the server. It's also a good idea to run queries on the database to make sure the transaction data is being stored properly.
17. External interfacesSome web systems have external interfaces. For example, a merchant might verify credit card transactions real-time in order to reduce fraud. You will need to send several test transactions using the web interface. Try credit cards that are valid, invalid, and stolen. If the merchant only takes Visa and MasterCard, try using a Discover card. (A script can check the first digit of the credit card number: 3 for American Express, 4 for Visa, 5 for MasterCard, or 6 for Discover, before the transaction is sent.) Basically, you want to make sure that the software can handle every possible message returned by the external server.
18. Error handlingOne of the areas left untested most often is interface error handling. Usually we try to make sure our system can handle all of our errors, but we never plan for the other systems' errors or for the unexpected. Try leaving the site mid-transaction - what happens? Does the order complete anyway? Try losing the internet connection from the user to the server. Try losing the connection from the server to the credit card verification server. Is there proper error handling for all these situations? Are charges still made to credit cards? Is the interruption is not user initiated, does the order get stored so customer service reps can call back if the user doesn't come back to the site?
19. CompatibilityYou will also want to verify that the application can work on the machines your customers will be using. If the product is going to the web for the world to use, you will need to try different combinations of operating system, browser, video setting and modem speed.
20. Operating systemsDoes the site work for both MAC and IBM-Compatibles? Some fonts are not available on both systems, so make sure that secondary fonts are selected. Make sure that the site doesn't use plug-ins only available for one OS, if your users will use both.
21. BrowsersDoes your site work with Netscape? Internet Explorer? Lynx? Some HTML commands or scripts only work for certain browsers. Make sure there are alternate tags for images, in case someone is using a text browser. If you're using SSL security, you only need to check browsers 3.0 and higher, but verify that there is a message for those using older browsers.
22. Video settings Does the layout still look good on 640x400 or 600x800? Are fonts too small to read? Are they too big? Does all the text and graphic alignment still work?
23. Modem/connection speedsDoes it take 10 minutes to load a page with a 28.8 modem, but you tested hooked up to a T1? Users will expect long download times when they are grabbing documents or demos, but not on the front page. Make sure that the images aren't too large. Make sure that marketing didn't put 50k of font size -6 keywords for search engines.
Black Box testing for web-based application: (4)
23. PrintersUsers like to print. The concept behind the web should save paper and reduce printing, but most people would rather read on paper than on the screen. So, you need to verify that the pages print properly. Sometimes images and text align on the screen differently than on the printed page. You need to at least verify that order confirmation screens can be printed properly.
24. CombinationsNow you get to try combinations. Maybe 600x800 looks good on the MAC but not on the IBM. Maybe IBM with Netscape works, but not with Lynx.If the web site will be used internally it might make testing a little easier. If the company has an official web browser choice, then you just need to verify that it works for that browser. If everyone has a T1 connection, then you might not need to check load times. (But keep in mind, some people may dial in from home.) With internal applications, the development team can make disclaimers about system requirements and only support those systems setups. But, ideally, the site should work on all machines so you don't limit growth and changes in the future.
25. Load/StressYou will need to verify that the system can handle a large number of users at the same time, a large amount of data from each user, and a long period of continuous use. Accessibility is extremely important to users. If they get a "busy signal", they hang up and call the competition. Not only must the system be checked so your customers can gain access, but many times crackers will attempt to gain access to a system by overloading it. For the sake of security, your system needs to know what to do when it's overloaded and not simply blow up.Many users at the same timeIf the site just put up the results of a national lottery, it better be able to handle millions of users right after the winning numbers are posted. A load test tool would be able to simulate large number of users accessing the site at the same time.Large amount of data from each user Most customers may only order 1-5 books from your new online bookstore, but what if a university bookstore decides to order 5000 different books? Or what if grandma wants to send a gift to each of her 50 grandchildren for Christmas (separate mailing addresses for each, of course.) Can your system handle large amounts of data from a single user? Long period of continuous useIf the site is intended to take orders for flower deliveries, then it better be able to handle the week before Mother's Day. If the site offers web-based email, it better be able to run for months or even years, without downtimes. You will probably want to use an automated test tool to implement these types of tests, since they are difficult to do manually. Imagine coordinating 100 people to hit the site at the same time. Now try 100,000 people. Generally, the tool will pay for itself the second or third time you use it. Once the tool is set up, running another test is just a click away.
26. SecurityEven if you aren't accepting credit card payments, security is very important. The web site will be the only exposure some customers have to your company. And, if that exposure is a hacked page, they won't feel safe doing business with you.
Black Box testing for web-based application: (5)
27. Directory setupThe most elementary step of web security is proper setup of directories. Each directory should have an index.html or main.html page so a directory listing doesn't appear.One company I was consulting for didn't observe this principal. I right clicked on an image and found the path "...com/objects/images". I went to that directory manually and found a complete listing of the images on that site. That wasn't too important. Next, I went to the directory below that: "...com/objects" and I hit the jackpot. There were plenty of goodies, but what caught my eye were the historical pages. They had changed their prices every month and kept the old pages. I browsed around and could figure out their profit margin and how low they were willing to go on a contract. If a potential customer did a little browsing first, they would have had a definite advantage at the bargaining table.SSL Many sites use SSL for secure transactions. You know you entered an SSL site because there will be a browser warning and the HTTP in the location field on the browser will change to HTTPS. If your development group uses SSL you need to make sure there is an alternate page for browser with versions less than 3.0, since SSL is not compatible with those browsers. You also need to make sure that there are warnings when you enter and leave the secured site. Is there a timeout limit? What happens if the user tries a transaction after the timeout?
28 LoginsIn order to validate users, several sites require customers to login. This makes it easier for the customer since they don't have to re-enter personal information every time. You need to verify that the system does not allow invalid usernames/password and that it does allow valid logins. Is there a maximum number of failed logins allowed before the server locks out the current user? Is the lockout based on IP? What if the maximum failed login attempts is three, and you try three, but then enter a valid login? What are the rules for password selection?
29. Log filesBehind the scenes, you will need to verify that server logs are working properly. Does the log track every transaction? Does it track unsuccessful login attempts? Does it only track stolen credit card usage? What does it store for each transaction? IP address? User name?
30. Scripting languagesScripting languages are a constant source of security holes. The details are different for each language. Some exploits allow access to the root directory. Others allow access to the mail server. Find out what scripting languages are being used and research the loopholes. It might also be a good idea to subscribe to a security newsgroup that discusses the language you will be testing.
31. Web Server Testing Features • Feature: Definition • Transactions: The nunber of times the test script requested the current URL • Elapsed time: The number of seconds it took to run the request • Bytes transferred: The total number of bytes sent or received, less HTTP headers • Response time: The average time it took for the server to respond to each individual request. • Transaction rate: The average number of transactions the server was able to handle per second. • Transferance: The average number of bytes transferred per second. • Concurrency: The average number of simultaneous connections the server was able to handle during the test session. • Status code nnn: This indicates how many times a particular HTTP status code was seen.

Software Quality Interview question 101-195

2010-01-26T09:15:00.000-08:00

101. What is Test Bed?
An execution environment configured for testing. May consist of specific hardware, OS, network topology, configuration of the product under test, other application or system software, etc. The Test Plan for a project should enumerated the test beds(s) to be used.

102. What is Test Case?
Test Case is a commonly used term for a specific test. This is usually the smallest unit of testing. A Test Case will consist of information such as requirements testing, test steps, verification steps, prerequisites, outputs, test environment, etc. A set of inputs, execution preconditions, and expected outcomes developed for a particular objective, such as to exercise a particular program path or to verify compliance with a specific requirement. Test Driven Development? Testing methodology associated with Agile Programming in which every chunk of code is covered by unit tests, which must all pass all the time, in an effort to eliminate unit-level and regression bugs during development. Practitioners of TDD write a lot of tests, i.e. an equal number of lines of test code to the size of the production code.

103. What is Test Driver?
A program or test tool used to execute a tests. Also known as a Test Harness.

104. What is Test Environment?
The hardware and software environment in which tests will be run, and any other software with which the software under test interacts when under test including stubs and test drivers.

105. What is Test First Design?
Test-first design is one of the mandatory practices of Extreme Programming (XP).It requires that programmers do not write any production code until they have first written a unit test.

106. What is Test Harness?
A program or test tool used to execute a tests. Also known as a Test Driver.

107. What is Test Plan?
A document describing the scope, approach, resources, and schedule of intended testing activities. It identifies test items, the features to be tested, the testing tasks, who will do each task, and any risks requiring contingency planning.

108. What is Test Procedure?
A document providing detailed instructions for the execution of one or more test cases.

109. What is Test Script?
Commonly used to refer to the instructions for a particular test that will be carried out by an automated test tool.

110. What is Test Specification?
A document specifying the test approach for a software feature or combination or features and the inputs, predicted results and execution conditions for the associated tests.

111. What is Test Suite?
A collection of tests used to validate the behavior of a product. The scope of a Test Suite varies from organization to organization. There may be several Test Suites for a particular product for example. In most cases however a Test Suite is a high level concept, grouping together hundreds or thousands of tests related by what they are intended to test.

112. What is Test Tools?
Computer programs used in the testing of a system, a component of the system, or its documentation.

113. What is Thread Testing?
A variation of top-down testing where the progressive integration of components follows the implementation of subsets of the requirements, as opposed to the integration of components by successively lower levels.
114. What is Top Down Testing?
An approach to integration testing where the component at the top of the component hierarchy is tested first, with lower level components being simulated by stubs. Tested components are then used to test lower level components. The process is repeated until the lowest level components have been tested.

115. What is Total Quality Management?
A company commitment to develop a process that achieves high quality product and customer satisfaction.

116. What is Traceability Matrix?
A document showing the relationship between Test Requirements and Test Cases.

117. What is Usability Testing?
Testing the ease with which users can learn and use a product.

118. What is Use Case?
The specification of tests that are conducted from the end-user perspective. Use cases tend to focus on operating software as an end-user would conduct their day-to-day activities.

119. What is Unit Testing?
Testing of individual software components.

120. What is Validation?
The process of evaluating software at the end of the software development process to ensure compliance with software requirements. The techniques for validation is testing, inspection and reviewing.

121. What is Verification?
The process of determining whether of not the products of a given phase of the software development cycle meet the implementation steps and can be traced to the incoming objectives established during the previous phase. The techniques for verification are testing, inspection and reviewing.

122. What is White Box Testing?
Testing based on an analysis of internal workings and structure of a piece of software. Includes techniques such as Branch Testing and Path Testing. Also known as Structural Testing and Glass Box Testing. Contrast with Black Box Testing. White box testing is used to test the internal logic of the code.for ex checking whether the path has been executed once, checking whether the branches has been executed at least once .....Used to check the structure of the code.

123. What is Workflow Testing?
Scripted end-to-end testing which duplicates specific workflows which are expected to be utilized by the end-user.

124. What's the difference between load and stress testing ?
One of the most common, but unfortunate misuse of terminology is treating “load testing” and “stress testing” as synonymous. The consequence of this ignorant semantic abuse is usually that the system is neither properly “load tested” nor subjected to a meaningful stress test. Stress testing is subjecting a system to an unreasonable load while denying it the resources (e.g., RAM, disc, mips, interrupts, etc.) needed to process that load. The idea is to stress a system to the breaking point in order to find bugs that will make that break potentially harmful. The system is not expected to process the overload without adequate resources, but to behave (e.g., fail) in a decent manner (e.g., not corrupting or losing data). Bugs and failure modes discovered under stress testing may or may not be repaired depending on the application, the failure mode, consequences, etc. The load (incoming transaction stream) in stress testing is often deliberately distorted so as to force the system into resource depletion. Load testing is subjecting a system to a statistically representative (usually) load. The two main reasons for using such loads is in support of software reliability testing and in performance testing. The term 'load testing' by itself is too vague and imprecise to warrant use. For example, do you mean representative load,' 'overload,' 'high load,' etc. In performance testing, load is varied from a minimum (zero) to the maximum level the system can sustain without running out of resources or having, transactions >suffer (application-specific) excessive delay. A third use of the term is as a test whose objective is to determine the maximum sustainable load the system can handle. In this usage, 'load testing' is merely testing at the highest transaction arrival rate in performance testing.

125. What's the difference between QA and testing?
QA is more a preventive thing, ensuring quality in the company and therefore the product rather than just testing the product for software bugs? TESTING means 'quality control' QUALITY CONTROL measures the quality of a product QUALITY ASSURANCE measures the quality of processes used to create a quality product.

126. What is the best tester to developer ratio?
Reported tester: developer ratios range from 10:1 to 1:10. There's no simple answer. It depends on so many things, Amount of reused code, number and type of interfaces, platform, quality goals, etc. It also can depend on the development model. The more specs, the less testers. The roles can play a big part also. Does QA own beta? Do you include process auditors or planning activities? These figures can all vary very widely depending on how you define 'tester' and 'developer'. In some organizations, a 'tester' is anyone who happens to be testing software at the time -- such as their own. In other organizations, a 'tester' is only a member of an independent test group. It is better to ask about the test labor content than it is to ask about the tester/developer ratio. The test labor content, across most applications is generally accepted as 50%, when people do honest accounting. For life-critical software, this can go up to 80%.

127. How can new Software QA processes be introduced in an existing organization?
- A lot depends on the size of the organization and the risks involved. For large organizations with high-risk (in terms of lives or property) projects, serious management buy-in is required and a formalized QA process is necessary. - Where the risk is lower, management and organizational buy-in and QA implementation may be a slower, step-at-a-time process. QA processes should be balanced with productivity so as to keep bureaucracy from getting out of hand. - For small groups or projects, a more ad-hoc process may be appropriate, depending on the type of customers and projects. A lot will depend on team leads or managers, feedback to developers, and ensuring adequate communications among customers, managers, developers, and testers. - In all cases the most value for effort will be in requirements management processes, with a goal of clear, complete, testable requirement specifications or expectations.

128. What are 5 common problems in the software development process?
1. poor requirements - if requirements are unclear, incomplete, too general, or not testable, there will be problems. 2. unrealistic schedule - if too much work is crammed in too little time, problems are inevitable. 3. inadequate testing - no one will know whether or not the program is any good until the customer complains or systems crash. 4. featuritis - requests to pile on new features after development is underway; extremely common. 5. miscommunication - if developers don't know what's needed or customer's have erroneous expectations, problems are guaranteed.

129. What are 5 common solutions to software development problems?
1. solid requirements - clear, complete, detailed, cohesive, attainable, testable requirements that are agreed to by all players. Use prototypes to help nail down requirements. 2. realistic schedules - allow adequate time for planning, design, testing, bug fixing, re-testing, changes, and documentation; personnel should be able to complete the project without burning out. 3. adequate testing - start testing early on, re-test after fixes or changes, plan for adequate time for testing and bug-fixing. 4. stick to initial requirements as much as possible - be prepared to defend against changes and additions once development has begun, and be prepared to explain consequences. If changes are necessary, they should be adequately reflected in related schedule changes. If possible, use rapid prototyping during the design phase so that customers can see what to expect. This will provide them a higher comfort level with their requirements decisions and minimize changes later on. 5. communication - require walkthroughs and inspections when appropriate; make extensive use of group communication tools - e-mail, groupware, networked bug-tracking tools and change management tools, intranet capabilities, etc.; insure that documentation is available and up-to-date - preferably electronic, not paper; promote teamwork and cooperation; use prototypes early on so that customers' expectations are clarified.

130. What is 'good code'?
'Good code' is code that works, is bug free, and is readable and maintainable. Some organizations have coding 'standards' that all developers are supposed to adhere to, but everyone has different ideas about what's best, or what is too many or too few rules. There are also various theories and metrics, such as McCabe Complexity metrics. It should be kept in mind that excessive use of standards and rules can stifle productivity and creativity. 'Peer reviews', 'buddy checks' code analysis tools, etc. can be used to check for problems and enforce standards. For C and C++ coding, here are some typical ideas to consider in setting rules/standards; these may or may not apply to a particular situation: - minimize or eliminate use of global variables. - use descriptive function and method names - use both upper and lower case, avoid abbreviations, use as many characters as necessary to be adequately descriptive (use of more than 20 characters is not out of line); be consistent in naming conventions. - use descriptive variable names - use both upper and lower case, avoid abbreviations, use as many characters as necessary to be adequately descriptive (use of more than 20 characters is not out of line); be consistent in naming conventions. - function and method sizes should be minimized; less than 100 lines of code is good, less than 50 lines is preferable. - function descriptions should be clearly spelled out in comments preceding a function's code.- organize code for readability. - use whitespace generously - vertically and horizontally - each line of code should contain 70 characters max. - one code statement per line. - coding style should be consistent through a program (eg, use of brackets, indentations, naming conventions, etc.) - in adding comments, err on the side of too many rather than too few comments; a common rule of thumb is that there should be at least as many lines of comments (including header blocks) as lines of code. - no matter how small, an application should include documentaion of the overall program function and flow (even a few paragraphs is better than nothing); or if possible a separate flow chart and detailed program documentation. - make extensive use of error handling procedures and status and error logging. - for C++, to minimize complexity and increase maintainability, avoid too many levels of inheritance in class heirarchies (relative to the size and complexity of the application). Minimize use of multiple inheritance, and minimize use of operator overloading (note that the Java programming language eliminates multiple inheritance and operator overloading.) - for C++, keep class methods small, less than 50 lines of code per method is preferable. - for C++, make liberal use of exception handlers

131. What is 'good design'?
'Design' could refer to many things, but often refers to 'functional design' or 'internal design'. Good internal design is indicated by software code whose overall structure is clear, understandable, easily modifiable, and maintainable; is robust with sufficient error-handling and status logging capability; and works correctly when implemented. Good functional design is indicated by an application whose functionality can be traced back to customer and end-user requirements. For programs that have a user interface, it's often a good idea to assume that the end user will have little computer knowledge and may not read a user manual or even the on-line help; some common rules-of-thumb include: - the program should act in a way that least surprises the user - it should always be evident to the user what can be done next and how to exit - the program shouldn't let the users do something stupid without warning them.

132. What makes a good test engineer?
A good test engineer has a 'test to break' attitude, an ability to take the point of view of the customer, a strong desire for quality, and an attention to detail. Tact and diplomacy are useful in maintaining a cooperative relationship with developers, and an ability to communicate with both technical (developers) and non-technical (customers, management) people is useful. Previous software development experience can be helpful as it provides a deeper understanding of the software development process, gives the tester an appreciation for the developers' point of view, and reduce the learning curve in automated test tool programming. Judgment skills are needed to assess high-risk areas of an application on which to focus testing efforts when time is limited.

133. What makes a good Software QA engineer?
The same qualities a good tester has are useful for a QA engineer. Additionally, they must be able to understand the entire software development process and how it can fit into the business approach and goals of the organization. Communication skills and the ability to understand various sides of issues are important. In organizations in the early stages of implementing QA processes, patience and diplomacy are especially needed. An ability to find problems as well as to see 'what's missing' is important for inspections and reviews.

134. What makes a good QA or Test manager?
A good QA, test, or QA/Test(combined) manager should: - be familiar with the software development process - be able to maintain enthusiasm of their team and promote a positive atmosphere, despite what is a somewhat 'negative' process (e.g., looking for or preventing problems) - be able to promote teamwork to increase productivity - be able to promote cooperation between software, test, and QA engineers - have the diplomatic skills needed to promote improvements in QA processes -have the ability to withstand pressures and say 'no' to other managers when quality is insufficient or QA processes are not being adhered to - have people judgment skills for hiring and keeping skilled personnel- be able to communicate with technical and non-technical people, engineers, managers, and customers. - be able to run meetings and keep them focused

135. What's the role of documentation in QA?
Critical. (Note that documentation can be electronic, not necessarily paper.) QA practices should be documented such that they are repeatable. Specifications, designs, business rules, inspection reports, configurations, code changes, test plans, test cases, bug reports, user manuals, etc. should all be documented. There should ideally be a system for easily finding and obtaining documents and determining what documentation will have a particular piece of information. Change management for documentation should be used if possible.

136. What's the big deal about 'requirements'?
One of the most reliable methods of insuring problems, or failure, in a complex software project is to have poorly documented requirements specifications. Requirements are the details describing an application's externally-perceived functionality and properties. Requirements should be clear, complete, reasonably detailed, cohesive, attainable, and testable. A non-testable requirement would be, for example, 'user-friendly' (too subjective). A testable requirement would be something like 'the user must enter their previously-assigned password to access the application'. Determining and organizing requirements details in a useful and efficient way can be a difficult effort; different methods are available depending on the particular project. Many books are available that describe various approaches to this task. Care should be taken to involve ALL of a project's significant 'customers' in the requirements process. 'Customers' could be in-house personnel or out, and could include end-users, customer acceptance testers, customer contract officers, customer management, future software maintenance engineers, salespeople, etc. Anyone who could later derail the project if their expectations aren't met should be included if possible. Organizations vary considerably in their handling of requirements specifications. Ideally, the requirements are spelled out in a document with statements such as 'The product shall.....'. 'Design' specifications should not be confused with 'requirements'; design specifications should be traceable back to the requirements. In some organizations requirements may end up in high level project plans, functional specification documents, in design documents, or in other documents at various levels of detail. No matter what they are called, some type of documentation with detailed requirements will be needed by testers in order to properly plan and execute tests. Without such documentation, there will be no clear-cut way to determine if a software application is performing correctly.

137. What steps are needed to develop and run software tests?
The following are some of the steps to consider: - Obtain requirements, functional design, and internal design specifications and other necessary documents - Obtain budget and schedule requirements - Determine project-related personnel and their responsibilities, reporting requirements, required standards and processes (such as release processes, change processes, etc.) - Identify application's higher-risk aspects, set priorities, and determine scope and limitations of tests - Determine test approaches and methods - unit, integration, functional, system, load, usability tests, etc. - Determine test environment requirements (hardware, software, communications, etc.) -Determine testware requirements (record/playback tools, coverage analyzers, test tracking, problem/bug tracking, etc.) - Determine test input data requirements - Identify tasks, those responsible for tasks, and labor requirements - Set schedule estimates, timelines, milestones - Determine input equivalence classes, boundary value analyses, error classes - Prepare test plan document and have needed reviews/approvals - Write test cases - Have needed reviews/inspections/approvals of test cases - Prepare test environment and testware, obtain needed user manuals/reference documents/configuration guides/installation guides, set up test tracking processes, set up logging and archiving processes, set up or obtain test input data - Obtain and install software releases - Perform tests - Evaluate and report results - Track problems/bugs and fixes - Retest as needed - Maintain and update test plans, test cases, test environment, and testware through life cycle

138. What is 'configuration management'?
Configuration management covers the processes used to control, coordinate, and track: code, requirements, documentation, problems, change requests, designs, tools/compilers/libraries/patches, changes made to them, and who makes the changes.

139. What if the software is so buggy it can't really be tested at all?
The best bet in this situation is for the testers to go through the process of reporting whatever bugs or blocking-type problems initially show up, with the focus being on critical bugs. Since this type of problem can severely affect schedules, and indicates deeper problems in the software development process (such as insufficient unit testing or insufficient integration testing, poor design, improper build or release procedures, etc.) managers should be notified, and provided with some documentation as evidence of the problem.

140. How can it be known when to stop testing?
This can be difficult to determine. Many modern software applications are so complex, and run in such an interdependent environment, that complete testing can never be done. Common factors in deciding when to stop are: - Deadlines (release deadlines, testing deadlines, etc.)- Test cases completed with certain percentage passed - Test budget depleted - Coverage of code/functionality/requirements reaches a specified point - Bug rate falls below a certain level - Beta or alpha testing period ends

141. What if there isn't enough time for thorough testing?
Use risk analysis to determine where testing should be focused. Since it's rarely possible to test every possible aspect of an application, every possible combination of events, every dependency, or everything that could go wrong, risk analysis is appropriate to most software development projects. This requires judgment skills, common sense, and experience. (If warranted, formal methods are also available.) Considerations can include: - Which functionality is most important to the project's intended purpose? - Which functionality is most visible to the user? - Which functionality has the largest safety impact? - Which functionality has the largest financial impact on users? - Which aspects of the application are most important to the customer? - Which aspects of the application can be tested early in the development cycle? - Which parts of the code are most complex, and thus most subject to errors? - Which parts of the application were developed in rush or panic mode? - Which aspects of similar/related previous projects caused problems? - Which aspects of similar/related previous projects had large maintenance expenses? - Which parts of the requirements and design are unclear or poorly thought out? - What do the developers think are the highest-risk aspects of the application? - What kinds of problems would cause the worst publicity? - What kinds of problems would cause the most customer service complaints?- What kinds of tests could easily cover multiple functionalities? - Which tests will have the best high-risk-coverage to time-required ratio?

142. What can be done if requirements are changing continuously?
A common problem and a major headache. - Work with the project's stakeholders early on to understand how requirements might change so that alternate test plans and strategies can be worked out in advance, if possible. - It's helpful if the application's initial design allows for some adaptability so that later changes do not require redoing the application from scratch. - If the code is well-commented and well-documented this makes changes easier for the developers.- Use rapid prototyping whenever possible to help customers feel sure of their requirements and minimize changes. - The project's initial schedule should allow for some extra time commensurate with the possibility of changes.- Try to move new requirements to a 'Phase 2' version of an application, while using the original requirements for the 'Phase 1' version. - Negotiate to allow only easily-implemented new requirements into the project, while moving more difficult new requirements into future versions of the application. - Be sure that customers and management understand the scheduling impacts, inherent risks, and costs of significant requirements changes. Then let management or the customers (not the developers or testers) decide if the changes are warranted - after all, that's their job. - Balance the effort put into setting up automated testing with the expected effort required to re-do them to deal with changes. - Try to design some flexibility into automated test scripts. - Focus initial automated testing on application aspects that are most likely to remain unchanged. - Devote appropriate effort to risk analysis of changes to minimize regression testing needs. - Design some flexibility into test cases (this is not easily done; the best bet might be to minimize the detail in the test cases, or set up only higher-level generic-type test plans) - Focus less on detailed test plans and test cases and more on ad hoc testing (with an understanding of the added risk that this entails).

143. What if the project isn't big enough to justify extensive testing?
Consider the impact of project errors, not the size of the project. However, if extensive testing is still not justified, risk analysis is again needed and the same considerations as described previously in 'What if there isn't enough time for thorough testing?' apply. The tester might then do ad hoc testing, or write up a limited test plan based on the risk analysis.

144. What if the application has functionality that wasn't in the requirements?
It may take serious effort to determine if an application has significant unexpected or hidden functionality, and it would indicate deeper problems in the software development process. If the functionality isn't necessary to the purpose of the application, it should be removed, as it may have unknown impacts or dependencies that were not taken into account by the designer or the customer. If not removed, design information will be needed to determine added testing needs or regression testing needs. Management should be made aware of any significant added risks as a result of the unexpected functionality. If the functionality only effects areas such as minor improvements in the user interface, for example, it may not be a significant risk.

145. How can Software QA processes be implemented without stifling productivity?
By implementing QA processes slowly over time, using consensus to reach agreement on processes, and adjusting and experimenting as an organization grows and matures, productivity will be improved instead of stifled. Problem prevention will lessen the need for problem detection, panics and burn-out will decrease, and there will be improved focus and less wasted effort. At the same time, attempts should be made to keep processes simple and efficient, minimize paperwork, promote computer-based processes and automated tracking and reporting, minimize time required in meetings, and promote training as part of the QA process. However, no one - especially talented technical types - likes rules or bureaucracy, and in the short run things may slow down a bit. A typical scenario would be that more days of planning and development will be needed, but less time will be required for late-night bug-fixing and calming of irate customers.

146. What if an organization is growing so fast that fixed QA processes are impossible?
This is a common problem in the software industry, especially in new technology areas. There is no easy solution in this situation, other than: - Hire good people - Management should 'ruthlessly prioritize' quality issues and maintain focus on the customer - Everyone in the organization should be clear on what 'quality' means to the customer

147. How does a client/server environment affect testing?
Client/server applications can be quite complex due to the multiple dependencies among clients, data communications, hardware, and servers. Thus testing requirements can be extensive. When time is limited (as it usually is) the focus should be on integration and system testing. Additionally, load/stress/performance testing may be useful in determining client/server application limitations and capabilities. There are commercial tools to assist with such testing.

148.How can World Wide Web sites be tested?
Web sites are essentially client/server applications - with web servers and 'browser' clients. Consideration should be given to the interactions between html pages, TCP/IP communications, Internet connections, firewalls, applications that run in web pages (such as applets, javascript, plug-in applications), and applications that run on the server side (such as cgi scripts, database interfaces, logging applications, dynamic page generators, asp, etc.). Additionally, there are a wide variety of servers and browsers, various versions of each, small but sometimes significant differences between them, variations in connection speeds, rapidly changing technologies, and multiple standards and protocols. The end result is that testing for web sites can become a major ongoing effort. Other considerations might include: - What are the expected loads on the server (e.g., number of hits per unit time?), and what kind of performance is required under such loads (such as web server response time, database query response times). What kinds of tools will be needed for performance testing (such as web load testing tools, other tools already in house that can be adapted, web robot downloading tools, etc.)? - Who is the target audience? What kind of browsers will they be using? What kind of connection speeds will they by using? Are they intra- organization (thus with likely high connection speeds and similar browsers) or Internet-wide (thus with a wide variety of connection speeds and browser types)? - What kind of performance is expected on the client side (e.g., how fast should pages appear, how fast should animations, applets, etc. load and run)? - Will down time for server and content maintenance/upgrades be allowed? how much? - What kinds of security (firewalls, encryptions, passwords, etc.) will be required and what is it expected to do? How can it be tested? - How reliable are the site's Internet connections required to be? And how does that affect backup system or redundant connection requirements and testing? - What processes will be required to manage updates to the web site's content, and what are the requirements for maintaining, tracking, and controlling page content, graphics, links, etc.? - Which HTML specification will be adhered to? How strictly? What variations will be allowed for targeted browsers? - Will there be any standards or requirements for page appearance and/or graphics throughout a site or parts of a site?? - How will internal and external links be validated and updated? how often? - Can testing be done on the production system, or will a separate test system be required? How are browser caching, variations in browser option settings, dial-up connection variabilities, and real-world internet 'traffic congestion' problems to be accounted for in testing?- How extensive or customized are the server logging and reporting requirements; are they considered an integral part of the system and do they require testing?- How are cgi programs, applets, javascripts, ActiveX components, etc. to be maintained, tracked, controlled, and tested? - Pages should be 3-5 screens max unless content is tightly focused on a single topic. If larger, provide internal links within the page. - The page layouts and design elements should be consistent throughout a site, so that it's clear to the user that they're still within a site. - Pages should be as browser-independent as possible, or pages should be provided or generated based on the browser-type. - All pages should have links external to the page; there should be no dead-end pages. - The page owner, revision date, and a link to a contact person or organization should be included on each page.

149. How is testing affected by object-oriented designs?
Well-engineered object-oriented design can make it easier to trace from code to internal design to functional design to requirements. While there will be little affect on black box testing (where an understanding of the internal design of the application is unnecessary), white-box testing can be oriented to the application's objects. If the application was well-designed this can simplify test design.

150. What is Extreme Programming and what's it got to do with testing?
Extreme Programming (XP) is a software development approach for small teams on risk-prone projects with unstable requirements. It was created by Kent Beck who described the approach in his book 'Extreme Programming Explained'. Testing ('extreme testing') is a core aspect of Extreme Programming. Programmers are expected to write unit and functional test code first - before the application is developed. Test code is under source control along with the rest of the code. Customers are expected to be an integral part of the project team and to help developed scenarios for acceptance/black box testing. Acceptance tests are preferably automated, and are modified and rerun for each of the frequent development iterations. QA and test personnel are also required to be an integral part of the project team. Detailed requirements documentation is not used, and frequent re-scheduling, re-estimating, and re-prioritizing is expected.

151. Will automated testing tools make testing easier?
- Possibly. For small projects, the time needed to learn and implement them may not be worth it. For larger projects, or on-going long-term projects they can be valuable. - A common type of automated tool is the 'record/playback' type. For example, a tester could click through all combinations of menu choices, dialog box choices, buttons, etc. in an application GUI and have them 'recorded' and the results logged by a tool. The 'recording' is typically in the form of text based on a scripting language that is interpretable by the testing tool. If new buttons are added, or some underlying code in the application is changed, etc. the application can then be retested by just 'playing back' the 'recorded' actions, and comparing the logging results to check effects of the changes. The problem with such tools is that if there are continual changes to the system being tested, the 'recordings' may have to be changed so much that it becomes very time-consuming to continuously update the scripts. Additionally, interpretation of results (screens, data, logs, etc.) can be a difficult task. Note that there are record/playback tools for text-based interfaces also, and for all types of platforms.- Other automated tools can include: code analyzers - monitor code complexity, adherence to standards, etc. coverage analyzers - these tools check which parts of the code have been exercised by a test, and may be oriented to code statement coverage, condition coverage, path coverage, etc. memory analyzers - such as bounds-checkers and leak detectors. load/performance test tools - for testing client/server and web applications under various load levels. web test tools - to check that links are valid, HTML code usage is correct, client-side and server-side programs work, a web site's interactions are secure. other tools - for test case management, documentation management, bug reporting, and configuration management.

151. What's the difference between black box and white box testing?
Black-box and white-box are test design methods. Black-box test design treats the system as a “black-box”, so it doesn't explicitly use knowledge of the internal structure. Black-box test design is usually described as focusing on testing functional requirements. Synonyms for black-box include: behavioral, functional, opaque-box, and closed-box. White-box test design allows one to peek inside the “box”, and it focuses specifically on using internal knowledge of the software to guide the selection of test data. Synonyms for white-box include: structural, glass-box and clear-box. While black-box and white-box are terms that are still in popular use, many people prefer the terms 'behavioral' and 'structural'. Behavioral test design is slightly different from black-box test design because the use of internal knowledge isn't strictly forbidden, but it's still discouraged. In practice, it hasn't proven useful to use a single test design method. One has to use a mixture of different methods so that they aren't hindered by the limitations of a particular one. Some call this 'gray-box' or 'translucent-box' test design, but others wish we'd stop talking about boxes altogether.It is important to understand that these methods are used during the test design phase, and their influence is hard to see in the tests once they're implemented. Note that any level of testing (unit testing, system testing, etc.) can use any test design methods. Unit testing is usually associated with structural test design, but this is because testers usually don't have well-defined requirements at the unit level to validate.

152. What kinds of testing should be considered?
Black box testing - not based on any knowledge of internal design or code. Tests are based on requirements and functionality. White box testing - based on knowledge of the internal logic of an application's code. Tests are based on coverage of code statements, branches, paths, conditions.unit testing - the most 'micro' scale of testing; to test particular functions or code modules. Typically done by the programmer and not by testers, as it requires detailed knowledge of the internal program design and code. Not always easily done unless the application has a well-designed architecture with tight code; may require developing test driver modules or test harnesses. incremental integration testing - continuous testing of an application as new functionality is added; requires that various aspects of an application's functionality be independent enough to work separately before all parts of the program are completed, or that test drivers be developed as needed; done by programmers or by testers. integration testing - testing of combined parts of an application to determine if they function together correctly. The 'parts' can be code modules, individual applications, client and server applications on a network, etc. This type of testing is especially relevant to client/server and distributed systems. functional testing - black-box type testing geared to functional requirements of an application; this type of testing should be done by testers. This doesn't mean that the programmers shouldn't check that their code works before releasing it (which of course applies to any stage of testing.) system testing - black-box type testing that is based on overall requirements specifications; covers all combined parts of a system. end-to-end testing - similar to system testing; the 'macro' end of the test scale; involves testing of a complete application environment in a situation that mimics real-world use, such as interacting with a database, using network communications, or interacting with other hardware, applications, or systems if appropriate. sanity testing or smoke testing - typically an initial testing effort to determine if a new software version is performing well enough to accept it for a major testing effort. For example, if the new software is crashing systems every 5 minutes, bogging down systems to a crawl, or corrupting databases, the software may not be in a 'sane' enough condition to warrant further testing in its current state. regression testing - re-testing after fixes or modifications of the software or its environment. It can be difficult to determine how much re-testing is needed, especially near the end of the development cycle. Automated testing tools can be especially useful for this type of testing. acceptance testing - final testing based on specifications of the end-user or customer, or based on use by end-users/customers over some limited period of time. load testing - testing an application under heavy loads, such as testing of a web site under a range of loads to determine at what point the system's response time degrades or fails.stress testing - term often used interchangeably with 'load' and 'performance' testing. Also used to describe such tests as system functional testing while under unusually heavy loads, heavy repetition of certain actions or inputs, input of large numerical values, large complex queries to a database system, etc. performance testing - term often used interchangeably with 'stress' and 'load' testing. Ideally 'performance' testing (and any other 'type' of testing) is defined in requirements documentation or QA or Test Plans.usability testing - testing for 'user-friendliness'. Clearly this is subjective, and will depend on the targeted end-user or customer. User interviews, surveys, video recording of user sessions, and other techniques can be used. Programmers and testers are usually not appropriate as usability testers. install/uninstall testing - testing of full, partial, or upgrade install/uninstall processes. recovery testing - testing how well a system recovers from crashes, hardware failures, or other catastrophic problems. failover testing - typically used interchangeably with 'recovery testing'security testing - testing how well the system protects against unauthorized internal or external access, willful damage, etc; may require sophisticated testing techniques. compatibility testing - testing how well software performs in a particular hardware/software/operating system/network/etc. environment. exploratory testing - often taken to mean a creative, informal software test that is not based on formal test plans or test cases; testers may be learning the software as they test it. ad-hoc testing - similar to exploratory testing, but often taken to mean that the testers have significant understanding of the software before testing it. context-driven testing - testing driven by an understanding of the environment, culture, and intended use of software. For example, the testing approach for life-critical medical equipment software would be completely different than that for a low-cost computer game. user acceptance testing - determining if software is satisfactory to an end-user or customer. comparison testing - comparing software weaknesses and strengths to competing products. alpha testing - testing of an application when development is nearing completion; minor design changes may still be made as a result of such testing. Typically done by end-users or others, not by programmers or testers. beta testing - testing when development and testing are essentially completed and final bugs and problems need to be found before final release. Typically done by end-users or others, not by programmers or testers. mutation testing - a method for determining if a set of test data or test cases is useful, by deliberately introducing various code changes ('bugs') and retesting with the original test data/cases to determine if the 'bugs' are detected. Proper implementation requires large computational resources.

151. Why is it often hard for management to get serious about quality assurance?
Solving problems is a high-visibility process; preventing problems is low-visibility.This is illustrated by an old parable:In ancient China there was a family of healers, one of whom was known throughout the land and employed as a physician to a great lord. The physician was asked which of his family was the most skillful healer. He replied, "I tend to the sick and dying with drastic and dramatic treatments, and on occasion someone is cured and my name gets out among the lords.""My elder brother cures sickness when it just begins to take root, and his skills are known among the local peasants and neighbors." "My eldest brother is able to sense the spirit of sickness and eradicate it before it takes form. His name is unknown outside our home."

152. Why does software have bugs?
1. Miscommunication or no communication - as to specifics of what an application should or shouldn't do (the application's requirements). 2. Software complexity - the complexity of current software applications can be difficult to comprehend for anyone without experience in modern-day software development. Multi-tiered applications, client-server and distributed applications, data communications, enormous relational databases, and sheer size of applications have all contributed to the exponential growth in software/system complexity. programming errors - programmers, like anyone else, can make mistakes. 3. Changing requirements (whether documented or undocumented) - the end-user may not understand the effects of changes, or may understand and request them anyway - redesign, rescheduling of engineers, effects on other projects, work already completed that may have to be redone or thrown out, hardware requirements that may be affected, etc. If there are many minor changes or any major changes, known and unknown dependencies among parts of the project are likely to interact and cause problems, and the complexity of coordinating changes may result in errors. Enthusiasm of engineering staff may be affected. In some fast-changing business environments, continuously modified requirements may be a fact of life. In this case, management must understand the resulting risks, and QA and test engineers must adapt and plan for continuous extensive testing to keep the inevitable bugs from running out of control. 3. Poorly documented code - it's tough to maintain and modify code that is badly written or poorly documented; the result is bugs. In many organizations management provides no incentive for programmers to document their code or write clear, understandable, maintainable code. In fact, it's usually the opposite: they get points mostly for quickly turning out code, and there's job security if nobody else can understand it ('if it was hard to write, it should be hard to read'). 4. software development tools - visual tools, class libraries, compilers, scripting tools, etc. often introduce their own bugs or are poorly documented, resulting in added bugs.

153. How can new Software QA processes be introduced in an existing organization?
A lot depends on the size of the organization and the risks involved. For large organizations with high-risk (in terms of lives or property) projects, serious management buy-in is required and a formalized QA process is necessary. Where the risk is lower, management and organizational buy-in and QA implementation may be a slower, step-at-a-time process. QA processes should be balanced with productivity so as to keep bureaucracy from getting out of hand. For small groups or projects, a more ad-hoc process may be appropriate, depending on the type of customers and projects. A lot will depend on team leads or managers, feedback to developers, and ensuring adequate communications among customers, managers, developers, and testers. The most value for effort will often be in (a) requirements management processes, with a goal of clear, complete, testable requirement specifications embodied in requirements or design documentation, or in 'agile'-type environments extensive continuous coordination with end-users, (b) design inspections and code inspections, and (c) post-mortems/retrospectives.

154. how do the companies expect the defect reporting to be communicated by the tester to the development team. Can the excel sheet template be used for defect reporting. If so what are the common fields that are to be included ? who assigns the priority and severity of the defect
To report bugs in excel: Sno. Module Screen/ Section Issue detail SeverityPrioriety Issue statusthis is how to report bugs in excel sheet and also set filters on the Columns attributes.But most of the companies use the share point process of reporting bugs In this when the project came for testing a module wise detail of project is inserted to the defect managment system they are using. It contains following field1. Date2. Issue brief3. Issue discription(used for developer to regenerate the issue)4. Issue status( active, resolved, on hold, suspend and not able to regenerate)5. Assign to (Names of members allocated to project)6. Prioriety(High, medium and low)7. severity (Major, medium and low) Please article entitled "Bug Tracking Basics" How do I track a defect? What tool should I use to track defects?http://link.fyicenter.com/view.php?ID=761How to Report Bugs Effectively http://link.fyicenter.com/view.php?ID=762A Bug's Life Cyclehttp://link.fyicenter.com/view.php?ID=763Problem Management Tools Summaryhttp://link.fyicenter.com/view.php?ID=328Defect Tracking Toolshttp://link.fyicenter.com/view.php?ID=764
155. What are the tables in testplans and testcases?
Test plan is a document that contains the scope, approach, test design and test strategies. It includes the following:-1. Test case identifier2. Scope3.Features to be tested4. Features not to be tested.5. Test strategy.6. Test Approach7. Test Deliverables8. Responsibilities.9 Staffing and Training10.Risk and Contingencies11. ApprovalWhile A test case is a noted/documented set of steps/activities that are carried out or executed on the software in order to confirm its functionality/behavior to certain set of inputs.

156. What are the table contents in testplans and test cases?
Test Plan is a document which is prepared with the details of the testing priority. A test Plan generally includes: 1. Objective of Testing2. Scope of Testing3. Reason for testing4. Timeframe5. Environment6. Entrance and exit criteria7. Risk factors involved8. Deliverables

157. What automating testing tools are you familiar with?
Win Runner , Load runner, QTP , Silk Performer, Test director, Rational robot, QA run.

158. How did you use automating testing tools in your job?
1. For regression testing2. Criteria to decide the condition of a particular build3. Describe some problem that you had with automating testing tool.The problem of winrunner identifying the third party controls like infragistics control.

159. How do you plan test automation?
1. Prepare the automation Test plan2. Identify the scenario3. Record the scenario4. Enhance the scripts by inserting check points and Conditional Loops5. Incorporated Error Handler6. Debug the script7. Fix the issue8. Rerun the script and report the result.

160. Can test automation improve test effectiveness?
Yes, Automating a test makes the test process:1.Fast2.Reliable3. Repeatable4.Programmable5.Reusable6.Comprehensive6. What is data - driven automation?Testing the functionality with more test cases becomes laborious as the functionality grows. For multiple sets of data (test cases), you can execute the test once in which you can figure out for which data it has failed and for which data, the test has passed. This feature is available in the WinRunner with the data driven test where the data can be taken from an excel sheet or notepad.

161. What are the main attributes of test automation?
software test automation attributes :Maintainability - the effort needed to update the test automation suites for each new releaseReliability - the accuracy and repeatability of the test automationFlexibility - the ease of working with all the different kinds of automation test wareEfficiency - the total cost related to the effort needed for the automationPortability - the ability of the automated test to run on different environmentsRobustness - the effectiveness of automation on an unstable or rapidly changing systemUsability - the extent to which automation can be used by different types of users

162. Does automation replace manual testing?
There can be some functionality which cannot be tested in an automated tool so we may have to do it manually. therefore manual testing can never be replaced. (We can write the scripts for negative testing also but it is hectic task).When we talk about real environment we do negative testing manually.

163. How will you choose a tool for test automation?
choosing of a tool defends on many things ...1. Application to be tested2. Test environment3. Scope and limitation of the tool.4. Feature of the tool.5. Cost of the tool.6. Whether the tool is compatible with your application which means tool should be able to interact with your application7. Ease of use

164. How you will evaluate the tool for test automation?
We need to concentrate on the features of the tools and how this could be benficial for our project. The additional new features and the enhancements of the features will also help.

165. What are main benefits of test automation?
FAST ,RELIABLE,COMPREHENSIVE,REUSABLE

166. What could go wrong with test automation?
1. The choice of automation tool for certain technologies 2. Wrong set of test automated

167. How you will describe testing activities?
Testing activities start from the elaboration phase. The various testing activities are preparing the test plan, Preparing test cases, Execute the test case, Log teh bug, validate the bug & take appropriate action for the bug, Automate the test cases.

168. What testing activities you may want to automate?
Automate all the high priority test cases which needs to be executed as a part of regression testing for each build cycle.

169. Describe common problems of test automation.
The common problems are:1. Maintenance of the old script when there is a feature change or enhancement2. The change in technology of the application will affect the old scripts

170. What types of scripting techniques for test automation do you know?
5 types of scripting techniques:LinearStructuredSharedData DrivenKey Driven

171. What are principles of good testing scripts for automation?
1. Proper code guiding standards2. Standard format for defining functions, exception handler etc3. Comments for functions4. Proper errorhandling mechanisms5. The appropriate synchronization techniques18. What tools are available for support of testing during software development life cycle?Testing tools for regression and load/stress testing for regression testing like, QTP, load runner, rational robot, winrunner, silk, test complete, Astra are available in the market. -For defect tracking BugZilla, Test Runner are available.

172. Can the activities of test case design be automated?
As I know it, test case design is about formulating the steps to be carried out to verify something about the application under test. And this cannot be automated. IHowever, I agree that the process of putting the test results into the excel sheet.

173. What are the limitations of automating software testing?
Hard-to-create environments like “out of memory”, “invalid input/reply”, and “corrupt registry entries” make applications behave poorly and existing automated tools can’t force these condition - they simply test your application in “normal” environment.

174. What skills needed to be a good test automator?
1.Good Logic for programming.2. Analytical sklls.3.Pessimestic in Nature.

175. How to find that tools work well with your existing system?
1. Discuss with the support officials2. Download the trial version of the tool and evaluate3. Get suggestions from people who are working on the tool

176. Describe some problem that you had with automating testing tool
1. The inability of winrunner to identify the third party control like infragistics controls2. The change of the location of the table object will cause object not found error.3. The inability of the winrunner to execute the script against multiple langauges

177. What are the main attributes of test automation?
Maintainability, Reliability, Flexibility, Efficiency, Portability, Robustness, and Usability - these are the main attributes in test automation.

178. What testing activities you may want to automate in a project?
Testing tools can be used for :* Sanity tests(which is repeated on every build),* stress/Load tests(U simulate a large no of users,which is manually impossible) &* Regression tests(which are done after every code change)

179. How to find that tools work well with your existing system?
To find this, select the suite of tests which are most important for your application. First run them with automated tool. Next subject the same tests to careful manual testing. If the results are coinciding you can say your testing tool has been performing.

180. How will you test the field that generates auto numbers of AUT when we click the button 'NEW" in the application?
We can create a textfile in a certain location, and update the auto generated value each time we run the test and compare the currently generated value with the previous one will be one solution.

181. How will you evaluate the fields in the application under test using automation tool?
We can use Verification points(rational Robot) to validate the fields .Ex.Using objectdata,objectdata properties VP we can validate fields.

182. Can we perform the test of single application at the same time using different tools on the same machine?
No. The Testing Tools will be in the ambiguity to determine which browser is opened by which tool.

183. Difference between Web application Testing and Client Server Testing. State the different types for Web application Testing and Client Server Testing types?
which winrunner 7.2 versioncompatiable with internet explorer, firefox,n.n

184. What is 'configuration management'?
Configuration management is a process to control and document any changes made during the life of a project. Revision control, Change Control, and Release Control are important aspects of Configuration Management.

185. How to test the Web applications?
The basic difference in webtesting is here we have to test for URL's coverage and links coverage. Using WinRunner we can conduct webtesting. But we have to make sure that Webtest option is selected in "Add in Manager". Using WR we cannot test XML objects.

186. What are the problems encountered during the testing the application compatibility on different browsers and on different operating systems
Font issues,alignment issues

188. How exactly the testing the application compatibility on different browsers and on different operating systems is done
Please submit Your Suggestion to our forum at http://www.fyicenter.com

189. How testing is proceeded when SRS or any other docccument is not given?
If SRS is not there we can perform Exploratory testing. In Exploratory testing the basic module is executed and depending on its results, the next plan is executed.

190. How do we test for severe memory leakages ?
By using Endurance Testing . Endurance Testing means checking for memory leaks or other problems that may occur with prolonged execution.

191. What is the difference between quality assurance and testing?
Quality assurance involves the entire software development process and testing involves operation of a system or application to evaluate the results under certain conditions. QA is oriented to prevention and Testing is oriented to detection.

192. Why does software have bugs?
1.miscommunication2.programming errors3.time pressures.4.changing requirements5.software complexity

193. How do u do usability testing,security testing,installation testing,ADHOC,safety and smoke testing?
Please submit Your Suggestion to our forum at http://www.fyicenter.com

194. What is memory leaks and buffer overflows ?
Memory leaks means incomplete deallocation - are bugs that happen very often. Buffer overflow means data sent as input to the server that overflows the boundaries of the input area, thus causing the server to misbehave. Buffer overflows can be used.

195. what are the major differences between stress testing,load testing,Volume testing?
Stress testing means increasing the load ,and checking the performance at each level. Load testing means at a time giving more load by the expectation and checking the performance at that level. Volume testing means first we have to apply initial.

Software Quality Assurance Interview question Part-1

2010-01-26T09:07:00.000-08:00

1. What is Acceptance Testing?
Testing conducted to enable a user/customer to determine whether to accept a software product. Normally performed to validate the software meets a set of agreed acceptance criteria.

2. What is Accessibility Testing?
Verifying a product is accessible to the people having disabilities (deaf, blind, mentally disabled etc.).

3. What is Ad Hoc Testing?
A testing phase where the tester tries to 'break' the system by randomly trying the system's functionality. Can include negative testing as well. See also Monkey Testing.

4. What is Agile Testing?
Testing practice for projects using agile methodologies, treating development as the customer of testing and emphasizing a test-first design paradigm. See also Test Driven Development.

5. What is Application Binary Interface (ABI)?
A specification defining requirements for portability of applications in binary forms across different system platforms and environments.

6. What is Application Programming Interface (API)?
A formalized set of software calls and routines that can be referenced by an application program in order to access supporting system or network services.

7. What is Automated Software Quality (ASQ)?
The use of software tools, such as automated testing tools, to improve software quality.

8. What is Automated Testing?
Testing employing software tools which execute tests without manual intervention. Can be applied in GUI, performance, API, etc. testing. The use of software to control the execution of tests, the comparison of actual outcomes to predicted outcomes, the setting up of test preconditions, and other test control and test reporting functions.

9. What is Backus-Naur Form?
A metalanguage used to formally describe the syntax of a language.

10. What is Basic Block?
A sequence of one or more consecutive, executable statements containing no branches.

11. What is Basis Path Testing?
A white box test case design technique that uses the algorithmic flow of the program to design tests.

12. What is Basis Set?
The set of tests derived using basis path testing.

13. What is Baseline?
The point at which some deliverable produced during the software engineering process is put under formal change control.

14. What is Beta Testing?
Testing of a rerelease of a software product conducted by customers.

15. What is Binary Portability Testing?
Testing an executable application for portability across system platforms and environments, usually for conformation to an ABI specification.

16. What is Black Box Testing?
Testing based on an analysis of the specification of a piece of software without reference to its internal workings. The goal is to test how well the component conforms to the published requirements for the component.

17. What is Bottom Up Testing?
An approach to integration testing where the lowest level components are tested first, then used to facilitate the testing of higher level components. The process is repeated until the component at the top of the hierarchy is tested.

18. What is Boundary Testing?
Test which focus on the boundary or limit conditions of the software being tested. (Some of these tests are stress tests).

19. What is Bug?
A fault in a program which causes the program to perform in an unintended or unanticipated manner.

20. What is Defect?
If software misses some feature or function from what is there in requirement it is called as defect.

21. What is Boundary Value Analysis?
BVA is similar to Equivalence Partitioning but focuses on "corner cases" or values that are usually out of range as defined by the specification. his means that if a function expects all values in range of negative 100 to positive 1000, test inputs would include negative 101 and positive 1001.

22. What is Branch Testing?
Testing in which all branches in the program source code are tested at least once.

23. What is Breadth Testing?
A test suite that exercises the full functionality of a product but does not test features in detail.

24. What is CAST?
Computer Aided Software Testing.

25. What is Capture/Replay Tool?
A test tool that records test input as it is sent to the software under test. The input cases stored can then be used to reproduce the test at a later time. Most commonly applied to GUI test tools.

26. What is CMM?
The Capability Maturity Model for Software (CMM or SW-CMM) is a model for judging the maturity of the software processes of an organization and for identifying the key practices that are required to increase the maturity of these processes.

27. What is Cause Effect Graph?
A graphical representation of inputs and the associated outputs effects which can be used to design test cases.

28. What is Code Complete?
Phase of development where functionality is implemented in entirety; bug fixes are all that are left. All functions found in the Functional Specifications have been implemented.

29. What is Code Coverage?
An analysis method that determines which parts of the software have been executed (covered) by the test case suite and which parts have not been executed and therefore may require additional attention.

30. What is Code Inspection?
A formal testing technique where the programmer reviews source code with a group who ask questions analyzing the program logic, analyzing the code with respect to a checklist of historically common programming errors, and analyzing its compliance with coding standards.

31. What is Code Walkthrough?
A formal testing technique where source code is traced by a group with a small set of test cases, while the state of program variables is manually monitored, to analyze the programmer's logic and assumptions.

32. What is Coding?
The generation of source code.

33. What is Compatibility Testing?
Testing whether software is compatible with other elements of a system with which it should operate, e.g. browsers, Operating Systems, or hardware.

34. What is Component?
A minimal software item for which a separate specification is available.

35. What is Component Testing?
Testing of individual software components (Unit Testing).

36. What is Concurrency Testing?
Multi-user testing geared towards determining the effects of accessing the same application code, module or database records. Identifies and measures the level of locking, deadlocking and use of single-threaded code and locking semaphores.

37. What is Conformance Testing?
The process of testing that an implementation conforms to the specification on which it is based. Usually applied to testing conformance to a formal standard.

38. What is Context Driven Testing?
The context-driven school of software testing is flavor of Agile Testing that advocates continuous and creative evaluation of testing opportunities in light of the potential information revealed and the value of that information to the organization right now.

39. What is Conversion Testing?
Testing of programs or procedures used to convert data from existing systems for use in replacement systems.

40. What is Cyclomatic Complexity?
A measure of the logical complexity of an algorithm, used in white-box testing.

41. What is Data Dictionary?
A database that contains definitions of all data items defined during analysis.

42. What is Data Flow Diagram?
A modeling notation that represents a functional decomposition of a system.

43. What is Data Driven Testing?
Testing in which the action of a test case is parameterized by externally defined data values, maintained as a file or spreadsheet. A common technique in Automated Testing.

44. What is Debugging?
The process of finding and removing the causes of software failures.

45. What is Defect?
Nonconformance to requirements or functional / program specification

46. What is Dependency Testing?
Examines an application's requirements for pre-existing software, initial states and configuration in order to maintain proper functionality.

47. What is Depth Testing?
A test that exercises a feature of a product in full detail.

48. What is Dynamic Testing?
Testing software through executing it. See also Static Testing.

49. What is Emulator?
A device, computer program, or system that accepts the same inputs and produces the same outputs as a given system.

50. What is Endurance Testing?
Checks for memory leaks or other problems that may occur with prolonged execution.

51. What is End-to-End testing?
Testing a complete application environment in a situation that mimics real-world use, such as interacting with a database, using network communications, or interacting with other hardware, applications, or systems if appropriate.

52. What is Equivalence Class?
A portion of a component's input or output domains for which the component's behaviour is assumed to be the same from the component's specification.

53. What is Equivalence Partitioning?
A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes.

54. What is Exhaustive Testing?
Testing which covers all combinations of input values and preconditions for an element of the software under test.

55. What is Functional Decomposition?
A technique used during planning, analysis and design; creates a functional hierarchy for the software.

56. What is Functional Specification?
A document that describes in detail the characteristics of the product with regard to its intended features.

57. What is Functional Testing?
Testing the features and operational behavior of a product to ensure they correspond to its specifications. Testing that ignores the internal mechanism of a system or component and focuses solely on the outputs generated in response to selected inputs and execution conditions. or Black Box Testing.

58. What is Glass Box Testing?
A synonym for White Box Testing.

59. What is Gorilla Testing?
Testing one particular module, functionality heavily.

60. What is Gray Box Testing?
A combination of Black Box and White Box testing methodologies? testing a piece of software against its specification but using some knowledge of its internal workings.

61. What is High Order Tests?
Black-box tests conducted once the software has been integrated.

62. What is Independent Test Group (ITG)?
A group of people whose primary responsibility is software testing,

63. What is Inspection?
A group review quality improvement process for written material. It consists of two aspects; product (document itself) improvement and process improvement (of both document production and inspection).

64. What is Integration Testing?
Testing of combined parts of an application to determine if they function together correctly. Usually performed after unit and functional testing. This type of testing is especially relevant to client/server and distributed systems.

65. What is Installation Testing?
Confirms that the application under test recovers from expected or unexpected events without loss of data or functionality. Events can include shortage of disk space, unexpected loss of communication, or power out conditions.

67. What is Load Testing?
See Performance Testing.

68. What is Localization Testing?
This term refers to making software specifically designed for a specific locality.

69. What is Loop Testing?
A white box testing technique that exercises program loops.

70. What is Metric?
A standard of measurement. Software metrics are the statistics describing the structure or content of a program. A metric should be a real objective measurement of something such as number of bugs per lines of code.

71. What is Monkey Testing?
Testing a system or an Application on the fly, i.e just few tests here and there to ensure the system or an application does not crash out.

72. What is Negative Testing?
Testing aimed at showing software does not work. Also known as "test to fail". See also Positive Testing.

73. What is Path Testing?
Testing in which all paths in the program source code are tested at least once.

74. What is Performance Testing?
Testing conducted to evaluate the compliance of a system or component with specified performance requirements. Often this is performed using an automated test tool to simulate large number of users. Also know as "Load Testing".

75. What is Positive Testing?
Testing aimed at showing software works. Also known as "test to pass". See also Negative Testing.

76. What is Quality Assurance?
All those planned or systematic actions necessary to provide adequate confidence that a product or service is of the type and quality needed and expected by the customer.

77. What is Quality Audit?
A systematic and independent examination to determine whether quality activities and related results comply with planned arrangements and whether these arrangements are implemented effectively and are suitable to achieve objectives.

78. What is Quality Circle?
A group of individuals with related interests that meet at regular intervals to consider problems or other matters related to the quality of outputs of a process and to the correction of problems or to the improvement of quality.

79. What is Quality Control?
The operational techniques and the activities used to fulfill and verify requirements of quality.

80. What is Quality Management?
That aspect of the overall management function that determines and implements the quality policy.

81. What is Quality Policy?
The overall intentions and direction of an organization as regards quality as formally expressed by top management.

82. What is Quality System?
The organizational structure, responsibilities, procedures, processes, and resources for implementing quality management.

83. What is Race Condition?
A cause of concurrency problems. Multiple accesses to a shared resource, at least one of which is a write, with no mechanism used by either to moderate simultaneous access.

84. What is Ramp Testing?
Continuously raising an input signal until the system breaks down.

85. What is Recovery Testing?
Confirms that the program recovers from expected or unexpected events without loss of data or functionality. Events can include shortage of disk space, unexpected loss of communication, or power out conditions.

86. What is Regression Testing?
Retesting a previously tested program following modification to ensure that faults have not been introduced or uncovered as a result of the changes made.

87. What is Release Candidate?
A pre-release version, which contains the desired functionality of the final version, but which needs to be tested for bugs (which ideally should be removed before the final version is released).

88. What is Sanity Testing?
Brief test of major functional elements of a piece of software to determine if its basically operational. See also Smoke Testing.

89. What is Scalability Testing?
Performance testing focused on ensuring the application under test gracefully handles increases in work load.

90. What is Security Testing?
Testing which confirms that the program can restrict access to authorized personnel and that the authorized personnel can access the functions available to their security level.

91. What is Smoke Testing?
A quick-and-dirty test that the major functions of a piece of software work. Originated in the hardware testing practice of turning on a new piece of hardware for the first time and considering it a success if it does not catch on fire.

92. What is Soak Testing?
Running a system at high load for a prolonged period of time. For example, running several times more transactions in an entire day (or night) than would be expected in a busy day, to identify and performance problems that appear after a large number of transactions have been executed.

93. What is Software Requirements Specification?
A deliverable that describes all data, functional and behavioral requirements, all constraints, and all validation requirements for software/

94. What is Software Testing?
A set of activities conducted with the intent of finding errors in software.

95. What is Static Analysis?
Analysis of a program carried out without executing the program.

96. What is Static Analyzer?
A tool that carries out static analysis.

97. What is Static Testing?
Analysis of a program carried out without executing the program.

98. What is Storage Testing?
Testing that verifies the program under test stores data files in the correct directories and that it reserves sufficient space to prevent unexpected termination resulting from lack of space. This is external storage as opposed to internal storage.

99. What is Stress Testing?
Testing conducted to evaluate a system or component at or beyond the limits of its specified requirements to determine the load under which it fails and how. Often this is performance testing using a very high level of simulated load.

100. What is Structural Testing?
Testing based on an analysis of internal workings and structure of a piece of software. See also White Box Testing.

101. What is System Testing?
Testing that attempts to discover defects that are properties of the entire system rather than of its individual components.

102. What is Testability?
The degree to which a system or component facilitates the establishment of test criteria and the performance of tests to determine whether those criteria have been met.

103. What is Testing?
The process of exercising software to verify that it satisfies specified requirements and to detect errors. The process of analyzing a software item to detect the differences between existing and required conditions (that is, bugs), and to evaluate the features of the software item (Ref. IEEE Std 829). The process of operating a system or component under specified conditions, observing or recording the results, and making an evaluation of some aspect of the system or component. What is Test Automation? It is the same as Automated Testing.