<?xml version='1.0' encoding='UTF-8'?><rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearchrss/1.0/" xmlns:blogger="http://schemas.google.com/blogger/2008" xmlns:georss="http://www.georss.org/georss" xmlns:gd="http://schemas.google.com/g/2005" xmlns:thr="http://purl.org/syndication/thread/1.0" version="2.0"><channel><atom:id>tag:blogger.com,1999:blog-37776098</atom:id><lastBuildDate>Thu, 07 Mar 2024 08:28:26 +0000</lastBuildDate><category>Firmware</category><category>Unlock</category><category>iPhone</category><title>Software Quality Testing</title><description>Software Quality Testing is a Blog dedicated to extensive Software Quality Assurance and Software Testing information. This is intended to be an one-stop Information Center for all your Software Quality and Testing needs.</description><link>http://software-quality-testing.blogspot.com/</link><managingEditor>noreply@blogger.com (Debasis Pradhan)</managingEditor><generator>Blogger</generator><openSearch:totalResults>51</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><item><guid isPermaLink="false">tag:blogger.com,1999:blog-37776098.post-5112091606165599154</guid><pubDate>Mon, 30 Mar 2009 08:00:00 +0000</pubDate><atom:updated>2009-07-06T19:26:13.721+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">Firmware</category><category domain="http://www.blogger.com/atom/ns#">iPhone</category><category domain="http://www.blogger.com/atom/ns#">Unlock</category><title>Unlock any iPhone in minutes!</title><atom:summary type="text">A couple of weeks back while on a conversation with a friend from CA, she expressed concern over how it was ridiculous for Apple to lock its iPhone only to be used by AT&amp;amp;T network! She was looking for a possibility if she could ever unlock her Apple iPhone 3G and be able to use it with other networks. I was searching over the net for any such resources and came upon this excellent looking </atom:summary><link>http://software-quality-testing.blogspot.com/2009/03/unlock-any-iphone-in-minutes.html</link><author>noreply@blogger.com (Debasis Pradhan)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-37776098.post-2913994219176415544</guid><pubDate>Sun, 22 Apr 2007 06:33:00 +0000</pubDate><atom:updated>2007-04-22T12:05:21.119+05:30</atom:updated><title>New Load Testing Tool Released for UltraLightClient</title><atom:summary type="text">From: PRWebCanoo Engineering has announced that it has released a new version of its load testing tool for UltraLightClient, ULC Load. The tool analyses the performance data of UltraLightClient-based applications.Since the last version, ULC Load has been completely re-implemented to offer improved testing functionality for Java RIA development with UltraLightClient. New features include improved </atom:summary><link>http://software-quality-testing.blogspot.com/2007/04/new-load-testing-tool-released-for.html</link><author>noreply@blogger.com (Debasis Pradhan)</author><thr:total>2</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-37776098.post-897198160306243281</guid><pubDate>Tue, 10 Apr 2007 18:32:00 +0000</pubDate><atom:updated>2007-04-11T00:24:02.013+05:30</atom:updated><title>Testing Master - Website Testing Tool (Review)</title><atom:summary type="text">Today I came across this wonderful Website testing tool. Testing Master is website testing tool for load stress and performance testing web sites and web applications. Testing Master is an easy-to-use and affordable website testing tool. It tests the performance of web sites or intranet applications by load and stress testing and helps you to find bottlenecks of your web site. Web site testing </atom:summary><link>http://software-quality-testing.blogspot.com/2007/04/testing-master-website-testing-tool.html</link><author>noreply@blogger.com (Debasis Pradhan)</author><thr:total>2</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-37776098.post-4096131530155322516</guid><pubDate>Sat, 03 Feb 2007 15:02:00 +0000</pubDate><atom:updated>2007-02-03T20:34:14.108+05:30</atom:updated><title>2007 conference for the association of software testing (CAST2007)</title><atom:summary type="text">Call for papers for the Conference for the Association of Software TestingJuly 9 - 11, 2007Meydenbauer Center, Bellevue, WA. For more details Check 2007 conference for the association of software testing (CAST2007).</atom:summary><link>http://software-quality-testing.blogspot.com/2007/02/2007-conference-for-association-of.html</link><author>noreply@blogger.com (Debasis Pradhan)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-37776098.post-5976964721572949385</guid><pubDate>Sat, 03 Feb 2007 14:41:00 +0000</pubDate><atom:updated>2007-02-03T20:15:25.730+05:30</atom:updated><title>Why is most software so bad?</title><atom:summary type="text">(from an interview with Bjarne Soustroup in techreview.com) Technology Review: Why is most software so bad? Bjarne Stroustrup: Some software is actually pretty good by any standards. Think of the Mars Rovers, Google, and the Human Genome Project. That&#39;s quality software! Fifteen years ago, most people, and especially most experts, would have said each of those examples was impossible. Our </atom:summary><link>http://software-quality-testing.blogspot.com/2007/02/why-is-most-software-so-bad.html</link><author>noreply@blogger.com (Debasis Pradhan)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjS3gMIt3wOPsPOBmloqVaa-Q2O6jfJAzKPhq1J3GrnlfjH_l9UBT-1VVD_hyqnD6utCvGpQqQ1lzMP03MKsIP_Tm31s-p7_k6M93LFaOHAmviGNvg5EXRilLYipGIUg3AlWvWW/s72-c/article_1a.gif" height="72" width="72"/><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-37776098.post-129561991426061002</guid><pubDate>Sun, 28 Jan 2007 14:36:00 +0000</pubDate><atom:updated>2007-01-28T20:12:00.790+05:30</atom:updated><title>Software Quality and Testing</title><atom:summary type="text">From: New Earth OnlineTesting is one of the fundamentals of Quality Assurance, it outlines where the defects are in a measurable form and helps to make an application &quot;bug free&quot;. Remember though that software testing never reveals the absence of bugs, only the presence of them. The purpose of this guide is to help promote the ideals of software quality, and illustrate why it is a good thing.The </atom:summary><link>http://software-quality-testing.blogspot.com/2007/01/software-quality-and-testing.html</link><author>noreply@blogger.com (Debasis Pradhan)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiYys50UaQFs1F7LXgPfyjQAy0j5FrwizPiCBVrtZ4CGvWiA2gw9CSsrrAz4MHFvYA_U594Ioa9hsBjfLigSAkBUTgmMA86nn8tFUnviM7Zbk8PFcl80G6Kqlob6H9edYZqRyDh/s72-c/faq.png" height="72" width="72"/><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-37776098.post-6186331652268801327</guid><pubDate>Tue, 23 Jan 2007 11:46:00 +0000</pubDate><atom:updated>2007-01-23T17:22:21.472+05:30</atom:updated><title>Performance, Reliability and Security Testing</title><atom:summary type="text">Performance testing:Not all software systems have specifications on performance explicitly. But every system will have implicit performance requirements. The software should not take infinite time or infinite resource to execute. &quot;Performance bugs&quot; sometimes are used to refer to those design problems in software that cause the system performance to degrade. Performance has always been a great </atom:summary><link>http://software-quality-testing.blogspot.com/2007/01/performance-reliability-and-security.html</link><author>noreply@blogger.com (Debasis Pradhan)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-37776098.post-7122450746810473929</guid><pubDate>Wed, 17 Jan 2007 08:37:00 +0000</pubDate><atom:updated>2007-01-17T14:12:56.881+05:30</atom:updated><title>Software Bug Tracking : Who Is Responsible?</title><atom:summary type="text">From: SoftwareProjects.orgBug tracking. It&#39;s the Achilles&#39; heel of software development. It&#39;s easy to report bugs found in software, but unless the bugs are properly tracked, all the way through to their resolution, one can never be sure whether these nuances truly have been swatted. Like criminals on the run, without proper bug tracking procedures, those responsible for fixing bugs spend their </atom:summary><link>http://software-quality-testing.blogspot.com/2007/01/software-bug-tracking-who-is.html</link><author>noreply@blogger.com (Debasis Pradhan)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-37776098.post-116859043534625992</guid><pubDate>Fri, 12 Jan 2007 08:26:00 +0000</pubDate><atom:updated>2007-01-12T13:57:17.240+05:30</atom:updated><title>Software Bug in Google Suggest !</title><atom:summary type="text">I hope you all know about Google Suggest. It as a search interface of GOOGLE, where possible keywords are suggested to you as you keep entering your keyword. Cool feature, right? Google does it by the help of Ajax. It helps the user to narrow down his/her search item based on the suggestions. Check it at: http://www.google.com/webhp?complete=1&amp;amp;hl=en Today I was using it, when I noticed this &#39;</atom:summary><link>http://software-quality-testing.blogspot.com/2007/01/software-bug-in-google-suggest.html</link><author>noreply@blogger.com (Debasis Pradhan)</author><thr:total>4</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-37776098.post-116850607361908740</guid><pubDate>Thu, 11 Jan 2007 08:55:00 +0000</pubDate><atom:updated>2007-02-07T19:23:32.252+05:30</atom:updated><title>Software Errors: Prevention and Detection</title><atom:summary type="text">From: MactechMost programmers are rather cavalier about controlling the quality of the software they write. They bang out some code, run it through some fairly obvious ad hoc tests, and if it seems okay, they&#39;re done. While this approach may work all right for small, personal programs, it doesn&#39;t cut the mustard for professional software development. Modern software engineering practices include </atom:summary><link>http://software-quality-testing.blogspot.com/2007/01/software-errors-prevention-and.html</link><author>noreply@blogger.com (Debasis Pradhan)</author><thr:total>5</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-37776098.post-116808249318219573</guid><pubDate>Sat, 06 Jan 2007 11:19:00 +0000</pubDate><atom:updated>2007-01-06T21:06:05.623+05:30</atom:updated><title>Tested by &quot;Tester Tested&quot; !</title><atom:summary type="text">I am a regular reader of Pradeep Soundararajan&#39;s Blog. Today I was reading his older posts and I was surprised (or rather shocked) to see my own name in his post Indian testing community - start blogging! !!!I am quoting few lines from his blogpost. I hope Pradeep doesn&#39;t mind that :)....Why testers who tried aping Tester Tested unable to continue? ( could be one of the following...)1. They </atom:summary><link>http://software-quality-testing.blogspot.com/2007/01/tested-by-tester-tested.html</link><author>noreply@blogger.com (Debasis Pradhan)</author><thr:total>1</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-37776098.post-116790585957736212</guid><pubDate>Thu, 04 Jan 2007 09:48:00 +0000</pubDate><atom:updated>2007-01-04T16:46:33.683+05:30</atom:updated><title>Understanding Software Testing Project Life Cycle (STPLC)</title><atom:summary type="text">The need to understand STPLC:We know that testing is a phase of Software Development Life Cycle (SDLC). But, when testing is leased to a third-party vendor, it becomes a project in itself for that vendor. And, it is very natural that a testing project is treated like most of the other development /maintenance projects. Most of the companies would be following a certain customized set of standards</atom:summary><link>http://software-quality-testing.blogspot.com/2007/01/understanding-software-testing-project.html</link><author>noreply@blogger.com (Debasis Pradhan)</author><thr:total>1</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-37776098.post-116789986103510203</guid><pubDate>Thu, 04 Jan 2007 08:31:00 +0000</pubDate><atom:updated>2007-01-04T14:07:42.336+05:30</atom:updated><title>Role of Agile Testing in a Quality Software</title><atom:summary type="text">What is Agile Testing? How many times this question came up in your mind? I was also trying to get a clearer picture, when among others, Lisa Crispin attempted to define it: When I use the term &#39;agile testing&#39; I&#39;m talking about a set of good practices which has helped me and my teams deliver higher quality software, whether or not we were part of an agile team. We know that people, not tools or </atom:summary><link>http://software-quality-testing.blogspot.com/2007/01/role-of-agile-testing-in-quality.html</link><author>noreply@blogger.com (Debasis Pradhan)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-37776098.post-116773539492257353</guid><pubDate>Tue, 02 Jan 2007 10:56:00 +0000</pubDate><atom:updated>2007-01-02T16:26:35.113+05:30</atom:updated><title>Bug Priority Vs. Bug Severity !</title><atom:summary type="text">Differentiate Priority and Severity. The effect of a bug on the software does not automatically correlate with the priority for fixing it. A severe bug that crashes the software only once in a blue moon for 1% of the users is lower priority than a mishandled error condition resulting in the need to re-enter a portion of the input for every user every time. Therefore, track priority and severity </atom:summary><link>http://software-quality-testing.blogspot.com/2007/01/bug-priority-vs-bug-severity.html</link><author>noreply@blogger.com (Debasis Pradhan)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-37776098.post-116773484025872489</guid><pubDate>Tue, 02 Jan 2007 10:43:00 +0000</pubDate><atom:updated>2007-01-02T16:18:49.050+05:30</atom:updated><title>How to handle Late Requirements !</title><atom:summary type="text">Many of project issues are related to bad requirements management. One particular issue which is hard to tackle is the handling of late requirements.Coping with new requirements after the development has started often leads to problems in the project:1. schedule, cost and scope of the running project become unknown2. delays due to unsufficient impact investigation, which may propagate to other </atom:summary><link>http://software-quality-testing.blogspot.com/2007/01/how-to-handle-late-requirements.html</link><author>noreply@blogger.com (Debasis Pradhan)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-37776098.post-116773408759347134</guid><pubDate>Tue, 02 Jan 2007 10:09:00 +0000</pubDate><atom:updated>2007-01-02T16:12:36.076+05:30</atom:updated><title>Agile Testing - The BUZZ !</title><atom:summary type="text">Agile testing is the new buzz word in testing industy. Testing from beginning of the project and continually testing throughout the product lifecycle is basis of agile testing. If tester can work with client and help him specify the requirements in form of test cases then it makes tham completely unambiguous. So the test cases are ready even before coding starts so developers can start measuring </atom:summary><link>http://software-quality-testing.blogspot.com/2007/01/agile-testing-buzz.html</link><author>noreply@blogger.com (Debasis Pradhan)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-37776098.post-116773247731208760</guid><pubDate>Tue, 02 Jan 2007 10:06:00 +0000</pubDate><atom:updated>2007-01-02T15:37:59.243+05:30</atom:updated><title>Bottom-up and top-down approaches in Integration Testing.</title><atom:summary type="text">Bottom-up approach: In this approach testing is conducted from sub module to main module, if the main module is not developed a temporary program called DRIVERS is used to simulate the main module.Top-down approach: In this approach testing is conducted from main module to sub module. if the sub module is not developed a temporary program called STUB is used for simulate the submodule.</atom:summary><link>http://software-quality-testing.blogspot.com/2007/01/bottom-up-and-top-down-approaches-in.html</link><author>noreply@blogger.com (Debasis Pradhan)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-37776098.post-116773231863544920</guid><pubDate>Tue, 02 Jan 2007 09:58:00 +0000</pubDate><atom:updated>2007-01-02T15:35:21.026+05:30</atom:updated><title>Test Bed Vs. Test Data</title><atom:summary type="text">Test Bed is an execution environment configured for software testing. It consists of specific hardware, network topology, Operating System, configuration of the product to be under test, system software and other applications. The Test Plan for a project should be developed from the test beds to be used.Test Data is that run through a computer program to test the software. Test data can be used </atom:summary><link>http://software-quality-testing.blogspot.com/2007/01/test-bed-vs-test-data.html</link><author>noreply@blogger.com (Debasis Pradhan)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-37776098.post-116592187494269619</guid><pubDate>Tue, 12 Dec 2006 10:53:00 +0000</pubDate><atom:updated>2006-12-12T16:49:22.136+05:30</atom:updated><title>Software Test Automation - Facts (Realities) and Fictions (Myths) !!!</title><atom:summary type="text">Test automation is a gimmick, most QA/Test managers use, to divert attention from serious issues of a project. This is what I have realised about test automation in all these years. Believe me, I am saying this from my past experience. If you are also in software testing/QA field then you might have noticed this too. Whenever a projects fails to meet its deadline or it fails to meet the expected </atom:summary><link>http://software-quality-testing.blogspot.com/2006/12/software-test-automation-facts.html</link><author>noreply@blogger.com (Debasis Pradhan)</author><thr:total>1</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-37776098.post-116558529878504146</guid><pubDate>Fri, 08 Dec 2006 13:29:00 +0000</pubDate><atom:updated>2006-12-08T19:11:39.036+05:30</atom:updated><title>Bumper Stickers for Software Testers !</title><atom:summary type="text">From: StickyMindsTry these bumper stickers on your car. Warning! Use at your own risk and only if you are a Software Tester !1 Ask me about my latest bug.2 Honk if you love to crash software.3 My other car is a bug.4 Have you hugged your software tester today?5 Software Testers: Always looking for trouble.6 Software Testing is Like Fishing, But You Get Paid.7 Software Testers: &quot;Depraved minds...</atom:summary><link>http://software-quality-testing.blogspot.com/2006/12/bumper-stickers-for-software-testers.html</link><author>noreply@blogger.com (Debasis Pradhan)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-37776098.post-116548410889427119</guid><pubDate>Thu, 07 Dec 2006 09:32:00 +0000</pubDate><atom:updated>2006-12-07T15:05:23.730+05:30</atom:updated><title>Common Misconceptions about Software Testing</title><atom:summary type="text">From the Book: Global Software Test Automation: A Discussion of Software Testing for ExecutivesThere are many misconceptions about software testing. This article deals with the five most common misconceptions about how software testing differs from other testing.Five Common MisconceptionsSome of the most common misconceptions about software testing relate to how software testing differs from </atom:summary><link>http://software-quality-testing.blogspot.com/2006/12/common-misconceptions-about-software.html</link><author>noreply@blogger.com (Debasis Pradhan)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-37776098.post-116488690781861748</guid><pubDate>Thu, 30 Nov 2006 11:41:00 +0000</pubDate><atom:updated>2006-11-30T17:11:49.483+05:30</atom:updated><title>Software Quality Assurance Interview Questions (Part-10)</title><atom:summary type="text">From: SQA FYI Center 1. What is the difference between a test strategy and a test plan?2. What is the relationship between test scripts and test cases?3. What goes into a test package?4. What test data would you need to test that a specific date occurs on a specific day of week?5. How would you prioritize the test?6. It is the eleventh hour and we have no test scripts, cases, or data. What would </atom:summary><link>http://software-quality-testing.blogspot.com/2006/11/software-quality-assurance_116488690781861748.html</link><author>noreply@blogger.com (Debasis Pradhan)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-37776098.post-116488631776510146</guid><pubDate>Thu, 30 Nov 2006 11:31:00 +0000</pubDate><atom:updated>2006-11-30T17:02:00.610+05:30</atom:updated><title>Software Quality Assurance Interview Questions (Part-9)</title><atom:summary type="text">From: SQA FYI Center 1. When should testing start in a project? Why?2. How do you go about testing a web application?3. Difference between Black &amp; White box testing4. What is Configuration management? Tools used?5. What do you plan to become after say 2-5yrs (Ex: QA Manager, Why?)6. Would you like to work in a team or alone, why?7. Give me 5 strong &amp;amp; weak points of yours8. Why do you want to </atom:summary><link>http://software-quality-testing.blogspot.com/2006/11/software-quality-assurance_116488631776510146.html</link><author>noreply@blogger.com (Debasis Pradhan)</author><thr:total>2</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-37776098.post-116488592585252216</guid><pubDate>Thu, 30 Nov 2006 11:25:00 +0000</pubDate><atom:updated>2006-11-30T16:55:29.743+05:30</atom:updated><title>Software Quality Assurance Interview Questions (Part-8)</title><atom:summary type="text">From: SQA FYI Center 1. How do you determine what to test?2. How do you decide when you have tested enough?3. How do you test if you have minimal or no documentation about the product?4. Describe me to the basic elements you put in a defect report?5. How do you perform regression testing?6. At what stage of the life cycle does testing begin in your opinion?7. How do you analyze your test results?</atom:summary><link>http://software-quality-testing.blogspot.com/2006/11/software-quality-assurance_116488592585252216.html</link><author>noreply@blogger.com (Debasis Pradhan)</author><thr:total>1</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-37776098.post-116488563197156167</guid><pubDate>Thu, 30 Nov 2006 11:20:00 +0000</pubDate><atom:updated>2006-11-30T16:50:32.996+05:30</atom:updated><title>Software Quality Assurance Interview Questions (Part-7)</title><atom:summary type="text">From: SQA FYI Center 1. Are regression tests required or do you feel there is a better use for resources?2. Our software designers use UML for modeling applications. Based on their use cases, we would like to plan a test strategy. Do you agree with this approach or would this mean more effort for the testers.3. Tell me about a difficult time you had at work and how you worked through it.4. Give </atom:summary><link>http://software-quality-testing.blogspot.com/2006/11/software-quality-assurance_116488563197156167.html</link><author>noreply@blogger.com (Debasis Pradhan)</author><thr:total>0</thr:total></item></channel></rss>