<?xml version="1.0"?>
<rss version="2.0">
   <channel>
      <title> by Suren AeRoz</title>
      <link>https://padlet.com/aendran_star/nnmlwsbq0pvn</link>
      <description></description>
      <language>en-us</language>
      <pubDate>2015-09-17 08:31:07 UTC</pubDate>
      <lastBuildDate>2015-09-17 09:22:07 UTC</lastBuildDate>
      <webMaster>hello@padlet.com</webMaster>
      <image>
         <url></url>
      </image>
      <item>
         <title>1122702589 SEF TUTORIAL 10</title>
         <author>aendran_star</author>
         <link>https://padlet.com/aendran_star/nnmlwsbq0pvn/wish/70658189</link>
         <description><![CDATA[<p>Part A: Discussion </p><p>1.</p><p><b><i>white box testing-</i></b>&nbsp;a method of testing&nbsp;<a href="https://en.wikipedia.org/wiki/Software">software</a>&nbsp;that tests internal structures or workings of an application, as opposed to its functionality..</p><p>test case derived from source codes- white box</p><p>conducts structural testing</p><p>number of test cases depends on number of functionality.</p><p><b><i>black box testing</i></b>-software&nbsp;<b>testing</b>&nbsp;that examines the functionality of an application without peering into its internal structures or workings. This method of&nbsp;<b>test</b>&nbsp;can be applied to virtually every level of software&nbsp;<b>testing</b></p><p>derived from component specification- black box</p><p>tests the program behavior.</p><p>number of cases depends on number of possible executions.</p><p>q2.</p><p>a)&nbsp;flow graph-</p><p>b) cyclomatic complexity -source code complexity measurement that is being correlated to a number of coding errors. It is calculated by developing a Control Flow Graph of the code that measures the number of linearly-independent paths through a program module. 3 LINEAR EXECUTION PATHS</p><p>c) 3 testing.. based on flow graph TO ENSURE ALL CODES STATEMENTS ARE EXECUTED AT LEAST ONCE</p><p>q3. THE SMALLEST TEST UNIT IN OO IS THE Classes. class operators cannot be tested in isolation. but as part of the class as well as its interaction with classes.</p><p>q4. system behaviour vs user behaviour</p><p>&nbsp;software&nbsp;<b>testing</b>&nbsp;activity that uses&nbsp;<b>scenarios</b>: hypothetical stories to help the tester work through a complex problem or&nbsp;<b>test</b>&nbsp;system.</p><p>detect errors during actors interaction with the system. focus on the actors behavior. test cases can be created based on the use cases, since the use cases document the actors objectives using the system.</p><p>q5.</p><p>sequence diagram</p><p>activity diagram</p><p>state transition diagram: derive the test cases based on the change of system states</p>]]></description>
         <enclosure url="" />
         <pubDate>2015-09-17 08:31:27 UTC</pubDate>
         <guid>https://padlet.com/aendran_star/nnmlwsbq0pvn/wish/70658189</guid>
      </item>
   </channel>
</rss>
