<?xml version="1.0" encoding="UTF-8"?>
<article article-type="research-article" xml:lang="English" xmlns:xlink="http://www.w3.org/1999/xlink">
<front>
<journal-meta>
<journal-id journal-id-type="publisher">london-journal-of-research-in-computer-science-technology</journal-id>
<journal-title-group>
<journal-title>London Journal of Research in Computer Science &amp; Technology</journal-title>
</journal-title-group>
<issn publication-format="print">2514-863X</issn>
<issn publication-format="electronic">2514-8648</issn>
<publisher><publisher-name>JournalsPress</publisher-name></publisher>
<self-uri xlink:href="https://journalspress.com/journal-seo-export/jats/101973.xml" />
</journal-meta>
<article-meta>
<article-id pub-id-type="publisher-id">101973</article-id>
<title-group>
<article-title>Understanding Unit Boundaries in White-Box Testing of Programs</article-title>
</title-group>
<volume>24</volume>
<issue>1</issue>
<abstract><p>The most tedious and time-consuming phase in a software development cycle is the software testing. White box testing is performed by developers and testing teams dedicated in uncovering defects earlier in a cycle, providing fixes for reported failures, regression testing and debugging in both unit level and integration level testing. Understanding the program units and program boundaries is essential and crucial for measuring a thoroughness and a cost of a testing and efforts related to prioritization of the tests. In this work we try to understand the boundary of a program unit in white box testing of procedural programs and  bjectoriented programs. We extend understanding on boundaries of units under white box testing toward developing understanding on determining a test order that may be effective for prioritizing integration and system level testing.</p></abstract>
<self-uri content-type="html" xlink:href="https://journalspress.com/understanding-unit-boundaries-in-white-box-testing-of-programs/" />
</article-meta>
</front>
<body>
<sec>
<title>Full Text</title>
<p>The most tedious and time-consuming phase in a software development cycle is the software testing. White box testing is performed by developers and testing teams dedicated in uncovering defects earlier in a cycle, providing fixes for reported failures, regression testing and debugging in both unit level and integration level testing. Understanding the program units and program boundaries is essential and crucial for measuring a thoroughness and a cost of a testing and efforts related to prioritization of the tests. In this work we try to understand the boundary of a program unit in white box testing of procedural programs and  bjectoriented programs. We extend understanding on boundaries of units under white box testing toward developing understanding on determining a test order that may be effective for prioritizing integration and system level testing.</p>
</sec>
</body>
</article>