<?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-14775571</id><updated>2012-01-24T15:08:33.135Z</updated><category term='Aff'/><category term='Database Modeling'/><category term='barcode scanners'/><category term='ISEB Foundation'/><category term='Business Process Management'/><category term='Test Planning'/><category term='Database'/><category term='Standards'/><category term='ISTQB'/><category term='Question Papers'/><category term='ISEB'/><category term='Exam Papers'/><category term='Software testing'/><category term='BPM'/><category term='Database Testing'/><category term='Yahoo search marketing coupon'/><category term='ISEB Sample Questions'/><category term='Database Auditing'/><category term='small businesses'/><title type='text'>Quality Assurance and Software Testing</title><subtitle type='html'>Online Resource Center for Software Quality Assurance and Software Testing containing handy information for QA and testing interviews.</subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default?max-results=100'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>82</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>100</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-14775571.post-1353561176458915592</id><published>2009-03-30T23:55:00.003+01:00</published><updated>2009-03-31T00:11:50.124+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='small businesses'/><category scheme='http://www.blogger.com/atom/ns#' term='barcode scanners'/><title type='text'>Barcode Scanners for Small Businesses</title><summary type='text'>Though this post might go little off topic, it would be certainly interesting. Specially when I thought about it while going through a bar code software. I thought couple of times, why bar code software has been very useful for the businesses.The retail sector has become an integral part of our lives. All the malls, small and big ones, are equally full of shoppers all the time.Products being </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/1353561176458915592/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=1353561176458915592&amp;isPopup=true' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/1353561176458915592'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/1353561176458915592'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2009/03/barcode-scanners-for-small-businesses.html' title='Barcode Scanners for Small Businesses'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-1714569339707737257</id><published>2009-03-16T23:33:00.005Z</published><updated>2009-03-16T23:46:02.874Z</updated><category scheme='http://www.blogger.com/atom/ns#' term='Database Testing'/><category scheme='http://www.blogger.com/atom/ns#' term='Database'/><category scheme='http://www.blogger.com/atom/ns#' term='Database Modeling'/><category scheme='http://www.blogger.com/atom/ns#' term='Database Auditing'/><title type='text'>Database Testing</title><summary type='text'>Databases are an integral part of any software developed today. Whether you are a Software Tester or an owner of a web site, it is of an utmost importance to know about the underlying database.The simplest task in dealing with databases is to write queries in order to communicate with a database. Web masters owning web sites or database administrators for complex or large software need certain </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/1714569339707737257/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=1714569339707737257&amp;isPopup=true' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/1714569339707737257'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/1714569339707737257'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2009/03/database-testing.html' title='Database Testing'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-4681636048463689309</id><published>2009-01-06T22:59:00.015Z</published><updated>2010-01-13T20:51:18.548Z</updated><category scheme='http://www.blogger.com/atom/ns#' term='Aff'/><category scheme='http://www.blogger.com/atom/ns#' term='Yahoo search marketing coupon'/><title type='text'>I am advertising on Yahoo using Free Advertising YSM Coupon</title><summary type='text'>This blog has been very successful to bring technology minded people through search engines. One of my friend in internet marketing suggested me to use other methods than search engine traffic as well to promote this quality blog.The best method he suggested is to use Yahoo Sponsored search coupon that offers me considerably big money when I deposit $30 cash only in my account. This is really a </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/4681636048463689309/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=4681636048463689309&amp;isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/4681636048463689309'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/4681636048463689309'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2009/01/i-am-advertising-on-yahoo-using-free-25.html' title='I am advertising on Yahoo using Free Advertising YSM Coupon'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-2116556663761721781</id><published>2009-01-01T12:31:00.001Z</published><updated>2009-01-01T12:31:01.066Z</updated><category scheme='http://www.blogger.com/atom/ns#' term='ISEB Foundation'/><category scheme='http://www.blogger.com/atom/ns#' term='Exam Papers'/><category scheme='http://www.blogger.com/atom/ns#' term='ISEB Sample Questions'/><category scheme='http://www.blogger.com/atom/ns#' term='ISEB'/><category scheme='http://www.blogger.com/atom/ns#' term='Question Papers'/><title type='text'>ISEB / ISTQB Foundation Software Testing Certification - Sample Exam Paper Questions and Answers</title><summary type='text'>Wish you all a very happy and prosperous new year 2009!I just told you about my success in ISEB Foundation Software Testing Certification and the books I referred for preparation.Along with the books, it would always help you to understand what kind of questions you might see in the online exam at Prometric center or paper examination.I have three sample exam question papers on ISEB Foundation </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/2116556663761721781/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=2116556663761721781&amp;isPopup=true' title='11 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/2116556663761721781'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/2116556663761721781'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2009/01/iseb-istqb-foundation-software-testing.html' title='ISEB / ISTQB Foundation Software Testing Certification - Sample Exam Paper Questions and Answers'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>11</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-2276332612178484600</id><published>2008-12-28T11:52:00.006Z</published><updated>2009-02-08T21:41:00.439Z</updated><category scheme='http://www.blogger.com/atom/ns#' term='ISEB Foundation'/><category scheme='http://www.blogger.com/atom/ns#' term='ISTQB'/><category scheme='http://www.blogger.com/atom/ns#' term='ISEB'/><category scheme='http://www.blogger.com/atom/ns#' term='Software testing'/><title type='text'>ISEB / ISTQB Books For Foundation Certification in Software Testing</title><summary type='text'>I just appeared for ISEB / ISTQB foundation certificate examination in Software testing and passed it with 87.5%. Moreover, couple of friends also cleared the certificate examination with flying colors. As ISEB exam is conducted through Prometric centers, you can get your results right after the examination.I would like to share my experience with ISEB / ISTQB software testing certificate </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/2276332612178484600/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=2276332612178484600&amp;isPopup=true' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/2276332612178484600'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/2276332612178484600'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2008/12/iseb-istqb-books-for-foundation.html' title='ISEB / ISTQB Books For Foundation Certification in Software Testing'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://1.bp.blogspot.com/_C07BnW_mfw8/SVdsSi9h1DI/AAAAAAAAAAU/JLpqEOZPz4E/s72-c/ISEB_Foundation_Software_Testing_Book_02.jpg' height='72' width='72'/><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-5573591651976903305</id><published>2008-11-27T02:48:00.000Z</published><updated>2008-11-27T03:18:12.055Z</updated><category scheme='http://www.blogger.com/atom/ns#' term='Business Process Management'/><category scheme='http://www.blogger.com/atom/ns#' term='BPM'/><title type='text'>Business Process Management Is Need of the Time</title><summary type='text'>Being in testing field, we should be always keen on knowing what's the buzz in Information technology. One of them is BPM. BPM stands for "Business Process Management" and it's about management of business processes as the name suggests. A business process is managed by a business person in the organization; someone who understand the "business" and works on deciding the strategy for doing that </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/5573591651976903305/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=5573591651976903305&amp;isPopup=true' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/5573591651976903305'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/5573591651976903305'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2008/11/business-process-management-is-need-of.html' title='Business Process Management Is Need of the Time'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-8102327609072374955</id><published>2007-09-26T13:36:00.000+01:00</published><updated>2007-09-26T13:41:50.769+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Standards'/><category scheme='http://www.blogger.com/atom/ns#' term='Test Planning'/><title type='text'>What are IEEE 829 Test Plan Standards?</title><summary type='text'>Hi All, I know I have been away from posting on this blog since long and I apologize for that. There were few things which needed to be taken care of so my blogging activity was side lined. I would try to be more regular in posting new articles on this blog now onwards.Recently, I have been searching a lot on testing jargons and come across a list of IEEE 829 Test Plan Standards as it was </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/8102327609072374955/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=8102327609072374955&amp;isPopup=true' title='10 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/8102327609072374955'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/8102327609072374955'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2007/09/what-are-ieee-829-test-plan-standards.html' title='What are IEEE 829 Test Plan Standards?'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>10</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-116703832591617104</id><published>2006-12-24T21:13:00.000Z</published><updated>2006-12-30T21:37:37.736Z</updated><title type='text'>What is a Traceability Matrix / Requirements Traceability Matrix?</title><summary type='text'>The concept of Traceability Matrix is to be able to trace from top level requirements to implementation, and from top level requirements to test. A traceability matrix is a table that traces a requirement to the tests that are needed to verify that the requirement is fulfilled. A good traceability matrix will provide backward and forward traceability, i.e. a requirement can be traced to a test </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/116703832591617104/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=116703832591617104&amp;isPopup=true' title='8 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/116703832591617104'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/116703832591617104'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2006/12/what-is-traceability-matrix.html' title='What is a Traceability Matrix / Requirements Traceability Matrix?'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>8</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-115071834137124223</id><published>2006-06-19T12:55:00.000+01:00</published><updated>2007-02-08T07:51:06.990Z</updated><title type='text'>Quick Test Professional (QTP) Questions n Answers</title><summary type='text'>Here's a good resource for Quick Test Professional (QTP). You can find here answers for FAQs regarding QTP. If you have any question to be answered, which is not present in the list, please drop in a comment.http://qtpro.blogspot.com</summary><link rel='related' href='http://qtpro.blogspot.com' title='Quick Test Professional (QTP) Questions n Answers'/><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/115071834137124223/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=115071834137124223&amp;isPopup=true' title='12 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/115071834137124223'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/115071834137124223'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2006/06/quick-test-professional-qtp-questions.html' title='Quick Test Professional (QTP) Questions n Answers'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>12</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-114977639089873860</id><published>2006-06-08T15:10:00.000+01:00</published><updated>2008-09-21T22:04:37.406+01:00</updated><title type='text'>Link for QTP (Quick Test Pro) 14-days free trial</title><summary type='text'>Click here for HP's QuickTest Professional Free 14-Day Trial. Choose the link for Quick Test Professional Evaluation on the page.Note that you'll have to register to download the same.</summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/114977639089873860/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=114977639089873860&amp;isPopup=true' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/114977639089873860'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/114977639089873860'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2006/06/link-for-qtp-quick-test-pro-14-days.html' title='Link for QTP (Quick Test Pro) 14-days free trial'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-113742592981014379</id><published>2006-01-16T15:35:00.000Z</published><updated>2006-02-12T13:52:17.766Z</updated><title type='text'>WinRunner Interview Questions</title><summary type='text'>1. How to recognise the objects during runtime in new build version (test suite) comparing with old guimap?2. Wait(20) - What is the minimum and maximum time the above mentioned synchronization statements will wait given that the global default timeout is set to 15 seconds. 3. Where in the user-defined function library should a new error code be defined?4. In a modular test tree, each test will </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/113742592981014379/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=113742592981014379&amp;isPopup=true' title='4 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/113742592981014379'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/113742592981014379'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2006/01/winrunner-interview-questions.html' title='WinRunner Interview Questions'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>4</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112689539214583818</id><published>2006-01-04T16:15:00.000Z</published><updated>2007-02-19T06:01:07.943Z</updated><title type='text'>Have I Tested Enough?</title><summary type='text'>One of the most intriguing and difficult questions to answer in any software development life cycle is whether the software is defect free. No matter what the level of maturity of software application, it is next to impossible to say that a software application is defect free. We can answer this question to a certain level by collecting data with regard to the performance and reliability of the </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112689539214583818/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112689539214583818&amp;isPopup=true' title='3 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112689539214583818'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112689539214583818'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2006/01/have-i-tested-enough.html' title='Have I Tested Enough?'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>3</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-113509372776464700</id><published>2005-12-20T15:20:00.000Z</published><updated>2005-12-20T15:48:55.470Z</updated><title type='text'>Security Testing</title><summary type='text'>Security Testing:Testing which confirms that the program can access to authorized personnel and that the authorized personnel can access the functions available to their security level. Security testing is testing how well the system is protected against unauthorized internal or external access, or willful damage.The purpose of security testing is to determine how well a system protects against </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/113509372776464700/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=113509372776464700&amp;isPopup=true' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/113509372776464700'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/113509372776464700'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/12/security-testing.html' title='Security Testing'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-113500821371944321</id><published>2005-12-19T16:01:00.000Z</published><updated>2006-10-05T06:01:10.453+01:00</updated><title type='text'>Funny replies developers give to testers..</title><summary type='text'>Top 20 replies by Programmers to Testers when their programs don't work:20. "That's weird..."19. "It's never done that before."18. "It worked yesterday."17. "How is that possible?"16. "It must be a hardware problem."15. "What did you type in wrong to get it to crash?"14. "There is something funky in your data."13. "I haven't touched that module in weeks!"12. "You must have the wrong version."11. </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/113500821371944321/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=113500821371944321&amp;isPopup=true' title='10 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/113500821371944321'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/113500821371944321'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/12/funny-replies-developers-give-to.html' title='Funny replies developers give to testers..'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>10</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112689453225789639</id><published>2005-12-12T15:14:00.000Z</published><updated>2006-06-08T15:27:27.813+01:00</updated><title type='text'>Link for WinRunner Demo</title><summary type='text'>Click here for Free trial version of WinRunner, Mercury Interactive's enterprise functional testing tool.Note that, you'll need to contact their sales department in you region.</summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112689453225789639/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112689453225789639&amp;isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112689453225789639'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112689453225789639'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/12/link-for-winrunner-demo.html' title='Link for WinRunner Demo'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-113356992749781454</id><published>2005-12-03T00:30:00.000Z</published><updated>2005-12-03T00:32:07.576Z</updated><title type='text'>What is Testware?</title><summary type='text'>As we know that hardware development engineers produce hardware. Software development engineers produce software. Same like this, Software test engineers produce testware.Testware is produced by both verification and validation testing methods. Testware includes test cases, test plan, test report and etc. Like software, testware should be placed under the control of a configuration management </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/113356992749781454/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=113356992749781454&amp;isPopup=true' title='3 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/113356992749781454'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/113356992749781454'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/12/what-is-testware.html' title='What is Testware?'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>3</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112688972827863918</id><published>2005-12-01T17:54:00.000Z</published><updated>2005-12-01T17:27:58.280Z</updated><title type='text'>Levels of testing</title><summary type='text'>A step into the world of software testing might seem like a nightmare, with memories of unending test scriptsproviding weeks of tedious repetitive testing and mountains of problem reports. Even after apparently exhaustive testing, bugs are still found, there is rework to carry out and inevitably yet more testing. But with careful planning, software testing can go like a dream.Levels of testing:</summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112688972827863918/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112688972827863918&amp;isPopup=true' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112688972827863918'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112688972827863918'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/12/levels-of-testing.html' title='Levels of testing'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112739703422359362</id><published>2005-11-29T15:30:00.000Z</published><updated>2005-11-29T12:57:58.243Z</updated><title type='text'>Checklist for Acceptance Test</title><summary type='text'>Test Preparation  - Has the plan for acceptance testing been submitted? - Have all possible interactions been described? - Are all input data required for testing available? - Is it possible to automatically document the test runs? - Have the customer specific constraints been considered? - Have you defined acceptance criteria (e.g. performance, portability, throughput, etc.) on which the  </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112739703422359362/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112739703422359362&amp;isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112739703422359362'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112739703422359362'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/11/checklist-for-acceptance-test.html' title='Checklist for Acceptance Test'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112688930347610794</id><published>2005-11-22T15:42:00.000Z</published><updated>2005-11-22T05:40:03.276Z</updated><title type='text'>Writing effective test cases</title><summary type='text'>Testing cannot ensure complete eradication of errors. Various types of Testing have their own limitations. Consider Exhaustive black box and white box testing, which are practically not "Exhaustive" to the verbose as they are required to be, owing to the resource factors. While testing a Software Product, one of the most important things is the design of effective test cases. A Tester tries to </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112688930347610794/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112688930347610794&amp;isPopup=true' title='5 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112688930347610794'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112688930347610794'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/11/writing-effective-test-cases.html' title='Writing effective test cases'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>5</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-113206804637110942</id><published>2005-11-16T15:18:00.000Z</published><updated>2005-11-16T13:46:02.590Z</updated><title type='text'>System Testing</title><summary type='text'>This type of test involves examination of all the system for software components, all the hardware components and any interfaces.The whole system is checked not only for validity but also for met objectives. The complete system is configured in a controlled environment, and test cases are developed to simulate real life scenarios that occur in a simulated real life test environment.  System </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/113206804637110942/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=113206804637110942&amp;isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/113206804637110942'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/113206804637110942'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/11/system-testing.html' title='System Testing'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112688844035787072</id><published>2005-11-15T15:32:00.000Z</published><updated>2005-11-15T16:00:28.923Z</updated><title type='text'>More Testing types: Funny</title><summary type='text'>Have you ever done Testing to Obsession?Well, we did it once and with that particularly long and painful bout of regression testing, we came up withthe list of other types of testing we ‘d like not to see – Aggression Testing: If this doesn't work, I'm gonna kill somebody.Compression Testing: [ ]Confession Testing: Okay, Okay, I did program that bug.Depression Testing: If this doesn't work, I'm </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112688844035787072/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112688844035787072&amp;isPopup=true' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112688844035787072'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112688844035787072'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/11/more-testing-types-funny.html' title='More Testing types: Funny'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112732359301189841</id><published>2005-11-14T15:24:00.000Z</published><updated>2005-11-14T14:13:38.933Z</updated><title type='text'>Responsibilities of a Test Manager</title><summary type='text'>Responsibilities of a Test Manager:− Manage the Testing Department.− Allocate resource to projects.− Review weekly Testers' status reports and take necessary actions− Escalate Testers' issues to the Sr. Management.− Estimate for testing projects.− Enforce the adherence to the company's Quality processes and procedures.− Decision to procure Software Testing tools for the organization.− Inter group</summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112732359301189841/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112732359301189841&amp;isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112732359301189841'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112732359301189841'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/11/responsibilities-of-test-manager.html' title='Responsibilities of a Test Manager'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112732362924206127</id><published>2005-11-11T15:26:00.000Z</published><updated>2005-11-11T15:03:17.390Z</updated><title type='text'>Responsibilities of a Test Lead</title><summary type='text'>Responsibilities of a Test leader:− Prepare the Software Test Plan. − Check / Review the Test Cases document – System, Integration and User Acceptance prepared by test engineers. − Analyze requirements during the requirements analysis phase of projects. − Keep track of the new requirements from the Project. − Forecast / Estimate the Project future requirements. − Arrange the Hardware and software</summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112732362924206127/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112732362924206127&amp;isPopup=true' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112732362924206127'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112732362924206127'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/11/responsibilities-of-test-lead.html' title='Responsibilities of a Test Lead'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112992395971536178</id><published>2005-11-08T15:45:00.000Z</published><updated>2006-07-21T11:02:41.933+01:00</updated><title type='text'>Boundary Value Analysis (BVA)</title><summary type='text'>Boundary value analysis is a technique for test data selection. A test engineer chooses values that lie along data extremes. Boundary values include maximum, minimum, just inside boundaries, just outside boundaries, typical values, and error values. The expectation is that, if a systems works correctly for these extreme or special values, then it will work correctly for all values in between. An </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112992395971536178/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112992395971536178&amp;isPopup=true' title='6 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112992395971536178'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112992395971536178'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/11/boundary-value-analysis-bva.html' title='Boundary Value Analysis (BVA)'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>6</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-113050777003717130</id><published>2005-10-28T15:36:00.000+01:00</published><updated>2005-10-28T15:13:49.990+01:00</updated><title type='text'>The Testing Estimation Process</title><summary type='text'>One of the most difficult and critical activities in IT is the estimation process. I believe that it occurs because when we say that one project will be accomplished in such time by at such cost, it must happen. If it does not happen, several things may follow: from peers’ comments and senior management’s warnings to being fired depending on the reasons and seriousness of the failure.Here are a </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/113050777003717130/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=113050777003717130&amp;isPopup=true' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/113050777003717130'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/113050777003717130'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/10/testing-estimation-process.html' title='The Testing Estimation Process'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112992352691030289</id><published>2005-10-21T20:30:00.000+01:00</published><updated>2005-10-21T20:38:46.963+01:00</updated><title type='text'>Testing - when requirements are changing continuously</title><summary type='text'>Work with management early on to understand how requirements might change, so that alternate test plans and strategies can be worked out in advance. It is helpful if the application's initial design allows for some adaptability, so that later changes do not require redoing the application from scratch. Additionally, try to...  - In the project's initial schedule, allow for some extra time to </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112992352691030289/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112992352691030289&amp;isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112992352691030289'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112992352691030289'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/10/testing-when-requirements-are-changing.html' title='Testing - when requirements are changing continuously'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112897070541273621</id><published>2005-10-17T15:20:00.000+01:00</published><updated>2005-10-17T14:40:08.173+01:00</updated><title type='text'>Difference between Verification and Validation</title><summary type='text'>Verification ensures the product is designed to deliver all functionality to the customer; it typically involves reviews and meetings to evaluate documents, plans, code, requirements and specifications; this can be done with checklists, issues lists, walkthroughs and inspection meetings. You CAN learn to do verification, with little or no outside help. Validation ensures that functionality, as </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112897070541273621/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112897070541273621&amp;isPopup=true' title='12 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112897070541273621'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112897070541273621'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/10/difference-between-verification-and.html' title='Difference between Verification and Validation'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>12</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112897034543022637</id><published>2005-10-14T15:40:00.000+01:00</published><updated>2006-09-06T20:31:47.626+01:00</updated><title type='text'>Difference between Alpha and Beta Testing</title><summary type='text'>Alpha testing is final testing before the software is released to the general public. First, (and this is called the first phase of alpha testing), the software is tested by in-house developers. They use either debugger software, or hardware-assisted debuggers. The goal is to catch bugs quickly. Then, (and this is called second stage of alpha testing), the software is handed over to us, the </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112897034543022637/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112897034543022637&amp;isPopup=true' title='9 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112897034543022637'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112897034543022637'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/10/difference-between-alpha-and-beta.html' title='Difference between Alpha and Beta Testing'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>9</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112896694589213623</id><published>2005-10-13T15:48:00.000+01:00</published><updated>2005-10-13T15:40:31.053+01:00</updated><title type='text'>How do you execute tests?</title><summary type='text'>Execution of tests is completed by following the test documents in a methodical manner. As each test procedure is performed, an entry is recorded in a test execution log to note the execution of the procedure and whether or not the test procedure uncovered any defects. Checkpoint meetings are held throughout the execution phase. Checkpoint meetings are held daily, if required, to address and </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112896694589213623/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112896694589213623&amp;isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112896694589213623'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112896694589213623'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/10/how-do-you-execute-tests.html' title='How do you execute tests?'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112896652702915799</id><published>2005-10-12T15:14:00.000+01:00</published><updated>2005-10-12T13:39:25.833+01:00</updated><title type='text'>How do you create a test plan/design?</title><summary type='text'>Test scenarios and/or cases are prepared by reviewing functional requirements of the release and preparing logical groups of functions that can be further broken into test procedures. Test procedures define test conditions, data to be used for testing and expected results, including database updates, file outputs, report results..   Test cases and scenarios are designed to represent both typical </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112896652702915799/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112896652702915799&amp;isPopup=true' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112896652702915799'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112896652702915799'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/10/how-do-you-create-test-plandesign.html' title='How do you create a test plan/design?'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112896619675147945</id><published>2005-10-11T16:41:00.000+01:00</published><updated>2005-10-21T20:59:11.446+01:00</updated><title type='text'>How do you create a Test Strategy?</title><summary type='text'>The test strategy is a formal description of how a software product will be tested. A test strategy is developed for all levels of testing, as required. The test team analyzes the requirements, writes the test strategy and reviews the plan with the project team. The test plan may include test cases, conditions, the test environment, a list of related tasks, pass/fail criteria and risk assessment.</summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112896619675147945/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112896619675147945&amp;isPopup=true' title='4 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112896619675147945'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112896619675147945'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/10/how-do-you-create-test-strategy.html' title='How do you create a Test Strategy?'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>4</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112896603638323377</id><published>2005-10-10T18:36:00.000+01:00</published><updated>2005-10-19T16:46:25.266+01:00</updated><title type='text'>What is software testing methodology?</title><summary type='text'>A software testing methodology is the use of a three step process of:1. Creating a test strategy;2. Creating a test plan/design; and3. Executing tests.This methodology can be used and molded to your organization's needs. Using this methodology is important in the development and in ongoing maintenance of the customers' applications.</summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112896603638323377/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112896603638323377&amp;isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112896603638323377'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112896603638323377'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/10/what-is-software-testing-methodology.html' title='What is software testing methodology?'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112851822738818183</id><published>2005-10-05T15:02:00.000+01:00</published><updated>2006-09-01T15:49:02.003+01:00</updated><title type='text'>Usability Testing</title><summary type='text'>What is Software Usability?According to ISO 9241-11 (1998), usability is the “extent to which a product can be used by specified usersto achieve specified goals with effectiveness, efficiency and satisfaction in a specified context of use.”What is Usability Testing?Usability testing refers to evaluating the ease with which users can learn and use a product. The scope of this phrase, however, can </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112851822738818183/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112851822738818183&amp;isPopup=true' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112851822738818183'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112851822738818183'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/10/usability-testing.html' title='Usability Testing'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112844322798634040</id><published>2005-10-04T17:20:00.000+01:00</published><updated>2005-10-04T17:27:08.000+01:00</updated><title type='text'>Performance measurement parameters for a tester</title><summary type='text'>Software testing is not about finding bugs. It's about delivering great software. No customer ever said with a straight face, "Wow! You found and fixed 65,000 bugs—that must be really great software!" So, why do many currently use bug counts as a measurement tool? The answer is simple: Bugs are just so darn countable that they are practically irresistible.   They can be counted, tracked, and used</summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112844322798634040/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112844322798634040&amp;isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112844322798634040'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112844322798634040'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/10/performance-measurement-parameters-for.html' title='Performance measurement parameters for a tester'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112689444107393102</id><published>2005-09-30T16:10:00.000+01:00</published><updated>2005-09-30T15:40:19.703+01:00</updated><title type='text'>Test Case Maintenance</title><summary type='text'>Changes to Product features can happen many times during a product development lifecycle. These may be driven by change of customer requirements, design changes or some times as late as customer acceptance tests. Many times, making necessary changes reported by customers can be crucial. In such scenarios test cases drawn by Test Engineers can become obsolete rendering the whole effort in test </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112689444107393102/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112689444107393102&amp;isPopup=true' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112689444107393102'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112689444107393102'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/09/test-case-maintenance.html' title='Test Case Maintenance'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112688819346723673</id><published>2005-09-28T16:28:00.000+01:00</published><updated>2006-08-08T18:43:56.880+01:00</updated><title type='text'>KPA in CMM</title><summary type='text'>The Key Process Areas (KPAs) define "building blocks" based on industry best practices. Theultimate goal is to establish "continual improvement" of the software engineering process and the resulting products. The KPAs of lower levels focus mainly on management processes (and industry minimal standards). While the KPAs of higher levels focus more on organizational and technical processes (and more</summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112688819346723673/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112688819346723673&amp;isPopup=true' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112688819346723673'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112688819346723673'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/09/kpa-in-cmm.html' title='KPA in CMM'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112689323510819557</id><published>2005-09-27T15:39:00.000+01:00</published><updated>2005-09-27T13:53:43.086+01:00</updated><title type='text'>Localization Testing</title><summary type='text'>Around one year ago I got the shock of my life as a tester when my Lead asked me to test our product for the localized versions. I was supposed to test our product on French and German platforms and one can imagine my condition as I didn’t have a faintest idea about either French or German. That was my first encounter with Localization Testing. It was not as bad as it sounds and in fact after a </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112689323510819557/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112689323510819557&amp;isPopup=true' title='4 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112689323510819557'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112689323510819557'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/09/localization-testing.html' title='Localization Testing'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>4</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112732125525101079</id><published>2005-09-23T15:30:00.000+01:00</published><updated>2006-03-23T13:21:27.150Z</updated><title type='text'>Responsibilities of a QA Engineer</title><summary type='text'>Title of the post should ideally be "Responsibilities of a Test Engineer" :D− Understand project requirements. − Prepare / Update the Test case document for testing of the application from all aspects. − Prepare the test setup. − Deploy the build in the required setup. − Conduct the Testing including Smoke, Sanity, and Bug Bash / Execute the Test cases. − Update the Test Result document. − Attend</summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112732125525101079/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112732125525101079&amp;isPopup=true' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112732125525101079'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112732125525101079'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/09/responsibilities-of-qa-engineer.html' title='Responsibilities of a QA Engineer'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112689211340935823</id><published>2005-09-22T15:20:00.000+01:00</published><updated>2005-09-22T14:34:34.710+01:00</updated><title type='text'>Exploratory Testing</title><summary type='text'>Have you ever tested a piece of software that you were not very familiar with? Also, you might not have had the luxury of ready-made test cases at hand and could not afford spending time to write them. Nevertheless you went ahead to test the product and did a quite a good job. If you remember, it required a lot of logical thinking, formulating your thoughts into test cases in real time and </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112689211340935823/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112689211340935823&amp;isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112689211340935823'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112689211340935823'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/09/exploratory-testing.html' title='Exploratory Testing'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112689638282897196</id><published>2005-09-21T15:32:00.000+01:00</published><updated>2005-09-21T15:30:51.656+01:00</updated><title type='text'>What You Don't Know May Help You</title><summary type='text'>Some testers take it upon themselves to learn as much as possible about the inner workings of the system under test. This type of "gray box" testing is valuable, and most testers have the technical wherewithal to grasp much of what's going on behind the scenes. But it's important to recognize that sometimes "ignorance is strength" when it comes to finding problems that users will encounter.When </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112689638282897196/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112689638282897196&amp;isPopup=true' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112689638282897196'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112689638282897196'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/09/what-you-dont-know-may-help-you.html' title='What You Don&apos;t Know May Help You'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112681070487084021</id><published>2005-09-20T15:10:00.000+01:00</published><updated>2005-09-20T10:03:39.460+01:00</updated><title type='text'>Checklist for conducting Unit Tests</title><summary type='text'>- Is the number of input parameters equal to number of arguments?- Do parameter and argument attributes match?- Do parameter and argument units system match?- Is the number of arguments transmitted to called modules equal to number of parameters?- Are the attributes of arguments transmitted to called modules equal to attributes of parameters?- Is the units system of arguments transmitted to </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112681070487084021/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112681070487084021&amp;isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112681070487084021'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112681070487084021'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/09/checklist-for-conducting-unit-tests.html' title='Checklist for conducting Unit Tests'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112688984295365339</id><published>2005-09-19T15:56:00.000+01:00</published><updated>2005-09-19T15:21:20.563+01:00</updated><title type='text'>Spike Testing</title><summary type='text'>Spike Test is used in terms of Load/Performance testing. Spike Tests are tests that use real-worlddistributions and user communities, but under extremely fast ramp up and ramp down times. It is common to execute stress tests that ramp up to 100% or 150% of expected peak expected user-load in a matter of minutes rather than about an hour.</summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112688984295365339/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112688984295365339&amp;isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112688984295365339'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112688984295365339'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/09/spike-testing.html' title='Spike Testing'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112689081557766717</id><published>2005-09-17T15:13:00.000+01:00</published><updated>2005-09-17T10:30:43.090+01:00</updated><title type='text'>Need of Test Plan and Test Cases for testing</title><summary type='text'>Test Plan identifies the test activities and also defines the objective, approach, and schedule of intended testing activities, while Test Cases comprises of the test procedure, test conditions and expected result. Writing a test plan early in the project lifecycle, and having it peer reviewed by Development  in general helps reduce the workload later in the project lifecycle. This allows testers</summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112689081557766717/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112689081557766717&amp;isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112689081557766717'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112689081557766717'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/09/need-of-test-plan-and-test-cases-for.html' title='Need of Test Plan and Test Cases for testing'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112680908128712701</id><published>2005-09-16T16:27:00.000+01:00</published><updated>2005-09-16T16:20:50.350+01:00</updated><title type='text'>Professional Characteristics of a good SQA Engineer</title><summary type='text'>Professional characteristics of a good QA (Quality Assurnace) Engineer:• Understanding of business approach and goals of the organization• Understanding of entire software development process• Strong desire for quality• Establish and enforce SQA methodologies, processes and Testing Strategies• Judgment skills to assess high-risk areas of application• Communication with Analysis and Development </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112680908128712701/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112680908128712701&amp;isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112680908128712701'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112680908128712701'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/09/professional-characteristics-of-good.html' title='Professional Characteristics of a good SQA Engineer'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112680825314203570</id><published>2005-09-15T19:07:00.000+01:00</published><updated>2005-09-15T19:17:33.266+01:00</updated><title type='text'>Test Case Checklist</title><summary type='text'>Here is a checklist for having well-documented test cases:Quality Attributes -     Accurate - tests what the description says it will test. -     Economical - has only the steps needed for its purpose -     Repeatable, self standing - same results no matter who tests it. -     Appropriate - for both immediate and future testers -     Traceable - to a requirement -     Self cleaning - returns the </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112680825314203570/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112680825314203570&amp;isPopup=true' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112680825314203570'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112680825314203570'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/09/test-case-checklist.html' title='Test Case Checklist'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112619911989383424</id><published>2005-09-13T16:02:00.000+01:00</published><updated>2005-09-13T14:54:10.646+01:00</updated><title type='text'>Smoke Testing</title><summary type='text'>Smoke testing is a relatively simple check to see whether the product "smokes" when it runs. Smoke testing is also sometimes known as ad hoc testing, i.e. testing without a formal test plan.With many projects, smoke testing is carried out in addition to formal testing. If smoke testing is carried out by a skilled tester, it can often find problems that are not caught during regular testing. </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112619911989383424/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112619911989383424&amp;isPopup=true' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112619911989383424'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112619911989383424'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/09/smoke-testing.html' title='Smoke Testing'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112619804750903666</id><published>2005-09-12T15:44:00.000+01:00</published><updated>2005-09-12T13:55:05.710+01:00</updated><title type='text'>Difference between System Testing and Integration Testing</title><summary type='text'>System testing is high level testing, and integration testing is a lower level testing. Integration testing is completed first, not the system testing. In other words, upon completion of integration testing, system testing is started, and not vice versa. For integration testing, test cases are developed with the express purpose of exercising the interfaces between the components. For system </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112619804750903666/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112619804750903666&amp;isPopup=true' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112619804750903666'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112619804750903666'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/09/difference-between-system-testing-and.html' title='Difference between System Testing and Integration Testing'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112619737960561888</id><published>2005-09-10T15:33:00.000+01:00</published><updated>2006-09-14T13:37:31.280+01:00</updated><title type='text'>How can software QA processes be implemented without stifling productivity?</title><summary type='text'>Implement QA processes slowly over time. Use consensus to reach agreement on processes and adjust and experiment as an organization grows and matures. Productivity will be improved instead of stifled. Problem prevention will lessen the need for problem detection. Panics and burnout will decrease and there will be improved focus and less wasted effort. At the same time, attempts should be made to </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112619737960561888/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112619737960561888&amp;isPopup=true' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112619737960561888'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112619737960561888'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/09/how-can-software-qa-processes-be.html' title='How can software QA processes be implemented without stifling productivity?'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112619709686351790</id><published>2005-09-09T15:29:00.000+01:00</published><updated>2005-09-09T14:50:16.640+01:00</updated><title type='text'>What makes a good QA/Test Manager?</title><summary type='text'>QA/Test Managers are - familiar with the software development process- able to maintain enthusiasm of their team and promote a positive atmosphere- able to promote teamwork to increase productivity- able to promote cooperation between Software and Test/QA Engineers- have the people skills needed to promote improvements in QA processes- have the ability to withstand pressures and say *no* to other</summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112619709686351790/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112619709686351790&amp;isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112619709686351790'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112619709686351790'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/09/what-makes-good-qatest-manager.html' title='What makes a good QA/Test Manager?'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112619693473234207</id><published>2005-09-08T17:25:00.000+01:00</published><updated>2005-09-08T17:28:54.740+01:00</updated><title type='text'>Do automated testing tools make testing easier?</title><summary type='text'>Yes and no. For larger projects, or ongoing long-term projects, they can be valuable. But for small projects, the time needed to learn and implement them is usually not worthwhile. A common type of automated tool is the record/playback type. For example, a test engineer clicks through all combinations of menu choices, dialog box choices, buttons, etc. in a GUI and has an automated testing tool </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112619693473234207/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112619693473234207&amp;isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112619693473234207'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112619693473234207'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/09/do-automated-testing-tools-make.html' title='Do automated testing tools make testing easier?'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112558069876428896</id><published>2005-09-05T15:15:00.000+01:00</published><updated>2005-09-05T15:28:02.640+01:00</updated><title type='text'>Installation Testing</title><summary type='text'>Installation testing is often the most under tested area in testing. This type of testing is performed to ensure that all Installed features and options function properly. It is also performed to verify that all necessary components of the application are, indeed, installed.Installation testing should take care of the following points: - 1. To check if while installing product checks for the </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112558069876428896/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112558069876428896&amp;isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112558069876428896'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112558069876428896'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/09/installation-testing.html' title='Installation Testing'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112558044289839147</id><published>2005-09-02T15:07:00.000+01:00</published><updated>2005-09-02T14:30:22.906+01:00</updated><title type='text'>Regression Testing</title><summary type='text'>Regression testing as the name suggests is used to test / check the effect of changes made in the code.Most of the time the testing team is asked to check last minute changes in the code just before making a release to the client, in this situation the testing team needs to check only the affected areas.So in short for the regression testing the testing team should get the input from the </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112558044289839147/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112558044289839147&amp;isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112558044289839147'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112558044289839147'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/09/regression-testing.html' title='Regression Testing'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112558001457289035</id><published>2005-09-01T14:01:00.000+01:00</published><updated>2005-09-01T14:06:54.576+01:00</updated><title type='text'>Content Management Testing</title><summary type='text'>‘Content Management’ has gained a predominant importance after the Web applications took a major part of our lives. What is Content Management? As the name denotes, it is managing the content. How do they work? Let us take a common example. You are in China and you wanted to open the Yahoo! Chinese version. When you choose Chinese version on the main page of Yahoo! You get to see the entire </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112558001457289035/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112558001457289035&amp;isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112558001457289035'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112558001457289035'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/09/content-management-testing.html' title='Content Management Testing'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112541826287688037</id><published>2005-08-31T16:58:00.000+01:00</published><updated>2005-08-31T17:18:52.303+01:00</updated><title type='text'>How objective is your qc?</title><summary type='text'>QC people have a special role in the development process. Part of this role is being involved in different activities throughout the entire development process. Starting from the time when requirements are gathered, when initial design is made, and until the end of each iteration, the QC people must observe and gather information about the system under development. This is crucial to the </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112541826287688037/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112541826287688037&amp;isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112541826287688037'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112541826287688037'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/08/how-objective-is-your-qc.html' title='How objective is your qc?'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112541708305726800</id><published>2005-08-30T16:31:00.000+01:00</published><updated>2005-08-31T17:25:21.326+01:00</updated><title type='text'>Rapid Testing</title><summary type='text'>Rapid testing means testing software faster than you do now, while maintaining or improving your standards of quality. Unfortunately, there is no simple way to achieve rapid testing. The figure shows a somewhat simplistic sketch that represents rapid testing as a structure that is built on a foundation of four components. If any of these components is weak, the effectiveness of testing will be </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112541708305726800/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112541708305726800&amp;isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112541708305726800'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112541708305726800'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/08/rapid-testing.html' title='Rapid Testing'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112498194255497449</id><published>2005-08-26T15:51:00.000+01:00</published><updated>2005-08-26T15:35:39.443+01:00</updated><title type='text'>Introducing Automated Software Testing in your project</title><summary type='text'>First determine if your product is stable and ready for automation. Then get your testers together along with your immediate manager and do a brainstorm on the requirements needed for a tool. Then put together a Planning and Scope document of your proposals and get buy-in from senior management. Take your requirements list and formalize it then send it to the Vendors of the tools which you think </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112498194255497449/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112498194255497449&amp;isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112498194255497449'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112498194255497449'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/08/introducing-automated-software-testing.html' title='Introducing Automated Software Testing in your project'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112317580944441510</id><published>2005-08-25T15:20:00.000+01:00</published><updated>2005-08-25T14:10:32.130+01:00</updated><title type='text'>Rules for Automation</title><summary type='text'>Rule #1 of automation: "If you can not logically describe what you are testing, you can't automate it."If you are testing specific items, then you may be able to do it. (e.g. Click on a specific button, check for the title of the box, fill in the box, check to make sure that the grayed out button becomes available). But for the UI test to be able to figure out that the background is not grayed </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112317580944441510/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112317580944441510&amp;isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112317580944441510'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112317580944441510'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/08/rules-for-automation.html' title='Rules for Automation'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112481132284903714</id><published>2005-08-24T15:12:00.000+01:00</published><updated>2005-08-24T14:14:17.846+01:00</updated><title type='text'>What if there isn't enough time for thorough testing?</title><summary type='text'>Since it's rarely possible to test every possible aspect of an application, every possible combination of events, every dependency, or everything that could go wrong, risk analysis is appropriate to most software development projects. Use risk analysis to determine where testing should be focused. This requires judgment skills, common sense and experience. The checklist should include answers to </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112481132284903714/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112481132284903714&amp;isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112481132284903714'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112481132284903714'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/08/what-if-there-isnt-enough-time-for.html' title='What if there isn&apos;t enough time for thorough testing?'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112480769249628313</id><published>2005-08-23T15:32:00.000+01:00</published><updated>2005-08-23T15:34:52.503+01:00</updated><title type='text'>Most Critical Web Application Security Vulnerabilities</title><summary type='text'>1. Unvalidated InputInformation from web requests is not validated before being used by a web application. Attackers can use these flaws to attack backend components through a web application.2. Broken Access ControlRestrictions on what authenticated users are allowed to do are not properly enforced. Attackers can exploit these flaws to access other users' accounts, view sensitive files, or use </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112480769249628313/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112480769249628313&amp;isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112480769249628313'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112480769249628313'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/08/most-critical-web-application-security.html' title='Most Critical Web Application Security Vulnerabilities'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112445597698019430</id><published>2005-08-20T15:19:00.000+01:00</published><updated>2005-08-20T12:09:38.370+01:00</updated><title type='text'>Standards For Testing An Application</title><summary type='text'>The General testing standards for testing any type of application based on various factors are listed below:1. Look &amp; Feel -&gt; Uniformity in terms of Content, Title, Position (Should be displayed at the center of any User Interface (UI)) of message boxes.-&gt; Enabling &amp; Disabling of menu items/icons according to the user security.-&gt; Ensure menu items are invoked as set in user security. If the </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112445597698019430/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112445597698019430&amp;isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112445597698019430'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112445597698019430'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/08/standards-for-testing-application.html' title='Standards For Testing An Application'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112444148347081965</id><published>2005-08-19T15:05:00.000+01:00</published><updated>2005-08-19T09:51:23.510+01:00</updated><title type='text'>Defect Taxonomies</title><summary type='text'>Categories of DefectsAll software defects can be broadly categorized into the below mentioned types:    •          Errors of commission: something wrong is done    •          Errors of omission: something left out by accident    •          Errors of clarity and ambiguity: different interpretations    •          Errors of speed and capacityHowever, the above is a broad categorization; below is a </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112444148347081965/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112444148347081965&amp;isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112444148347081965'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112444148347081965'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/08/defect-taxonomies.html' title='Defect Taxonomies'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112443424548990300</id><published>2005-08-19T07:39:00.000+01:00</published><updated>2005-10-03T17:23:51.570+01:00</updated><title type='text'>Test Development Life Cycle</title><summary type='text'>Usually, Testing is considered as a part of the System Development Life Cycle, but it can be also termed as Test Development Life Cycle or Software Testing Life Cycle.The diagram does not depict where and when you write your Test Plan and Strategy documents. But, it is understood that before you begin your testing activities these documents should be ready. Ideally, when the Project Plan and </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112443424548990300/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112443424548990300&amp;isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112443424548990300'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112443424548990300'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/08/test-development-life-cycle.html' title='Test Development Life Cycle'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112428308592507669</id><published>2005-08-17T13:51:00.000+01:00</published><updated>2005-08-17T14:17:12.260+01:00</updated><title type='text'>Bug Count Vs Test Coverage</title><summary type='text'>Bug counts on a project speak volumes about the quality of testing for a particular product and how vigorous the test team is working to "assure quality". Bug counts are invariably a primary area of test metrics that are reported to management. What is the rationale behind drawing so much attention to the number of bugs being found through the course of a project? &lt;?xml:namespace prefix = o /&gt;I </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112428308592507669/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112428308592507669&amp;isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112428308592507669'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112428308592507669'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/08/bug-count-vs-test-coverage.html' title='Bug Count Vs Test Coverage'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112418166493822349</id><published>2005-08-16T19:32:00.000+01:00</published><updated>2005-08-16T13:38:34.440+01:00</updated><title type='text'>When to start and stop Testing?</title><summary type='text'>Testing is sometimes incorrectly thought as an after-the-fact activity; performed after programming is done for a product. Instead, testing should be performed at every development stage of the product. Test data sets must be derived and their correctness and consistency should be monitored throughout the development process. If we divide the lifecycle of software development into “Requirements </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112418166493822349/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112418166493822349&amp;isPopup=true' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112418166493822349'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112418166493822349'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/08/when-to-start-and-stop-testing.html' title='When to start and stop Testing?'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112412396635429533</id><published>2005-08-15T17:26:00.000+01:00</published><updated>2005-08-15T17:48:48.976+01:00</updated><title type='text'>Types of Black Box Testing</title><summary type='text'>Acceptance testingAlpha testingBeta testingComparison testing Computability testing End-to-end testing Functional testing Incremental integration testingInstall/uninstall testing Integration testingLoad testingPerformance testing Recovery testingRegression testing Sanity testingSecurity testing System testingUsability testingVisit http://quality-assurance-software-testing.blogspot.com/2005/07/</summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112412396635429533/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112412396635429533&amp;isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112412396635429533'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112412396635429533'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/08/types-of-black-box-testing.html' title='Types of Black Box Testing'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112374321472428411</id><published>2005-08-12T07:51:00.000+01:00</published><updated>2005-08-12T06:20:58.786+01:00</updated><title type='text'>Software Testing - 10 Rules</title><summary type='text'>1. Test early and test often.2. Integrate the application development and testing life cycles. You'll get better results.3. Formalize a testing methodology; you'll test everything the same way and you'll get uniform results.4. Develop a comprehensive test plan; it forms the basis for the testing methodology.5. Use both static and dynamic testing.6. Define your expected results.7. Understand the </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112374321472428411/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112374321472428411&amp;isPopup=true' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112374321472428411'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112374321472428411'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/08/software-testing-10-rules.html' title='Software Testing - 10 Rules'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112368732237539689</id><published>2005-08-10T15:44:00.000+01:00</published><updated>2005-08-10T16:22:02.416+01:00</updated><title type='text'>Ten tips to write better bug reports</title><summary type='text'>Applying the following ten tips will help you achieve better bug/defect reports:1. StructureA tester who uses a deliberate, careful approach to testing, and takes careful notes, tends to have a good idea of what’s going on with the system under test. When failures occur, she knows when the first signs of failure manifested themselves.2. ReproduceThe tester should check reproducibility of a </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112368732237539689/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112368732237539689&amp;isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112368732237539689'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112368732237539689'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/08/ten-tips-to-write-better-bug-reports.html' title='Ten tips to write better bug reports'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112368496321707708</id><published>2005-08-10T15:34:00.000+01:00</published><updated>2005-08-10T15:42:43.223+01:00</updated><title type='text'>Benefits of Automated Testing</title><summary type='text'>Manually testing software is a time-consuming and often tedious process, one which cannot guarantee consistency of testing across releases and across platforms. Additionally, time constraints often do not afford us the luxury of being able to manually test and retest our applications before they are released. Inevitably the question remains, “Did any critical bugs go undetected?”Automating your </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112368496321707708/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112368496321707708&amp;isPopup=true' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112368496321707708'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112368496321707708'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/08/benefits-of-automated-testing.html' title='Benefits of Automated Testing'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112230944080433972</id><published>2005-08-07T19:30:00.000+01:00</published><updated>2005-08-09T16:31:43.683+01:00</updated><title type='text'>Quality Control Issues and Testing</title><summary type='text'>Why Testing/Quality Assurance?Rising customer expectations for fault free requirements-exact software has increased awareness of the importance of software testing as a critical activity. The payoffs from QA/testing are in form of customer satisfaction, reduced costs taking quality in consideration, efficient processes.Who is responsible for testing?Contradicting the myths, quality is everyone's </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112230944080433972/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112230944080433972&amp;isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112230944080433972'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112230944080433972'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/08/quality-control-issues-and-testing.html' title='Quality Control Issues and Testing'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112308660491607670</id><published>2005-08-06T17:22:00.000+01:00</published><updated>2005-08-06T19:45:02.956+01:00</updated><title type='text'>Testing Interview Questions</title><summary type='text'>Here are some questions you might be asked on a job interview for a testing opening: 1. Why did you ever become involved in QA/testing?2. What is the testing lifecycle and explain each of its phases?3. What is the difference between testing and Quality Assurance?4. What is Negative testing?5. What was a problem you had in your previous assignment (testing if possible)? How did you resolve it?6. </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112308660491607670/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112308660491607670&amp;isPopup=true' title='9 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112308660491607670'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112308660491607670'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/08/testing-interview-questions.html' title='Testing Interview Questions'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>9</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112288995026942596</id><published>2005-08-05T18:48:00.000+01:00</published><updated>2005-08-05T13:31:04.110+01:00</updated><title type='text'>Difference between Load and Stress Testing.</title><summary type='text'>One of the most common misuse of terminology is treating "Load Testing" and "Stress Testing" as synonymous. The consequence of this ignorant semantic abuse is usually that the system is neither properly "load tested" nor subjected to a meaningful stress test.1. Stress testing is subjecting a system to an unreasonable load while denying it the resources (e.g., RAM, disc, mips, interrupts, etc.) </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112288995026942596/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112288995026942596&amp;isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112288995026942596'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112288995026942596'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/08/difference-between-load-and-stress.html' title='Difference between Load and Stress Testing.'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112308897618715200</id><published>2005-08-04T17:56:00.000+01:00</published><updated>2005-08-04T17:47:21.703+01:00</updated><title type='text'>How does one make a good tester ?</title><summary type='text'>For starters, formal training and gaining experience in both:1. Manual testing, and2. Quality AssuranceTechnical:1. Understanding of systems and software2. Programming skills are helpfulSkills a good SQA person has to have:- 'test to break' attitude, - Ability to take the point of view of the customer, - Strong desire for quality, - Attention to detail. - Tact and diplomacy are useful in </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112308897618715200/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112308897618715200&amp;isPopup=true' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112308897618715200'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112308897618715200'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/08/how-does-one-make-good-tester.html' title='How does one make a good tester ?'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112308311648076191</id><published>2005-08-04T13:43:00.000+01:00</published><updated>2005-08-04T13:47:12.810+01:00</updated><title type='text'>Gray Box Testing</title><summary type='text'>Even though you probably don't have full knowledge of the internals of the product you test, a test strategy based partly on internals is a powerful idea. This can be called as gray box testing. The concept is simple: If you know something about how the product works on the inside, you can test it better from the outside. This is not to be confused with white box testing, which attempts to cover </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112308311648076191/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112308311648076191&amp;isPopup=true' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112308311648076191'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112308311648076191'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/08/gray-box-testing.html' title='Gray Box Testing'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112288961187402786</id><published>2005-08-03T10:43:00.000+01:00</published><updated>2005-08-03T12:55:13.316+01:00</updated><title type='text'>Black box/white box testing</title><summary type='text'>Black-box and white-box are test design methods. Black-box test design treats the system as a "black-box", so it doesn't explicitly use knowledge of the internal structure. Black-box test design is usually described as focusing on testing functional requirements. Synonyms for black-box include: behavioral, functional, opaque-box, and closed-box. White-box test design allows one to peek inside the</summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112288961187402786/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112288961187402786&amp;isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112288961187402786'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112288961187402786'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/08/black-boxwhite-box-testing.html' title='Black box/white box testing'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112288636727989425</id><published>2005-08-02T09:35:00.000+01:00</published><updated>2006-06-21T12:21:35.763+01:00</updated><title type='text'>Web Applications Testing</title><summary type='text'>Web-based applications present new challenges, these challenges include:- Short release cycles;- Constantly Changing Technology;- Possible huge number of users during initial website launch;- Inability to control the user's running environment;- 24-hour availability of the web site.The quality of a website must be evident from the Onset. Any difficulty whether in response time, accuracy of </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112288636727989425/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112288636727989425&amp;isPopup=true' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112288636727989425'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112288636727989425'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/08/web-applications-testing.html' title='Web Applications Testing'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112266301920929876</id><published>2005-07-29T19:47:00.000+01:00</published><updated>2005-08-15T17:44:12.396+01:00</updated><title type='text'>Testing Methodologies</title><summary type='text'>Acceptance TestingTesting the system with the intent of confirming readiness of the product and customer acceptance. Acceptance testing, which is a black box testing, will give the client the opportunity to verify the system functionality and usability prior to the system being moved to production. The acceptance test will be the responsibility of the client; however, it will be conducted with </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112266301920929876/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112266301920929876&amp;isPopup=true' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112266301920929876'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112266301920929876'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/07/testing-methodologies.html' title='Testing Methodologies'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112247809642103097</id><published>2005-07-27T16:27:00.000+01:00</published><updated>2005-07-27T16:28:16.423+01:00</updated><title type='text'>What is Testing?</title><summary type='text'>Testing is the process of identifying defects, where a defect is any variance between actual and expected results.Defect can be caused by a flaw in the application software or by a flaw in the application specification. For example, unexpected (incorrect) results can be from errors made during the construction phase, or from an algorithm incorrectly defined in the specification. Testing is </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112247809642103097/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112247809642103097&amp;isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112247809642103097'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112247809642103097'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/07/what-is-testing.html' title='What is Testing?'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112231066776809510</id><published>2005-07-25T17:48:00.000+01:00</published><updated>2005-07-27T16:11:42.276+01:00</updated><title type='text'>What is SEI? CMM? CMMI? ISO? IEEE? ANSI?</title><summary type='text'>SEI = 'Software Engineering Institute' at Carnegie-Mellon University; initiated by the U.S. Defense Department to help improve software development processes.CMM = 'Capability Maturity Model', now called the CMMI ('Capability Maturity Model Integration'), developed by the SEI. It's a model of 5 levels of process 'maturity' that determine effectiveness in delivering quality software. It is geared </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112231066776809510/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112231066776809510&amp;isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112231066776809510'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112231066776809510'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/07/what-is-sei-cmm-cmmi-iso-ieee-ansi.html' title='What is SEI? CMM? CMMI? ISO? IEEE? ANSI?'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112230884601904811</id><published>2005-07-25T17:19:00.000+01:00</published><updated>2005-07-27T16:12:13.146+01:00</updated><title type='text'>Advantages in a process driven organization</title><summary type='text'>Imagine a situation that you have to start working in a project from the middle, in spite of being new to this project, you are bound to deliver the best anytime and every time andthat is expected this time too. There is no documentation available in that project, there are no processes how to carry out the tasks and there is noting in place. Your PM is too busy to devote full time to you to </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112230884601904811/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112230884601904811&amp;isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112230884601904811'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112230884601904811'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/07/advantages-in-process-driven.html' title='Advantages in a process driven organization'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112230722871020157</id><published>2005-07-25T16:53:00.000+01:00</published><updated>2006-07-18T05:29:44.466+01:00</updated><title type='text'>Difference between QA and QC</title><summary type='text'>What is Software Quality?Though there are a number of definitions propounded by the gurus in the field - each having its own adherents, two definitions that are widely accepted and that are complementary to each other are:- Conformance to explicitly stated functional and performance requirements, explicitly documented development standards, and implicit characteristics that are expected of all </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112230722871020157/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112230722871020157&amp;isPopup=true' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112230722871020157'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112230722871020157'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/07/difference-between-qa-and-qc.html' title='Difference between QA and QC'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-112374341548969094</id><published>2005-07-25T16:50:00.000+01:00</published><updated>2006-02-03T07:08:10.246Z</updated><title type='text'>Software Testing Glossary</title><summary type='text'>Acceptance TestingTesting conducted to enable a user/customer to determine whether to accept a software product. Normally performed to validate the software meets a set of agreed acceptance criteria. Accessibility TestingVerifying a product is accessible to the people having disabilities (deaf, blind, mentally disabled etc.).Ad Hoc TestingA testing phase where the tester tries to 'break' the </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/112374341548969094/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=112374341548969094&amp;isPopup=true' title='3 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112374341548969094'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/112374341548969094'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/07/software-testing-glossary.html' title='Software Testing Glossary'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>3</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14775571.post-113880868888127405</id><published>2005-07-01T15:39:00.000+01:00</published><updated>2006-02-12T13:41:09.313Z</updated><title type='text'>Software Testing books - Amazon.com</title><summary type='text'>The best thing about "Testing Computer Software" is its practical point-by-point guide to everyday software testing, from creating a test plan, to writing effective bug reports, to working with programming staff and management to fix bugs.Topics covered: test case design, test planning, project lifecycle overview, software errors, boundary conditions, bug reports, regression testing, black box </summary><link rel='replies' type='application/atom+xml' href='http://quality-assurance-software-testing.blogspot.com/feeds/113880868888127405/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14775571&amp;postID=113880868888127405&amp;isPopup=true' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/113880868888127405'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14775571/posts/default/113880868888127405'/><link rel='alternate' type='text/html' href='http://quality-assurance-software-testing.blogspot.com/2005/07/software-testing-books-amazoncom.html' title='Software Testing books - Amazon.com'/><author><name>Techie</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry></feed>
