<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="/res/preview.xsl"?>
<rss version="2.0">
  <channel>
    <title>unit testing - citeseer query</title>
    <link>http://citeseer.ist.psu.edu/cs?q=unit&#37;20testing&amp;cs=1&amp;submit=Search+Documents&amp;af=Any&amp;ao=Date&amp;am=20</link>
    <description><![CDATA[unit testing - ResearchIndex document query]]></description>
    <lastBuildDate>Tue, 09 Feb 2010 13:36:35 GMT</lastBuildDate>
    <generator>Feed43 Proxy/1.0 (www.feed43.com)</generator>
    <ttl>360</ttl>

<item>
<guid isPermaLink="false">6c2fa679f319c1dff5ec304d9f64188d</guid>
<title>Software Development Methodology for High Consequence Systems - Baca Bouchard Collins (1997)</title>
<link>http://citeseer.ist.psu.edu/360986.html</link>
<description><![CDATA[Extract: "cleanly compiled"from the first sentence. <b>Unit testing</b> automatically implies cleanly compiled. 3.5.1<br> to produce code units which have been thoroughly <b>unit teste</b>d. Inspection of the code includes a surety</font><br><br><br><a href="http://infoserve.sandia.gov/sand_doc/1997/972474.pdf">Original link</a><p><sub><i>-- Delivered by <a href="http://feed43.com/">Feed43</a> service</i></sub></p>
]]></description>
</item>
<item>
<guid isPermaLink="false">549f1818d1e7fde0d59f1276d0d9e02c</guid>
<title>Tight Spiral Projects for Communicating Software.. - Clinton Jeffery Division (1998)</title>
<link>http://citeseer.ist.psu.edu/jeffery98tight.html</link>
<description><![CDATA[Extract: rapid prototyping, source code control, <b>unit testing</b> and code integration. Maintenance is a <br> fourth iteration emphasizes revision control, <b>unit testing</b> and integration. Lectures describe a variety</font><br><br><br><a href="http://www.cs.utsa.edu/research/idol/fitg.ps.gz">Original link</a><p><sub><i>-- Delivered by <a href="http://feed43.com/">Feed43</a> service</i></sub></p>
]]></description>
</item>
<item>
<guid isPermaLink="false">e232092d80985fc715228f1eeb900881</guid>
<title>Formally Verified On-Line Diagnosis - Walter, Lincoln, Suri (1997)</title>
<link>http://citeseer.ist.psu.edu/walter97formally.html</link>
<description><![CDATA[Extract: that are capable of testing each other. Unit-to-<b>unit testing</b> assignments are established to obtain test<br> results could be relied upon when any fault-free <b>unit teste</b>d a faulty unit. Derivatives and subsequent work </font><br><br><br><a href="http://www.ce.chalmers.se/~suri/papers/paper-tse.ps">Original link</a><p><sub><i>-- Delivered by <a href="http://feed43.com/">Feed43</a> service</i></sub></p>
]]></description>
</item>
<item>
<guid isPermaLink="false">f4aa5fad5f1d54aadb65f1de7041d7a3</guid>
<title>.6 Rationale for NIST Participation - Required Nist Resources</title>
<link>http://citeseer.ist.psu.edu/357567.html</link>
<description><![CDATA[Extract: testing techniques are typically applied to <b>unit testing</b> of code, while tests for standards are often</font><br><br><br><a href="http://www.antd.nist.gov/CANE/cane-examples.ps">Original link</a><p><sub><i>-- Delivered by <a href="http://feed43.com/">Feed43</a> service</i></sub></p>
]]></description>
</item>
<item>
<guid isPermaLink="false">eaf3611a109aadae0b9b9e8ab067542c</guid>
<title>An Empirical Study of the Branch Coverage of Different Fault.. - Cline, Werner</title>
<link>http://citeseer.ist.psu.edu/355541.html</link>
<description><![CDATA[Extract: testing. High branch coverage is common in <b>unit testing</b>, but can be a dicult goal to reach in system<br> While branch coverage is most often measured in <b>unit testing</b>, in recent years it has gained popularity as </font><br><br><br><a href="http://www.cse.ucsc.edu/~cline/csspaper.ps.gz">Original link</a><p><sub><i>-- Delivered by <a href="http://feed43.com/">Feed43</a> service</i></sub></p>
]]></description>
</item>
<item>
<guid isPermaLink="false">01836c8c3b67f2543005c41608f58091</guid>
<title>Model Checking Java Programs Using Java PathFinder - Havelund, Pressburger (1998)</title>
<link>http://citeseer.ist.psu.edu/havelund98model.html</link>
<description><![CDATA[Extract: can imagine model checking being applied for <b>unit testing</b>, where one focuses on a single class (or a few <br> this small system. This can be regarded as <b>unit testing</b> the buffer. Concretely, we shall define two</font><br><br><br><a href="http://ase.arc.nasa.gov/havelund/Publications/jpf-sttt.ps.Z">Original link</a><p><sub><i>-- Delivered by <a href="http://feed43.com/">Feed43</a> service</i></sub></p>
]]></description>
</item>
<item>
<guid isPermaLink="false">33343f2ea4a46df56001ab789f1f3aea</guid>
<title>Criteria for Generating Specification-based Tests - Offutt, Xiong, Liu (1999)</title>
<link>http://citeseer.ist.psu.edu/offutt99criteria.html</link>
<description><![CDATA[Extract: generation is often thought of as useful for <b>unit testing</b>, when individual functions or modules are</font><br><br><br><a href="http://www.sel.cs.hiroshima-cu.ac.jp/~liu/ICECCS99Jeffspectestp.ps">Original link</a><p><sub><i>-- Delivered by <a href="http://feed43.com/">Feed43</a> service</i></sub></p>
]]></description>
</item>
<item>
<guid isPermaLink="false">fb90126164ef497f25ceff9ec1074c86</guid>
<title>A Case Study Of IV&amp;V Cost Effectiveness - Neal, McCaugherty, Joshi, Callahan (1997)</title>
<link>http://citeseer.ist.psu.edu/neal97case.html</link>
<description><![CDATA[Extract: Design (DD) Phase 4: Implementation (coding and <b>unit testing</b>) Imp) Phase 5: Integration and System Test<br> examination normally starts during coding and <b>unit testing</b> (Phase 4) and concludes at the end of</font><br><br><br><a href="http://research.ivv.nasa.gov/docs/techreports/1997/NASA-IVV-97-007.ps">Original link</a><p><sub><i>-- Delivered by <a href="http://feed43.com/">Feed43</a> service</i></sub></p>
]]></description>
</item>
<item>
<guid isPermaLink="false">ae55978f6020f1035a12a4695cf6e8f0</guid>
<title>IBDL: A Language for Interface Behavior Specification and.. - Viswanadha, al.</title>
<link>http://citeseer.ist.psu.edu/349461.html</link>
<description><![CDATA[Extract: developed at Sun Microsystems Laboratories for <b>unit-testing</b> of Cprograms. Another bene#t of this</font><br><br><br><a href="http://www.usenix.org/publications/library/proceedings/coots98/full_papers/viswanadha/viswanadha.pdf">Original link</a><p><sub><i>-- Delivered by <a href="http://feed43.com/">Feed43</a> service</i></sub></p>
]]></description>
</item>
<item>
<guid isPermaLink="false">f72967f9d12fd41462029bf07342bfd1</guid>
<title>Concurrency Control in Advanced Database Applications - Barghouti, Kaiser (1994)</title>
<link>http://citeseer.ist.psu.edu/barghouti94concurrency.html</link>
<description><![CDATA[Extract: of the code such as the completion of <b>unit testing</b>. Other traditional concurrency control schemes </font><br><br><br><a href="http://ftp.cs.columbia.edu/pub/marvel/CUCS-425-89.ps.gz">Original link</a><p><sub><i>-- Delivered by <a href="http://feed43.com/">Feed43</a> service</i></sub></p>
]]></description>
</item>
<item>
<guid isPermaLink="false">d8f6f7a9517881f98716f69cfe15cefd</guid>
<title>Verification and Validation in a Rapid Software Development .. - Callahan, Easterbrook</title>
<link>http://citeseer.ist.psu.edu/347220.html</link>
<description><![CDATA[Extract: they are expensive and poor substitutes for <b>unit testing</b>. Important objectives of <b>unit testing</b> are<br> for <b>unit testing</b>. Important objectives of <b>unit testing</b> are to ensure that adequate test coverage is<br> tool was used to develop and perform white-box <b>testing (unit</b> and integrated component level verification)</font><br><br><br><a href="http://www.csee.wvu.edu/~callahan/pub/sel97.ps">Original link</a><p><sub><i>-- Delivered by <a href="http://feed43.com/">Feed43</a> service</i></sub></p>
]]></description>
</item>
<item>
<guid isPermaLink="false">a48a37018253394fe23c5e8a8b59003e</guid>
<title>Test Generation and Recognition with Formal Methods - Ammann, Black (2000)</title>
<link>http://citeseer.ist.psu.edu/ammann00test.html</link>
<description><![CDATA[Extract: several functional source code benchmarks for <b>unit testing</b>, then generated good test sets. Currently we</font><br><br><br><a href="http://hissa.nist.gov/~black/Papers/limerick.ps">Original link</a><p><sub><i>-- Delivered by <a href="http://feed43.com/">Feed43</a> service</i></sub></p>
]]></description>
</item>
<item>
<guid isPermaLink="false">7c8b5f1780aeb7d39cca9653981b2bde</guid>
<title>A Flexible Rule-Chaining Engine for Process-Based.. - Tong, Kaiser, Popovich (1994)</title>
<link>http://citeseer.ist.psu.edu/tong94flexible.html</link>
<description><![CDATA[Extract: each of the affected source files has passed <b>unit testing</b> successfully. Each of the steps after reserve<br> built, the system guidance chained to the <b>unit test</b> rule on "agenda module" and then the build</font><br><br><br><a href="http://ftp.cs.columbia.edu/pub/marvel/CUCS-005-94.ps.gz">Original link</a><p><sub><i>-- Delivered by <a href="http://feed43.com/">Feed43</a> service</i></sub></p>
]]></description>
</item>
<item>
<guid isPermaLink="false">1336da11bcdd05917955a4d5acdead94</guid>
<title>Manufacturer's CORBA Interface Testing Toolkit: Overview - Flater (1999)</title>
<link>http://citeseer.ist.psu.edu/flater99manufacturers.html</link>
<description><![CDATA[Extract: automatically. Dummy components are useful for <b>unit testing</b>, where one component must be tested in<br> following varieties of software testing. 3.1 <b>Unit Testing</b> Before a component is integrated into a</font><br><br><br><a href="http://www.mel.nist.gov/msidlibrary/doc/j42fla.pdf">Original link</a><p><sub><i>-- Delivered by <a href="http://feed43.com/">Feed43</a> service</i></sub></p>
]]></description>
</item>
<item>
<guid isPermaLink="false">7115b8828ec45c804e4a6f348abafe5b</guid>
<title>An Approach To Analyzing and Testing Component-Based Systems - Harrold, Liang, Sinha (1999)</title>
<link>http://citeseer.ist.psu.edu/harrold99approach.html</link>
<description><![CDATA[Extract: testing a component is similar to traditional <b>unit testing</b>. However, traditional <b>unittesting</b> criteria,<br> traditional <b>unit testing</b>. However, traditional <b>unittesting</b> criteria, such as statement and branch</font><br><br><br><a href="http://www.cc.gatech.edu/aristotle/Publications/Papers/icse99-workshop.ps">Original link</a><p><sub><i>-- Delivered by <a href="http://feed43.com/">Feed43</a> service</i></sub></p>
]]></description>
</item>
<item>
<guid isPermaLink="false">68ee35d474387f6e6d5f6d85dd15b15c</guid>
<title>Criteria for Testing Exception-Handling Constructs in Java.. - Sinha, Harrold (1999)</title>
<link>http://citeseer.ist.psu.edu/sinha99criteria.html</link>
<description><![CDATA[Extract: are directed towards attaining those goals. <b>Unit testing</b>, for example, tests each individual module in<br> way in which the criteria can be used during <b>unit testing</b> and integration testing. 4.1 Computation of<br> from i to j. 4.2 Using the criteria for <b>unit testing</b> <b>Unit testing</b> focuses on testing individual modules </font><br><br><br><a href="http://www.cc.gatech.edu/~sinha/papers/icsm99.ps">Original link</a><p><sub><i>-- Delivered by <a href="http://feed43.com/">Feed43</a> service</i></sub></p>
]]></description>
</item>
<item>
<guid isPermaLink="false">f723ae3986f4189b515951436bec977d</guid>
<title>v-Promela: A Visual, Object-Oriented Language for SPIN - Leue, Holzmann</title>
<link>http://citeseer.ist.psu.edu/329492.html</link>
<description><![CDATA[Extract: by a design stage, an implementation and <b>unit testing</b> stage, an integration testing stage, and</font><br><br><br><a href="http://fee.uwaterloo.ca:80/~sleue/publications.files/isorc99.ps.Z">Original link</a><p><sub><i>-- Delivered by <a href="http://feed43.com/">Feed43</a> service</i></sub></p>
]]></description>
</item>
<item>
<guid isPermaLink="false">d3407538decd26451c41098faf50dd4d</guid>
<title>Software Quality: A Curriculum Postscript? - Thomas Hilburn Embry-Riddle (2000)</title>
<link>http://citeseer.ist.psu.edu/hilburn00software.html</link>
<description><![CDATA[Extract: techniques that are used seem to center around <b>unit testing</b>. Students often end up, like many professional <br> design phase. At the same time, planning for <b>unit testing</b> begins. Next, as the coding for a unit is</font><br><br><br><a href="http://faculty.db.erau.edu/hilburn/pap-pre/sigcse20pub.pdf">Original link</a><p><sub><i>-- Delivered by <a href="http://feed43.com/">Feed43</a> service</i></sub></p>
]]></description>
</item>
<item>
<guid isPermaLink="false">e4cd62acc3aff8e70c5049e19867b163</guid>
<title>Computing - Glendenning, Raffi (2000)</title>
<link>http://citeseer.ist.psu.edu/glendenning00computing.html</link>
<description><![CDATA[Extract: Code acceptance and documentation standards. <b>Testing (unit</b> and integration)Maintain a list of</font><br><br><br><a href="http://www.tuc.nrao.edu/~demerson/almapbk/test_int/chap11/chap11.pdf">Original link</a><p><sub><i>-- Delivered by <a href="http://feed43.com/">Feed43</a> service</i></sub></p>
]]></description>
</item>
<item>
<guid isPermaLink="false">467066ac748926119ec86c3119e0b2f4</guid>
<title>Extended TTCN in Software Testing - Liu, Dasiewicz</title>
<link>http://citeseer.ist.psu.edu/328822.html</link>
<description><![CDATA[Extract: Firstly, the syntax of TTCN too cumbersome for <b>unit testing</b>, which requires a much more lightweight</font><br><br><br><a href="http://vlsi.uwaterloo.ca/~wbliu/testinfo/pubs/ccece98.ps">Original link</a><p><sub><i>-- Delivered by <a href="http://feed43.com/">Feed43</a> service</i></sub></p>
]]></description>
</item>


  </channel>
</rss>
