<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://www.csqa.info" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Software Testing</title>
 <link>http://www.csqa.info/taxonomy/term/45/feed</link>
 <description>The taxonomy view with a depth of 0.</description>
 <language>en</language>
<item>
 <title>How To Break Web Software - A look at security vulnerabilities in web software</title>
 <link>http://www.csqa.info/how_to_break_web_software_-_a_look_at_security_vulnerabilities_in_web_software</link>
 <description>&lt;p&gt;As more applications get &amp;quot;web-ified&amp;quot; moving from the desktop or legacy systems onto the web, attackers follow the vulnerabilities. Without sophisticated tools or &amp;quot;1337 5x1llz&amp;quot;, web applications are now the most attacked technology, with the majority of attacks categorized as &amp;quot;easily exploitable&amp;quot;. &lt;/p&gt;
&lt;p&gt;So, before your application is placed out into one of the most hostile environments, how do you stop your software from being &amp;quot;0wn3d&amp;quot; by the 14 year old in their blacked-out bedroom, or being used by a Russian crime cartel? &lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://www.csqa.info/how_to_break_web_software_-_a_look_at_security_vulnerabilities_in_web_software&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.csqa.info/how_to_break_web_software_-_a_look_at_security_vulnerabilities_in_web_software#comments</comments>
 <category domain="http://www.csqa.info/video/software_testing">Software Testing</category>
 <pubDate>Thu, 31 May 2007 16:44:29 -0500</pubDate>
 <dc:creator>admin</dc:creator>
 <guid isPermaLink="false">516 at http://www.csqa.info</guid>
</item>
<item>
 <title>GUI Regression Test Tools / Automation</title>
 <link>http://www.csqa.info/gui_regression_test_tools_/_automation</link>
 <description>&lt;p&gt;&lt;font size=&quot;-1&quot;&gt;&lt;span class=&quot;visible&quot;&gt;GUI-level regression test tools are the most commonly used black box test automation tools. There is a huge business (vendors and consultants) invested in these tools. But one of the most common ways of using them (capture-replay) yields poorly designed, unmaintainable code. It is possible to use (most of) the tools in ways that go beyond capture/replay but this requires programming skill, thoughtful design, and a good enough understanding of the tool&amp;#39;s (often very poorly documented) programming language&lt;/span&gt;&lt;/font&gt;&lt;/p&gt;
</description>
 <comments>http://www.csqa.info/gui_regression_test_tools_/_automation#comments</comments>
 <category domain="http://www.csqa.info/video/software_testing">Software Testing</category>
 <pubDate>Tue, 29 May 2007 21:28:30 -0500</pubDate>
 <dc:creator>admin</dc:creator>
 <guid isPermaLink="false">510 at http://www.csqa.info</guid>
</item>
<item>
 <title>Can you test Completely ? When to Stop Testing ?</title>
 <link>http://www.csqa.info/can_you_test_completely_%3F_when_to_stop_testing_%3F</link>
 <description>&lt;p&gt;&lt;font size=&quot;-1&quot;&gt;&lt;span class=&quot;visible&quot;&gt;t&amp;#39;s impossible to fully test a program. In the face of an infinitely large &lt;strong&gt;testing&lt;/strong&gt; task, we must be skeptical of statements that some people make that the &lt;strong&gt;testing&lt;/strong&gt; project must always do this or always deliver that. In the face of an infinitely large task, everything is a tradeoff--work spent on one task is work not allocated to another. Wise allocation of resources to tasks and deliverables must be a function of the information objectives of the project at hand.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://www.csqa.info/can_you_test_completely_%3F_when_to_stop_testing_%3F&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.csqa.info/can_you_test_completely_%3F_when_to_stop_testing_%3F#comments</comments>
 <category domain="http://www.csqa.info/video/software_testing">Software Testing</category>
 <pubDate>Tue, 29 May 2007 21:26:14 -0500</pubDate>
 <dc:creator>admin</dc:creator>
 <guid isPermaLink="false">509 at http://www.csqa.info</guid>
</item>
<item>
 <title>Agile Testing *****</title>
 <link>http://www.csqa.info/agile_testing_%2A%2A%2A%2A%2A</link>
 <description>&lt;p&gt;&lt;font size=&quot;-1&quot;&gt;s more teams are adopting Agile practices such as XP and Scrum, &lt;span class=&quot;invisible&quot;&gt; &lt;strong&gt;...&lt;/strong&gt; &lt;a id=&quot;expandlink&quot; style=&quot;color: #7777cc&quot; href=&quot;javascript:void(0)&quot; onclick=&quot;ele(&amp;quot;alldescr&amp;quot;).className=&amp;quot;invisible&amp;quot;; ele(&amp;quot;wholedescr&amp;quot;).className=&amp;quot;visible&amp;quot;; saveCollapseDescr(false); VP_userTouchedSomething=true;&quot;&gt;all &lt;strong&gt;»&lt;/strong&gt;&lt;/a&gt;&lt;/span&gt; &lt;span class=&quot;visible&quot;&gt;&lt;strong&gt;software&lt;/strong&gt; &lt;strong&gt;testing&lt;/strong&gt; teams are being asked to become &amp;quot;Agile&amp;quot; as well. But what does that mean?&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://www.csqa.info/agile_testing_%2A%2A%2A%2A%2A&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.csqa.info/agile_testing_%2A%2A%2A%2A%2A#comments</comments>
 <category domain="http://www.csqa.info/video/software_testing">Software Testing</category>
 <pubDate>Tue, 29 May 2007 21:24:22 -0500</pubDate>
 <dc:creator>admin</dc:creator>
 <guid isPermaLink="false">508 at http://www.csqa.info</guid>
</item>
<item>
 <title>Improve Testing Effectiveness Training</title>
 <link>http://www.csqa.info/improve_testing_effectiveness_training</link>
 <description>&lt;p&gt;&lt;font size=&quot;-1&quot;&gt;&lt;span class=&quot;visible&quot;&gt;Testers&amp;#39; ability to identify, assess and prioritize risk is critical to having the right test focus. Objective, quantitative methods for risk assessment generally do not work well. And s ubjective, intuitive methods for risk assessment are derived as much or more from emotion and psychology rather than &amp;quot;logic&amp;quot;. &lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://www.csqa.info/improve_testing_effectiveness_training&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.csqa.info/improve_testing_effectiveness_training#comments</comments>
 <category domain="http://www.csqa.info/video/software_testing">Software Testing</category>
 <pubDate>Tue, 29 May 2007 21:14:56 -0500</pubDate>
 <dc:creator>admin</dc:creator>
 <guid isPermaLink="false">507 at http://www.csqa.info</guid>
</item>
<item>
 <title>Become a Software Testing Expert</title>
 <link>http://www.csqa.info/become_a_software_testing_expert</link>
 <description>&lt;p&gt;&lt;font size=&quot;-1&quot;&gt;&lt;span class=&quot;visible&quot;&gt;You&amp;#39;re already an experienced tester. You know how to design tests and report bugs. Now what? Do you feel like an expert?&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://www.csqa.info/become_a_software_testing_expert&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.csqa.info/become_a_software_testing_expert#comments</comments>
 <category domain="http://www.csqa.info/video/software_testing">Software Testing</category>
 <pubDate>Tue, 29 May 2007 21:05:36 -0500</pubDate>
 <dc:creator>admin</dc:creator>
 <guid isPermaLink="false">506 at http://www.csqa.info</guid>
</item>
</channel>
</rss>
