<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 08/12/11 21:09, Alex Lourie wrote:
<blockquote
cite="mid:CAKdn+_NuFLNSqC19P98LXbCgL4K9VabEen5rhM6Fq0x9XnZZ-A@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_quote">On Thu, Dec 8, 2011 at 7:57 PM, Gema
Gomez <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:gema.gomez-solano@canonical.com">gema.gomez-solano@canonical.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="HOEnZb">
<div class="h5">On 08/12/11 15:06, Alex Lourie wrote:<br>
> Hi all<br>
><br>
> Proceeding with the work we started for test case
rewriting, there's an<br>
> issue I'd like to discuss here - categorising the
test cases. How would<br>
> we like it to be? What categories would you think
should be created? How<br>
> do we decided the relation of a test case to a
specific category? Can<br>
> any given test be part of more than one categories?<br>
><br>
> Please share your thoughts,<br>
> Thanks.<br>
><br>
> --<br>
> Alex Lourie<br>
><br>
><br>
<br>
</div>
</div>
The categorization we have at the moment is:<br>
<br>
- Applications<br>
- System<br>
- Hardware<br>
- Install<br>
- Upgrade<br>
- CasesMods (not sure what this even means)<br>
<br>
There are many ways to categorize test cases:<br>
<br>
- by functionality under test (like we are sort of doing,
but not quite)<br>
<br>
- by test type<br>
* positive/negative<br>
* smoke: target the system horizontally and
superficially / regression:<br>
target vertical slices of the system, in depth<br>
* Unit testing (target an api method, or a very small<br>
functionality)/Integration testing (target the integration
of two or<br>
more subsystems)/System testing (target the system as a
whole)<br>
* Functional (target functionality, the system
behaves as it should and<br>
fails gracefully in error situations) / Non-Functional
(performance or<br>
benchmarking, security testing, fuzzy testing, load or
stress testing,<br>
compatibility testing, MTBF testing, etc)<br>
<br>
- by test running frequency: this test case should run<br>
daily/weekly/fortnightly/once per milestone<br>
<br>
<br>
And many other ways. I am deliberately introducing a lot of
jargon here,<br>
for those less familiar with the QA speech, please have a
look at the<br>
glossary or ask when in doubt, if we want to truly improve
the test<br>
cases we are writing we need to start thinking about all
these things:<br>
<a moz-do-not-send="true"
href="https://wiki.ubuntu.com/QATeam/Glossary"
target="_blank">https://wiki.ubuntu.com/QATeam/Glossary</a><br>
<br>
Thanks,<br>
Gema<br>
<font color="#888888"><br>
</font></blockquote>
<div><br>
</div>
<div>Hi Gema</div>
<div>That's OK, we can handle the jargon.</div>
<div><br>
</div>
<div>I think that in our case, categories should represent our
way of work. So for community team, current categories are
probably fine, but for QA engineering they may not be well
suited (you may want an additional manual/automatic note). I
don't think we should stumble on this issue for too long, so
I'd recommend to go with the following scheme, and update it
if we feel necessary. So it would go as this:</div>
<div><br>
</div>
<div>* <b>Applications</b> (for application related tests,
such as testing editors, browsers, etc).</div>
<div>* <b>System</b> (for testing system built ins, such as,
maybe, services scripts, global/local settings, default
system configurations, etc)</div>
<div>* <b>Hardware</b> (for testing hardware components)</div>
<div>* <b>Install</b> (for test cases performed during the
installation process)</div>
<div>* <b>Upgrade</b> (for test cases performed during the
upgrade process)</div>
<div><i>* CasesMods (I have no idea what it is right now, so
if anyone does please let us know).</i></div>
</div>
</div>
</blockquote>
Looking at the wiki, this is not in fact a separate category but
rather a page that holds information on cases which need to be
updated, suggestions for new cases, etc<br>
<blockquote
cite="mid:CAKdn+_NuFLNSqC19P98LXbCgL4K9VabEen5rhM6Fq0x9XnZZ-A@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_quote">
<div><br>
</div>
<div><br>
</div>
<div>I am going to use this selection on the Test Cases
Rewriting document, and if anything changes we'll update
accordingly.</div>
<div> </div>
</div>
-- <br>
Alex Lourie<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
</blockquote>
<br>
</body>
</html>