•Needs judgement to decide the severity and priority of an issue found in testing •Question has 10 scenarios •Classify the severity (S1 through S4) and priority (P1 through P4) •Justify your determination in one or two complete sentences –Document any assumptionsYou are testing new company web page. The owner requested that the logo be on the front page. It is but is squashed in the top left corner and very distorted.The password reset functions uses the last four digits of a student’s social security number as an authentication code.You are testing a Web site and the buttons to go to the various pages are very small, close together, and difficult to click on.In the e-commerce application, you click in the Order button and it does not show the user that the order has been placed or not.The order allow for 10 items to be entered but the user is only charged for 1.The search of the product catalog on the e-commerce site finds items when you enter the singular term but nit the plural (e.g. boot but not boots).You are testing a multi-player game that has a scoreboard to show the ranking of all the players. You name appears correctly on the scoreboard at the end of the game but does not appear the next time that you log in.You are testing a Spanish version of the application, and one of the error message appears in English.You are testing the changes to the company web site and a video has been added. It is very large and pushes important text so that the user has to scroll down for the information.The program crashes after running it several tomes on a laptop. You suspect that there is a memory leak.
it355unit09.pptx
Unformatted Attachment Preview
IT355
Unit 9 – Test Management
Spring 2017
Dr Diane Murphy
4/16/2017
1
Test Management
• Need to first ensure that as many bugs as
possible are fixed in the time allowed and with
the resource allocated
• This information is documented in the Test
Report
• Bugs are fixed by the developer
• The tester must provide sufficient information
for the developer to know what the problem
is and where in the code it might occur
4/16/2017
2
Reason Given for Not Fixing Bugs
•
•
•
•
•
There is not enough time
It is not really a bug
It is too risky to fix
It is not worth it
Ineffective bug reporting
Principles for Reporting a Bug
•
•
•
•
•
•
Report bugs as soon as possible
Effectively describe the bugs
Be nonjudgmental in reporting bugs
Follow-up on your bug reports
Make sure they are obvious and reproducible
Classify severity and priority
Time to Find Bugs
Isolating and Reproducing Bugs
• Do not take anything for granted
• Look for time-dependent and race condition
problems
• White—box issues for boundary condition bugs,
memory leaks, and data over flows can be slow
to show reveal themselves
• State bugs show up only in certain states of the
software
• Consider resource dependencies and interactions
with memory, network, and hardware sharing
• Do not ignore the hardware
Simple Bugs Life Cycle
Generic Bug Life Cycle
Bug Tracking
• Process that requires:
– A lot of information
– High level of detail
– Discipline
• Need to log bugs as soon as they are found
and monitor them through the lifecycle
• Bug tracking system important tool to
streamline the process
• Need to classify the bugs
Severity
• Critical (S1): The defect affects critical functionality or critical
data. It does not have a workaround. Example: Unsuccessful
installation, complete failure of a feature.
• Major (S2): The defect affects major functionality or major
data. It has a workaround but is not obvious and is difficult.
Example: A feature is not functional from one module but
the task is doable if 10 complicated indirect steps are
followed in another module/s.
• Minor : The defect affects minor functionality or non-critical
data. It has an easy workaround. Example: A minor feature
that is not functional in one module but the same task is
easily doable from another module.
• Trivial: The defect does not affect functionality or data. It
does not even need a workaround. It does not impact
productivity or efficiency. It is merely an inconvenience.
Example: Petty layout discrepancies, spelling/grammatical
errors
Priority
•
•
•
•
Priority 1 – Critical (P1): This has to be fixed immediately within 24 hours. This
generally occurs in cases when an entire functionality is blocked and no testing can
proceed as a result of this. Or in certain other cases if there are significant memory
leaks, then generally the defect is classified as a priority -1 meaning the program/
feature is unusable in the current state.
Priority 2 – High (P2): Once the critical defects have been fixed, a defect having
this priority is the next candidate which has to be fixed for any test activity to
match the “exit” criteria. Normally when a feature is not usable as it’s supposed to
be, due to a program defect, or that a new code has to be written or sometimes
even because some environmental problem has to be handled through the code, a
defect may qualify for a priority 2.
Priority 3 – Medium (P3): A defect with this priority must be in contention to be
fixed as it could also deal with functionality issues which are not as per
expectation. Sometimes even cosmetic errors such as expecting the right error
message during the failure could qualify to be a priority 3 defect.
Priority 4 – Low (P4): A defect with low priority indicates that there is definitely an
issue, but it doesn’t have to be fixed to match the “exit” criteria. Typically, some
typing errors or even cosmetic errors as discussed previously could be categorized
in here. Sometimes defects with priority low are also opened to suggest some
enhancements in the existing design or a request to implement a small feature to
enhance user experience.
Getting Bugs Fixed
• Project manager or business owner must
determine
– What bugs get fixed when
– If bugs can be left until after the release
• Severity and priority are the two main
considerations:
– Critical items must be fixed
– High priority items must be fixed
• Pressure from customers, managers,
marketers, etc. to release on schedule
4/16/2017
12
Impact of Buggy Releases
• Most recently see vulnerability with airlines
– Delta (January 2017)
– United (January 2017)
– Southwest (July 2016)
• Gil Hecht, Continuity Software, said more
testing would reduce outages, but expensive
• He compared the construction of complex
computer systems to a layer cake, with Web
servers, database software, storage and
possibly interaction with other
4/16/2017
13
Quiz 4
• Needs judgement to decide the severity and
priority of an issue found in testing
• Quiz has 10 scenarios
• Classify the severity (S1 through S4) and
priority (P1 through P4)
• Justify your determination in onw or two
complete sentences
– Document any assumptions
4/16/2017
14
Test Reporting
• Two types of functional tests
– Black box
– White Box
• Different information for each
• Black box
– Specific tests
• White box
– Review code against the requirements
4/16/2017
15
Activity 9
• We have previously developed black box tests
for the flag application
– Complete these test
– Download program, will not run in Canvas
• Web application so we can see the code
– Check calculatiins by reviewing the
HTML/Javascript code
• Put all results in one spreadshett, different
worksheets
4/16/2017
16
…
Purchase answer to see full
attachment
Recent Comments