7/25/2019 Bug Edits Assign

1/9

Copyright (c) 1994-2004 Cem Kaner. 1

Software Testing 1

CSE 3411 SWE 5411

Assignment #1

Replicate and Edit Bugs

7/25/2019 Bug Edits Assign

2/9

Copyright (c) 1994-2004 Cem Kaner. 2

Editing Bugs

The purpose of this assignment is to give you experience eiting !ugs "ritten !y otherpeop#e. This tas$ "i## give you practice thin$ing a!out "hat a professiona# report shou#!e% !efore you start entering your o"n reports into this pu!#ic system.

Work with the current version of Open Office Calc

Join the QA project, use your F! e"ail a##ress$

%ea# the instructions at http&''(a$openoffice$or)'issue*han#lin)'project*issues$ht"l an#http&''(a$openoffice$or)'servlets'+rojectssues$ %ea# the u) entry )ui#elines athttp&''(a$openoffice$or)'issue*han#lin)'u)*writin)*)ui#elines$ht"l$

Fin# - u) reports in ssue !racker aout prole"s with Open Office Calc that appear tohave not yet een in#epen#ently verifie#$ !hese are liste# in the #ataase as .unconfir"e#/$f you search y project, you mayfin# relevant u)s in the sc project 0sprea#sheet,#ocu"entation project, #a 0#ataase, api 0application pro)ra""in) interface, an# ui 0userinterface$

For each report, review an# replicate the u), an# a## co""ents as appropriate in theA##itional Co""ents fiel# to the report on issueilla$

!he assi)n"ent that you su"it to meshoul# list the u) nu"ers$ will rea# the co""entsyou file# 0if any on the u) report$ n a##ition, for each u), tell "e what was #one well,what was #one poorly an# what was "issin) that shoul# have een there in the u) report$

http://qa.openoffice.org/issue_handling/project_issues.htmlhttp://qa.openoffice.org/servlets/ProjectIssueshttp://qa.openoffice.org/servlets/ProjectIssueshttp://qa.openoffice.org/issue_handling/project_issues.html

7/25/2019 Bug Edits Assign

3/9

Copyright (c) 1994-2004 Cem Kaner. 3

Editing Bugs

Assignment Procedure

&or each !ug' %eview the report for clarity an# tone 0see .first i"pressions/, ne4t sli#e$

nc#ue comments on c#arity an tone on the memo you sen me (!ut on*t ma$e thesecomments on the !ug report itse#f)

Atte"pt to replicate the u)$ +en comments to me on the rep#ication steps ("ere the ones in the report c#ear an

accurate)% your overa## impressions of the !ug report as a proceure escription% anescri!e any fo##o"-up tests that you "ou# recommen.

5ou "ay e#it the u) report yourself, pri"arily in the followin) ways$ , a comment inicating that you successfu##y rep#icate the !ug on configuration

in !ui#. , a comment escri!ing a simp#er set of rep#ication steps (if you have a simp#er set).

/a$e sure these are c#ear an accurate. , a comment escri!ing "hy this !ug "ou# !e important to customers (this is on#y

neee if the !ug #oo$s minor or #i$e it "on*t !e fixe. t is on#y usefu# if you $no" "hat

you are ta#$ing a!out). our comments shou# 3 appear critica# or isrespectfu# of the origina# report or ofthe person "ho "rote it. ou are aing information% not criticiing "hat "as there.

f you e#it the report in the #ataase, never change what the reporter has actually written$ 5ou arenot chan)in) his work, you are a##in) co""ents to it at the en# of the report

5our co""ents shoul# have your na"e an# the co""ent #ate, usually at the start of the co""ent, fore4a"ple& .0Ce" 6aner, 12'17'81 9ere is an alternative set of replication steps&/

7/25/2019 Bug Edits Assign

4/9

Copyright (c) 1994-2004 Cem Kaner. 7

Editing BugsFirst impressions

5 s the summary short (a!out 60-70 characters) an escriptive8

5 Can you unerstan the report8

As you rea# the #escription, #o you un#erstan# what the reporter

#i#:

Can you envision what the pro)ra" #i# in response: ;o you un#erstan# what the failure was:

5 s it o!vious "here to start ("hat state to !ring the program to) to

rep#icate the !ug8

5 s it o!vious "hat fi#es to use (if any)8 s it o!vious "hat you

"ou# type8

5 s the rep#ication seuence provie as a num!ere set of steps%

"hich te## you exact#y "hat to o an% "hen usefu#% "hat you "i##

see8

7/25/2019 Bug Edits Assign

5/9

Copyright (c) 1994-2004 Cem Kaner. -

Editing BugsFirst impressions

5 :oes the report inc#ue unnecessary information% persona#opinions or anecotes that seem out of p#ace8

5 s the tone of the report insu#ting8 ,re any "ors in the

report potentia##y insu#ting8

5 :oes the report seem too #ong8 Too short8 :oes it seem tohave a #ot of unnecessary steps8 (This is your firstimpression;you might !e mista$en. ,fter a##% you haven*trep#icate it yet. >K #i$e there*s a #ot ofexcess in the report8)

5 :oes the report seem over#y genera# (?nsert a fi#e an you

"i## see@ A "hat fi#e8 Bhat $in of fi#e8 s there an examp#e%

#i$e ?nsert a fi#e #i$e !#ah.foo or !#ah2.fee@8)

7/25/2019 Bug Edits Assign

6/9

Copyright (c) 1994-2004 Cem Kaner.