|
Server : Apache/2.4.62 System : FreeBSD fbsdweb2.web.rcn.net 14.1-RELEASE FreeBSD 14.1-RELEASE releng/14.1-n267679-10e31f0946d8 GENERIC amd64 User : www ( 80) PHP Version : 8.3.8 Disable Function : NONE Directory : /domains/srakitin/OLD/training/ |
Upload File : |
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
<html>
<head>
<meta http-equiv="Content-Type"
content="text/html; charset=iso-8859-1">
<title>Improving the Effectiveness of Testing</title>
</head>
<BODY>
<body bgcolor="#FFFFFF">
<!--- Logo and Page Title ---->
<p align="center">
<img src="../gif/logo2008.gif" width=348 height=64 border=0 alt="logo2008">
</p>
<p align="center">
<font color=black size=5 face=Verdana>
<b>Training</b> </font>
</p>
<p align="center">
<img src="../gif/topline.gif" width=915 height=6 border=0>
<br>
<font size="3" face="Verdana">
<p align="CENTER"><b>Improving the Effectiveness of Testing</b></font></p>
</center>
<center>
<table WIDTH=600>
<tr>
<td>
<p><font face="Verdana" size=2>
Many organizations have conflicting goals and objectives for testing
software. For example, some organizations believe the purpose of
testing is to show that the software works. We know from over three
decades of experience that testing can only be used to show
the presence of defects, not prove their absence.
<p>Further compounding the problem is a lack of understanding of the
levels of testing and the different methods that are appropriate at each
level as illustrated below:<br><br>
</td>
</tr>
</table>
</center>
<center>
<table border="1" cellpadding="7" cellspacing="1" width="636">
<tr>
<td valign="top" width="14%" bgcolor="#FFFF00">
<p align="center"><font face="Verdana" size="2"><b>Level</b></font></p>
</td>
<td valign="top" width="25%" bgcolor="#00FFFF">
<p align="center"><font face="Verdana" size="2"> <b>Objectives</b>
</font></p>
</td>
<td valign="top" width="17%" bgcolor="#00FFFF"><p
align="center"><font face="Verdana" size="2">
<b>Performed by</b></font></p>
</td>
<td valign="top" width="20%" bgcolor="#00FFFF"><p
align="center"><font face="Verdana" size="2">
<b>Environment</b></font></p>
</td>
<td valign="top" width="24%" bgcolor="#00FFFF"><p
align="center"><font face="Verdana" size="2"><b>Test Methods</b>
</font></p>
</td>
</tr>
<tr>
<td valign="top" width="14%" bgcolor="#FFFF00"><p
align="center"><font face="Verdana" size="2">
<b>Unit or Module Testing</b></font></p>
</td>
<td valign="top" width="25%"><font face="Verdana" size="2">
Verify logic, data, and algorithms in individual modules</font></td>
<td valign="top" width="17%"><font face="Verdana" size="2">
Software Engineering</font></td>
<td valign="top" width="20%"><font face="Verdana" size="2">
Isolated. </font></td>
<td valign="top" width="24%"><font face="Verdana" size="2">
White Box</font></td>
</tr>
<tr>
<td valign="top" width="14%" bgcolor="#FFFF00"><p
align="center"><font face="Verdana" size="2"><b>
Integration Testing</b></font></p>
</td>
<td valign="top" width="25%"><font face="Verdana" size="2">
Verify interfaces between modules</font></td>
<td valign="top" width="17%"><font face="Verdana" size="2">
Software Engineering</font></td>
<td valign="top" width="20%"><font face="Verdana" size="2">
Isolated and/or simulated. </font></td>
<td valign="top" width="24%"><font face="Verdana" size="2">
White Box, Top-down, Bottom-up, or Outside-in</font></td>
</tr>
<tr>
<td valign="top" width="14%" bgcolor="#FFFF00"><p
align="center"><font face="Verdana" size="2"><b>
Validation Testing</b></font></p>
</td>
<td valign="top" width="25%"><font face="Verdana" size="2">
Determine if the software meets requirements in SRS</font></td>
<td valign="top" width="17%"><font face="Verdana" size="2">
SQA or Software Validation Team</font></td>
<td valign="top" width="20%"><font face="Verdana" size="2">
Actual </font></td>
<td valign="top" width="24%"><font face="Verdana" size="2">
Functional, White Box, and Act-Like-A-Customer</font></td>
</tr>
<tr>
<td valign="top" width="14%" bgcolor="#FFFF00"><p
align="center"><font face="Verdana" size="2"><b>
Regression Testing</b></font></p>
</td>
<td valign="top" width="25%"><font face="Verdana" size="2">
Determine if software still meets requirements in light of bug fixes
or changes</font></td>
<td valign="top" width="17%"><font face="Verdana" size="2">
SQA or Software Validation Team</font></td>
<td valign="top" width="20%"><font face="Verdana" size="2">
Actual </font></td>
<td valign="top" width="24%"><font face="Verdana" size="2">
Functional and Act-Like-A-Customer</font></td>
</tr>
<tr>
<td valign="top" width="14%" bgcolor="#FFFF00"><p
align="center"><font face="Verdana" size="2"><b>
Acceptance Testing</b></font></p>
</td>
<td valign="top" width="25%"><font face="Verdana" size="2">
Determine if system meets customer requirements</font></td>
<td valign="top" width="17%"><font face="Verdana" size="2">
SQA or Software Validation Team</font></td>
<td valign="top" width="20%"><font face="Verdana" size="2">
Actual. Usually with customer present</font></td>
<td valign="top" width="24%"><font face="Verdana" size="2">
Functional and Act-Like-A-Customer</font></td>
</tr>
</table>
</center>
<br>
<center>
<table WIDTH=600>
<tr>
<td width=600>
<p align=left><font face="Verdana" font size="2" color=black>
One way to improve the effectiveness of testing involves using a test method
called <b>Act-Like-A-Customer testing </b> (or ALAC) which is based on the
following simple principle:<br><br>
<p>
</td>
</tr>
<tr>
<td>
<p align="center">
<img src="../gif/alac3.GIF" width=433 height=246 border=0>
</td>
</tr>
<tr>
<td width=600>
<p><font face="Verdana" font size="2">
By working with your Software QA staff, I can help them improve the
effectiveness of the tests they write by learning the technique of
<b>Act Like A Customer </b>testing. In this way, the tests they develop are
more likely to uncover problems your customers would likely find.
<p>Improving the effectiveness of testing helps improve Customer Satisfaction
and therefore provides a significant return on investment.<p>
</td>
</tr>
</table>
<br>
<table width=600>
<tr>
<td>
<font size=3 face="Verdana" color=Red>
<b>Tailoring</b>
<p>
</td>
</tr>
<tr>
<td width=20%>
<img src="../gif/tailor.JPG" width=101 height=97 hspace=0 vspace=0 border=0
align="center" alt="tailor">
</td>
<td width=80%>
<font size=2 face=Verdana font color=black>
This workshop can be tailored to meet your specific needs. <p>
This informal, interactive workshop is based, in part, on the book: <b>
<A HREF="../articles/summary.html">
Software Verification and Validation for Practitioners and Managers,</a></b>
by Steven R. Rakitin.
</TD>
</tr>
</TABLE>
</center>
<!--- bottom line -->
<br>
<p align="center">
<img src="../gif/bottomline.gif" width=915 height=6 border=0>
<br>
<!--- Contact Message -->
<center>
<br>
<p align="center">
<font size="3" color=Black face="Verdana">
<b>For further information,
<p>call Steve Rakitin at <font size="3" color=Red face="Verdana">508.529.4282</font>
<p><font size="3" color=Black face="Verdana">or e-mail him at
<a href="mailto:[email protected]"><b>[email protected]</a></b><p><br>
<!--- Bottom Row of Links -->
<center>
<TABLE BORDER=0 WIDTH=375>
<TR>
<TD VALIGN="TOP" >
<FONT FACE="Verdana" color=black SIZE=1>
<a href="../index.html"><b>Home</b></FONT></a></p>
</TD>
<TD VALIGN="TOP" >
<FONT FACE="Verdana" color=black SIZE=1>
<A HREF="/company/summary.html">
<P ALIGN="CENTER"><b>Company Info</b></FONT></a>
</TD>
<TD VALIGN="TOP" >
<FONT FACE="Verdana" color=black SIZE=1>
<A HREF="/company/contact.html">
<P ALIGN="CENTER"><b>Contact Info</b></FONT></a>
</TD>
</TR>
</TABLE>
</center>
<br>
<!-- Copyright -->
<p align="center"><font size="1" color=black face="Verdana">
Food for Thought and Predictable Software Development are trademarks of Software Quality Consulting, Inc.<br>
Copyright �2008 Software Quality Consulting, Inc. All rights reserved.<br>
<p>
Updated January 2008</font></p>
</body>
</html>