<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:georss='http://www.georss.org/georss' xmlns:gd='http://schemas.google.com/g/2005' xmlns:thr='http://purl.org/syndication/thread/1.0'><id>tag:blogger.com,1999:blog-15591271</id><updated>2011-12-14T18:43:19.906-08:00</updated><title type='text'>Planning Automated Software Testing</title><subtitle type='html'>Blog will cover test planning and test automation topics. It will be focused on specific types of testing. Primarily testing described as regression, functional and system testing.</subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://operativesoft2.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/15591271/posts/default?max-results=100'/><link rel='alternate' type='text/html' href='http://operativesoft2.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><author><name>Bruce</name><uri>http://www.blogger.com/profile/17601518184121444265</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='22' height='32' src='http://www.operativesoft.com/images/me.gif'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>4</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>100</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-15591271.post-112663084037149496</id><published>2005-09-13T09:11:00.000-07:00</published><updated>2005-09-13T10:14:09.893-07:00</updated><title type='text'>Planning to Select Test Automation Software</title><content type='html'>Selecting a test automation tool requires planning and actually testing the tool for compatibility. The white paper link below covers many items that should be considered before selecting a test automation tool.&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.operativesoft.com/html/introregress.htm"&gt;White Paper&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Summary:&lt;br /&gt;Planning to automate testing requires and understanding of the Windows GUI interface composed of Text and Objects. Modern tools have essential components and associated automated testing methodologies. As development technologies have evolved so have automated test tools. Development environment, test requirements, test methodologies and skill level should be the basis for selecting a particular product.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/15591271-112663084037149496?l=operativesoft2.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://operativesoft2.blogspot.com/feeds/112663084037149496/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=15591271&amp;postID=112663084037149496' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/15591271/posts/default/112663084037149496'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/15591271/posts/default/112663084037149496'/><link rel='alternate' type='text/html' href='http://operativesoft2.blogspot.com/2005/09/planning-to-select-test-automation.html' title='Planning to Select Test Automation Software'/><author><name>Bruce</name><uri>http://www.blogger.com/profile/17601518184121444265</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='22' height='32' src='http://www.operativesoft.com/images/me.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-15591271.post-112448038563253781</id><published>2005-08-19T12:37:00.000-07:00</published><updated>2005-08-19T12:48:14.190-07:00</updated><title type='text'>Good Test Plan Development is a Team Effort</title><content type='html'>The &lt;a href="http://www.sei.cmu.edu/"&gt;Software Engineering Institute&lt;/a&gt; provides courses on the Capability Maturity Model (CMM), which is a methodology, used to develop and refine an organization's software development process. Since 1984, the SEISM has been identifying, developing, and advocating practices for designing high-quality software and protecting networked systems.&lt;br /&gt;&lt;br /&gt;However, The Blog below in my opinion is excellent, outlining what a good process would be for the planning side of testing. It does an excellent job to incorporate the considerations that are needed to properly implement automated testing.&lt;br /&gt;&lt;br /&gt;&lt;a href="http://blogs.ittoolbox.com/eai/implementation/archives/003123.asp"&gt;Test Planning Process&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/15591271-112448038563253781?l=operativesoft2.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://operativesoft2.blogspot.com/feeds/112448038563253781/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=15591271&amp;postID=112448038563253781' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/15591271/posts/default/112448038563253781'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/15591271/posts/default/112448038563253781'/><link rel='alternate' type='text/html' href='http://operativesoft2.blogspot.com/2005/08/good-test-plan-development-is-team.html' title='Good Test Plan Development is a Team Effort'/><author><name>Bruce</name><uri>http://www.blogger.com/profile/17601518184121444265</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='22' height='32' src='http://www.operativesoft.com/images/me.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-15591271.post-112448001046469887</id><published>2005-08-19T12:32:00.000-07:00</published><updated>2005-08-19T12:46:04.573-07:00</updated><title type='text'>Test Planning the Details</title><content type='html'>Method Labs creator of ReadySET Pro - a set of templates for use cases, test plans, and other software engineering documents. They have an excellent white paper on the need for Test Plans&lt;br /&gt;&lt;br /&gt;&lt;a href="http://readysetpro.com/whitepapers/testplans.html"&gt;http://readysetpro.com/whitepapers/testplans.html&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Another excellent article that gets right to the point "Effective Automation Test Script Design"&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.softtest.org/sigs/material/jphillips1.htm"&gt;http://www.softtest.org/sigs/material/jphillips1.htm&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;This is a fantastic article about creating test plans when requirement are at best poor. It does a great job explaining real world reasons for such a situation. I would like to be charitable and say that this is not the norm, but I think I will leave it alone.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.psqtconference.com/2004east/tracks/Tuesday/PSQTcoe2.pdf"&gt;Requirements and Test Plans&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Nice information on developing test cases and test case samples.&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.sqatester.com/documentation/testcasesmpl.htm"&gt;http://www.sqatester.com/documentation/testcasesmpl.htm&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Other examples:&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/15591271-112448001046469887?l=operativesoft2.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://operativesoft2.blogspot.com/feeds/112448001046469887/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=15591271&amp;postID=112448001046469887' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/15591271/posts/default/112448001046469887'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/15591271/posts/default/112448001046469887'/><link rel='alternate' type='text/html' href='http://operativesoft2.blogspot.com/2005/08/test-planning-details.html' title='Test Planning the Details'/><author><name>Bruce</name><uri>http://www.blogger.com/profile/17601518184121444265</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='22' height='32' src='http://www.operativesoft.com/images/me.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-15591271.post-112447945238459193</id><published>2005-08-19T12:21:00.000-07:00</published><updated>2005-08-19T12:36:33.860-07:00</updated><title type='text'>Purpose</title><content type='html'>Although Test Tool vendors offer training, it is normally the case that too little training and consulting is purchased. Hey, we all have a budget and when it comes to testing, that budget is usually thin. Given budget limitations, Training is usually becomes a feature dump, if the budget is good you possibly get a day or two of real hands on use use of the tool with your application. Most of the causes for test automation problems are usually planning issues.&lt;br /&gt;&lt;br /&gt;This Blog was put together to educate our Sales Team and help them assist customers. It will cover test planning and test automation topics. It will be focused on specific types of testing. Primarily testing described as regression, functional and system testing. We hope it is also a good resource for those test, and especially for those with limited resources that want to automate testing.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/15591271-112447945238459193?l=operativesoft2.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://operativesoft2.blogspot.com/feeds/112447945238459193/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=15591271&amp;postID=112447945238459193' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/15591271/posts/default/112447945238459193'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/15591271/posts/default/112447945238459193'/><link rel='alternate' type='text/html' href='http://operativesoft2.blogspot.com/2005/08/purpose.html' title='Purpose'/><author><name>Bruce</name><uri>http://www.blogger.com/profile/17601518184121444265</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='22' height='32' src='http://www.operativesoft.com/images/me.gif'/></author><thr:total>0</thr:total></entry></feed>
