﻿<?xml version="1.0" encoding="utf-8"?><rss xmlns:a10="http://www.w3.org/2005/Atom" version="2.0"><channel><title>SoftwareTestPro.com Error Handling Feed</title><description /><item><guid isPermaLink="true">http://www.softwaretestpro.com/Item/5769/Basics-of-Test-Automation-Part-3---Test-Automation-Approach/End-to-End-Test-and-QA-Testing-Automation-Error-Handling-Future-Test-Quality-Assurance-Regression</guid><link>http://www.softwaretestpro.com/Item/5769/Basics-of-Test-Automation-Part-3---Test-Automation-Approach/End-to-End-Test-and-QA-Testing-Automation-Error-Handling-Future-Test-Quality-Assurance-Regression</link><author>smita.mishra@qazone.in</author><category>End to End</category><category>Test and QA</category><category>Testing</category><category>Automation</category><category>Error Handling</category><category>Future Test</category><category>Quality Assurance</category><category>Regression</category><title>Basics of Test Automation: Part 3 - Test Automation Approach</title><description>Here is the final part of the 3 article series and the simplest one to absorb. Once the methodology is finalised and understood, the next hurdle is to approach automation in a phased manner to implement our automation methodology. Here comes - Tasks and Phases for Test Automation from Test Planning to Maintenance of Test Suite.
ROI and effort estimation have not been explained in detail. If you are looking for it, please let me know.</description><pubDate>Wed, 02 Jan 2013 00:00:00 -0700</pubDate></item><item><guid isPermaLink="true">http://www.softwaretestpro.com/Item/4945/Whose-Fault-is-it/STQA-Magazine-Error-Handling</guid><link>http://www.softwaretestpro.com/Item/4945/Whose-Fault-is-it/STQA-Magazine-Error-Handling</link><author>claire.cates@sas.com</author><category>ST&amp;QA Magazine</category><category>Error Handling</category><title>Whose Fault is it?</title><description>To achieve complete code coverage during application testing, all error
conditions need to be triggered. Forcing errors out of memory or disk full can
be next to impossible, yet the code paths must be tested to guarantee that the
application handles these errors correctly.</description><pubDate>Mon, 11 Oct 2010 00:00:00 -0600</pubDate></item><item><guid isPermaLink="true">http://www.softwaretestpro.com/Item/4886/Customers-get-quality-centric-VIP-treatment/Best-Practices-Case-Study-Exploratory-Functional-Quality-Assurance-Regression-Software-Test-and-QA-Testing-Process-Error-Handling-Technology-Management</guid><link>http://www.softwaretestpro.com/Item/4886/Customers-get-quality-centric-VIP-treatment/Best-Practices-Case-Study-Exploratory-Functional-Quality-Assurance-Regression-Software-Test-and-QA-Testing-Process-Error-Handling-Technology-Management</link><author>kmackinder@origsoft.com</author><category>Best Practices</category><category>Case Study</category><category>Exploratory</category><category>Functional</category><category>Quality Assurance</category><category>Regression</category><category>Software</category><category>Test and QA</category><category>Testing</category><category>Process</category><category>Error Handling</category><category>Technology</category><category>Management</category><title>Customers get quality-centric VIP treatment </title><description>Vermont Information Processing (VIP) has been providing business solutions to beverage wholesalers since 1972. The company develops software solutions that handle every aspect of the beverage distributorship, streamlining warehouse efficiency, cutting costs, managing inventories and forecasting sales. Market consolidation forced a period of accelerated development upon the company and it was the QA team that really felt the crunch. Customers became wary about upgrading. Now, with a much more robust approach to software quality an the introduction of new tools from Original Software, VIP has completely turned around its QA process and overcome its customers’ cautious attitudes. The company has now transformed into a software testing centre of excellence with happy customers who are keen to upgrade to new releases.</description><pubDate>Thu, 19 Aug 2010 05:25:37 -0600</pubDate></item><item><guid isPermaLink="true">http://www.softwaretestpro.com/Item/4853/Agile-Testing-Notes/Testing-Agile-Teams-Project-Management-Automation-Metrics-Software-Unit-User-Error-Handling-Training-offshore-Tools</guid><link>http://www.softwaretestpro.com/Item/4853/Agile-Testing-Notes/Testing-Agile-Teams-Project-Management-Automation-Metrics-Software-Unit-User-Error-Handling-Training-offshore-Tools</link><author>smanjunath@yahoo.com</author><category>Testing</category><category>Agile</category><category>Teams</category><category>Project Management</category><category>Automation</category><category>Metrics</category><category>Software</category><category>Unit</category><category>User</category><category>Error Handling</category><category>Training</category><category>offshore</category><category>Tools</category><title>Agile Testing Notes</title><description>On a quest to understand how agile projects are successful, I encountered several interesting scenarios and insight into how the overall project is executed. But to my dismay, I almost always find that the information on Agile Testing itself, is quite generic (not talking Automation or Unit testing here). WHY SO? 
</description><pubDate>Thu, 29 Jul 2010 10:05:00 -0600</pubDate></item><item><guid isPermaLink="true">http://www.softwaretestpro.com/Item/4773/Bugs-and-their-Characters/Editorial-Error-Handling-Software-Teams</guid><link>http://www.softwaretestpro.com/Item/4773/Bugs-and-their-Characters/Editorial-Error-Handling-Software-Teams</link><author>fusionjunky@gmail.com</author><category>Editorial</category><category>Error Handling</category><category>Software</category><category>Teams</category><title>Bugs and their Characters</title><description>To what degree are software hiccups charming, if not endearing?</description><pubDate>Wed, 09 Jun 2010 18:00:00 -0600</pubDate></item><item><guid isPermaLink="true">http://www.softwaretestpro.com/Item/4771/The-Automated-Testing-Handbook---Download/Automation-Acceptance-Error-Handling-Future-Test-Performance-Test-and-QA-Quality-Assurance-Testing-End-to-End-Membership-Crews-Web</guid><link>http://www.softwaretestpro.com/Item/4771/The-Automated-Testing-Handbook---Download/Automation-Acceptance-Error-Handling-Future-Test-Performance-Test-and-QA-Quality-Assurance-Testing-End-to-End-Membership-Crews-Web</link><category>Automation</category><category>Acceptance</category><category>Error Handling</category><category>Future Test</category><category>Performance</category><category>Test and QA</category><category>Quality Assurance</category><category>Testing</category><category>End to End</category><category>Membership</category><category>Crews</category><category>Web</category><title>The Automated Testing Handbook - Download</title><description>The risk of software failure has never been greater. The estimated annual economic impact ranges from $60 billion for poor testing to $100 billion in lost revenues and increased costs. Unfortunately, market pressure for the delivery of new functionality and applications has also never been stronger. This combination creates increasing pressure on software test organizations to improve test coverage while meeting ever-shorter deadlines with static or even declining resources. The only practical means to achieving quality goals within the constraints of schedules and budgets is to automate.

This premium resource is available for a limited time to "Basic Members".</description><pubDate>Wed, 09 Jun 2010 08:06:00 -0600</pubDate></item></channel></rss>