tag:blogger.com,1999:blog-89612506840183744992024-03-05T01:02:42.494-08:00software testing and QA,software Quality assurance,softwaretesting jokes,quotes,software testing and quality analysis,quality assurance,bug tracking,debugging,Qa,MYsql,database testing,product testing ,testing and Qa,software testing quotes,cartoons,jokes about software testing.software quality assurance,software testing certifications,istqb,cste,iseb.indian testing board,accenture software testing challenge,appium,UTest,99 Tests,earn money by testing,Unknownnoreply@blogger.comBlogger19125tag:blogger.com,1999:blog-8961250684018374499.post-8924742977844297872022-04-15T03:29:00.002-07:002022-04-15T03:29:42.132-07:00Best Software testing websites and training videos In Online
I already shared about the website https://www.softwaretestinghelp.com/ . One of the site i learned so many things from experts.
Another one great content i found and wish to share with Everyone Pavan sir Videos. He provides all the latest courses for free with crystal clear
explanation about each topic.
From BDD Cucumber testing to Manual testing. All are very worthy videos to watch.
definately it will be useful for anyone who is looking to enter to software testing from entry level.
Also who provides online training for people who are looking for guidance in the field of Software testing.
Please subscribe to his channel using this <a href="https://www.youtube.com/channel/UC46vj6mN-6kZm5RYWWqebsg" target="_blank" rel="nofollow">link</a> https://www.youtube.com/channel/UC46vj6mN-6kZm5RYWWqebsg
As a tribute to my Online guru i submitting this blog post to Pavan sir.
<div class="separator" style="clear: both;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjfRDrzxuQsLRbsX0L2-CNAt_kRcDZ68XVhvOtS3tRtwHtwlO1XIRgwcbgJ9yZho-0CcbUAbsGsuNS4nU1PS8FC6_WsLbQGdfT-2pa1BDWyS_LJR8UsoV5h9fGDhrBhDQ7rZqGWpk_DOeJx0e9zGz5612u9yXMJIrORZ5_kcFXIIOcaYR1IZcjvyuzdXQ/s1102/pavan%20sir.JPG" style="display: block; padding: 1em 0; text-align: center; "><img alt="" border="0" width="320" data-original-height="184" data-original-width="1102" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjfRDrzxuQsLRbsX0L2-CNAt_kRcDZ68XVhvOtS3tRtwHtwlO1XIRgwcbgJ9yZho-0CcbUAbsGsuNS4nU1PS8FC6_WsLbQGdfT-2pa1BDWyS_LJR8UsoV5h9fGDhrBhDQ7rZqGWpk_DOeJx0e9zGz5612u9yXMJIrORZ5_kcFXIIOcaYR1IZcjvyuzdXQ/s320/pavan%20sir.JPG"/></a></div>
Thank you for your Great work.
Unknownnoreply@blogger.com2tag:blogger.com,1999:blog-8961250684018374499.post-58069296036494928362018-02-08T08:20:00.000-08:002018-02-12T07:36:42.014-08:00Appium Configuration with Visual studio for selenium C# developmentPrerequisites:
1. Visual Studio Ultimate (2010 or above) (Because MSTest is present in that)
2. Android SDK For Windows (Download Link) (Website link)
3. Appium For Windows (Website Link) (Download Link)
4. A Real Android Device running Android 4.2 or Above
5. A USB Cable to attach your Android Phone to Your PC.
6. ADB Interface Drivers for your device (Link on how to get that ) (very important Step)
Some Configurations for Android SDK and Appium:
• When you have installed Android SDK, go to My Computer, right click, click Properties, click Advanced System Settings, and click Environment Variables.
• Create a new User Variable with the name “ANDROID_HOME”. Give path to your sdk folder in the value. The default path is C:\Program Files (x86)\Android\android-sdk
• Edit the PATH variable in “System Variable” Section. Append the path to your tools folder and platform-tools folder. Separated with “;”
The paths are
C:\Program Files (x86)\Android\android-sdk\tools
C:\Program Files (x86)\Android\android-sdk\platform-tools
See the image below.
• Connect your Android Device with USB Cable. To make sure your android Device is connected with your PC, we have to do following.
Go to C:\Program Files (x86)\Android\android-sdk\tools. Click on “uiautomatorviewer.bat”. A window will open. See Image.
You can use this window to inspect the elements of your app in android. Open the appropriate app in your android device and click on “Device Screenshot” button on this screen. If you receive this error message “No Android devices were found by adb”
That means adb interface drivers are not installed on your system. You have to read again point number 6 in the Prerequisites section. If android device is successfully connected, you should see a snapshot along with Object Map in this window like this.
•Unzip AppiumforWindows.zip in a folder. Open Appium.exe, you should see a window like this.
Click on the android Icon on the top left of this window. You will see a window in which you can configure the platform and version of your android on which you want to test. I have filled the following configurations there.
Now click on the Play button on the top right corner of the window. Appium server will start with the configurations you have provided.
•Developer options should be enabled on your android device, with these two options.
Usb Debugging should be enabled.
Stay Awake should be enabled.
Now it is time to code.
Open Visual Studio Ultimate (2010 or above)
Create a UnitTest project.
Install “Appium Web Driver” and “Selenium WebDriver” using NuGet package manager. (The easiest way)
If you don’t want to use NuGet package manager, you can manually download Appium dot net driver and selenium web driver c# libraries and add them to your solution
Your reference section should look like this.
For every application you want to test, you must know its package name and app activity name. So to know about these attributes, you need to download a little android app on your phone. It is called apkInfo. It will show you the package name and activity name of any android app installed on your phone. Just pass these parameters here and that app will launch on your phone by automation code.
Conclusion.
If you are familiar with Selenium WebDriver, coding in Appium is not so different. Only problem was the configuration. If you have done this right, you should be able start writing scripts for your android. I tried to explain this as simply as possible.
Unknownnoreply@blogger.com51tag:blogger.com,1999:blog-8961250684018374499.post-45294977007741921312018-02-08T08:19:00.002-08:002018-02-08T08:34:32.244-08:00How to earn money using your Software Testing expertise<b>How to earn money using your Software Testing expertise ?</b><br />
<br />
<b> 1. Start your Own blog ?</b><br />
<br />
Start your own blog in Blogspot or with your own Domain and write your own content share knowledge with fellow testing community.<br />
<br />
Content for your blogs may create interest in fellow testers.<br />
<br />
write a review about the software testing tools you are using currently .<br />
<br />
Or evavualate a Open source Testing Tool and give your feed back about pros and cons.<br />
<br />
Start writing content for Software Testing Blogs who will pay for Article also a good choice of Revenue. <a href="http://www.softwaretestinghelp.com/">Softwaretestinghelp.com paying for articles who share with them</a><br />
<br />
<b>2. Become a member in <a href="https://www.utest.com/">UTest</a> or <a href="https://99tests.com/">99 Tests</a></b><br />
<br />
Now a days with the increase of Gadgets , Mobiles, Smart TV and (IOT) Internet of things , The scope of testing is changed .<br />
Companies developing Apps or specified programs for General public are relied on Crowd source companies like UTest,99 Tests etc.<br />
Create your own profile with all your Electronic inventory like mobiles,Tabs, Smart tv, Smart Appliance and complete the Sand box or a Free project which will evaluate your skills on QA knowledge.<br />
<br />
Based on your Ratings you will be invited for Paid projects.<br />
<br />
Utest and 99 Test are most active Crowd source Platform for QA and Testing Community.<br />
<br />
some times you can upto $ 1** for referrals on specific projects.
for more info Visit <a href="https://www.utest.com/">UTEST</a> forum and Blogs .<br />
<br />
Forums like UTEST or 99 Tests giving oppurtunity for novoice testers.<br />
<br />
Freshers who are looking for Job in Software testing field these forums are training ground, they can horn their software testing skills and learn testing new technologies.<br />
<br />
I will keep updating this post whenever i get encounter with something new in Software testing field.<br />
<br />
Thanks for reading this article,<br />
<br />
Please provide your feedback in comments column.Unknownnoreply@blogger.com23tag:blogger.com,1999:blog-8961250684018374499.post-68459156961168820642009-01-31T07:08:00.000-08:002009-01-31T07:24:26.069-08:00Internet is harmful for you: Google thinks soClick the image to see it in full size:<br /><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgCfX0odSokW9nPrY3HiNfr8DNdtU8MFHOPqWiJQfZYLOkRmORQ_I1XvRySsH6FZiDW2SLfO7qFSzSDLkGxUlITLTojF7GHNc87WnmPmJASKyKpttmg9UkRPcYJeAZKDat1y27GBNDycCwM/s1600-h/news+-+Google+Search_1233414295812.png"><img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;width: 250px; height: 400px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgCfX0odSokW9nPrY3HiNfr8DNdtU8MFHOPqWiJQfZYLOkRmORQ_I1XvRySsH6FZiDW2SLfO7qFSzSDLkGxUlITLTojF7GHNc87WnmPmJASKyKpttmg9UkRPcYJeAZKDat1y27GBNDycCwM/s400/news+-+Google+Search_1233414295812.png" border="0" alt=""id="BLOGGER_PHOTO_ID_5297478355013395730" /></a><br /><br />Today, for a few minutes Google suddenly started warning all of its indexed sites as Harmful to your computer! Perhaps it was a glitch in their algorithm, but we managed to make a snap of it for the record.Unknownnoreply@blogger.com189tag:blogger.com,1999:blog-8961250684018374499.post-33639686217402726732008-11-17T03:16:00.000-08:002008-11-17T03:27:06.149-08:00BugBug<br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjKiA4kfx4_WDK1cCjm38j-vqKwSvehDLQrKYG0MxjLmkukrFfJgc0RiiyqDTSTZKVq8sD_Kgc5B3ly7pujGLJzh2Ez1h70KCHb73tek1KRHHfYELsjr2zFsIazz7-glcy_JVIxTGynR45y/s1600-h/bug(2).png"><img style="float:left; margin:0 10px 10px 0;cursor:pointer; cursor:hand;width: 400px; height: 187px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjKiA4kfx4_WDK1cCjm38j-vqKwSvehDLQrKYG0MxjLmkukrFfJgc0RiiyqDTSTZKVq8sD_Kgc5B3ly7pujGLJzh2Ez1h70KCHb73tek1KRHHfYELsjr2zFsIazz7-glcy_JVIxTGynR45y/s400/bug(2).png" border="0" alt=""id="BLOGGER_PHOTO_ID_5269585592343560882" /></a> click to enlarge the image<br /><br />Today i received a mail containing this above image , from one of my Friend Who is working for IBM. i tried to find the Origin of this cartoon but can't make it, so i thought of promoting for the creativity of the cartoonist. Hope you People Like it.Unknownnoreply@blogger.com31tag:blogger.com,1999:blog-8961250684018374499.post-75117650133464705522008-07-15T21:06:00.000-07:002008-07-15T21:12:50.421-07:00Designing Test Cases<span style="font-weight: bold;">Designing Test Cases</span><br /><p class="text">A <a id="KonaLink2" target="_top" class="kLink" style="text-decoration: underline ! important; position: static;" href="http://onestoptesting.com/test-cases/designing.asp#"><span style="color: blue ! important; font-family: Verdana; font-weight: 400; font-size: 13px; position: static;color:blue;" ><span class="kLink" style="border-bottom: 1px solid blue; color: blue ! important; font-family: Verdana; font-weight: 400; font-size: 13px; position: static; padding-bottom: 1px; background-color: transparent;"></span></span></a>test case is a detailed procedure that fully tests a feature or an aspect of a feature. Whereas the test plan <a id="KonaLink3" target="_top" class="kLink" style="text-decoration: underline ! important; position: static;" href="http://onestoptesting.com/test-cases/designing.asp#"><span style="color: blue ! important; font-family: Verdana; font-weight: 400; font-size: 13px; position: static;color:blue;" ><span class="kLink" style="color: blue ! important; font-family: Verdana; font-weight: 400; font-size: 13px; position: static;"></span></span></a> describes what to test, a test case describes how to perform a particular test. You need to develop a test case for each test listed in the test plan. </p><span style="font-weight: bold;">A test case includes:</span> <ul class="text" type="disc"><li>The purpose of the test.</li><br /><li>Special hardware requirements, such as a modem.</li><br /><li>Special software requirements, such as a tool.</li><br /><li>Specific setup or configuration requirements.</li><br /><li>A description of how to perform the test.</li><br /><li>The expected results or success criteria for the test.</li></ul><br />Test cases should be written by a team member who understands the function or <a id="KonaLink4" target="_top" class="kLink" style="text-decoration: underline ! important; position: static;" href="http://onestoptesting.com/test-cases/designing.asp#"><span style="color: blue ! important; font-family: Verdana; font-weight: 400; font-size: 13px; position: static;color:blue;" ><span class="kLink" style="border-bottom: 1px solid blue; color: blue ! important; font-family: Verdana; font-weight: 400; font-size: 13px; position: static; padding-bottom: 1px; background-color: transparent;"></span></span></a>technology being tested, and each test case should be submitted for peer review.<br /><br />Organizations take a variety of approaches to documenting test cases; these range from developing detailed, recipe-like steps to writing general descriptions. In detailed test cases, the steps describe exactly how to perform the test. In descriptive test cases, the tester decides at the time of the test how to perform the test and what data to use.<br /><br />Most organizations prefer detailed test cases because determining pass or fail criteria is usually easier with this type of case. In addition, detailed test cases are reproducible and are easier to automate than descriptive test cases. This is particularly important if you plan to compare the results of tests over time, such as when you are optimizing configurations. Detailed test cases are more time-consuming to develop and maintain. On the other hand, test cases that are open to interpretation are not repeatable and can require debugging, consuming time that would be better spent on testing.<br /><br /><b>Test Case Design</b><br /><br /><b>Test Case ID</b>:<br />It is unique number given to test case in order to be identified.<br /><br /> <b>Test description</b>:<br />The description if test case you are going to test.<br /><br /> <b>Revision history</b>:<br />Each test case has to have its revision history in order to know when and by whom it is created or modified.<br /><br /> <b>Function to be tested</b>:<br />The name of function to be tested.<br /><br /> <b>Environment</b>:<br />It tells in which environment you are testing.<br /><br /> <b>Test Setup</b>:<br />Anything you need to set up outside of your <a id="KonaLink5" target="_top" class="kLink" style="text-decoration: underline ! important; position: static;" href="http://onestoptesting.com/test-cases/designing.asp#"><span style="color: blue ! important; font-family: Verdana; font-weight: 400; font-size: 13px; position: static;color:blue;" ><span class="kLink" style="color: blue ! important; font-family: Verdana; font-weight: 400; font-size: 13px; position: static;"></span></span></a>application for example printers, network and so on.<br /><br /> <b>Test Execution</b>:<br />It is detailed description of every step of execution.<br /><br /> <b>Expected Results</b>:<br />The description of what you expect the function to do.<br /><br /> <b>Actual Results</b>:<br />pass / failed<br /><br />If pass - What actually happen when you run the test.<br /><br />If failed - put in description of what you've observed.Unknownnoreply@blogger.com18tag:blogger.com,1999:blog-8961250684018374499.post-30104669905599539772008-07-14T22:44:00.000-07:002008-07-14T22:52:44.951-07:00Regression testing Introduction<p class="text"><b>Regression testing</b> is any type of software testing which seeks to uncover regression bugs. Regression bugs occur whenever software functionality that previously worked as desired, stops working or no longer works in the same way that was previously planned. Typically regression bugs occur as an unintended consequence of program changes.</p> <p class="text"><i>Common methods</i> of regression testing include re-running previously run tests and checking whether previously fixed faults have re-emerged.</p><br /><h1>Types of Regression</h1>Local - changes introduce new bugs.<ul class="text"><li>Unmasked - changes unmask previously existing bugs.</li><li>Remote - Changing one part breaks another part of the program. For example, Module A writes to a <span style="font-size:78%;"><span class="kLink" style="text-decoration: underline ! important; position: static;"></span></span>database. Module B reads from the database. If changes to what Module A writes to the database break Module B, it is remote regression.</li></ul> <p class="text">There's another way to classify regression.</p> <ul class="text"><li>New feature regression - changes to code that is new to release 1.1 break other code that is new to release 1.1.</li></ul> <ul class="text"><li>Existing feature regression - changes to code that is new to release 1.1 break code that existed in release 1.0.</li></ul> <br /><center><h1>Uses of Regression Testing</h1></center>Regression testing can be used not only for testing the <i>correctness</i> of a program, but it is also often used to track the quality of its output. For instance in the design of a compiler, regression testing should track the code size, simulation time and compilation time of the test suite cases.<br /><p class="text"><b>Recommended Resources</b><br />• <a href="http://www.coolinterview.com/type.asp?iType=197" target="_blank" title="Testing Interview Questions">Testing Interview Questions </a>- <a href="http://www.coolinterview.com/type.asp?iType=197" target="_blank" title="http://www.coolinterview.com/type.asp">http://www.coolinterview.com/type.asp</a><br />• <a href="http://www.coolinterview.com/type.asp?iType=198" target="_blank" title="Testing Tools Interview Questions">Testing Tools Interview Questions </a>- <a href="http://www.coolinterview.com/type.asp?iType=198" target="_blank" title="http://www.coolinterview.com/type.asp">http://www.coolinterview.com/type.asp</a><br />• <a href="http://en.wikipedia.org/wiki/Software_testing" target="_blank" title="What is Software Testing?">What is Software Testing?</a>- <a href="http://en.wikipedia.org/wiki/Software_testing" target="_blank" title="http://en.wikipedia.org/wiki/Software_testing">http://en.wikipedia.org/wiki/Software_testing</a><br />• <a href="http://www.softwareqatest.com/" target="_blank" title="Software QA & Testing Resource Center">Software QA & Testing Resource Center</a>- <a href="http://www.softwareqatest.com/" target="_blank" title="http://www.softwareqatest.com/">http://www.softwareqatest.com/</a><br />• <a href="http://www.testingfaqs.org/" target="_blank" title="Testing Faqs">Testing Faqs</a>- <a href="http://www.testingfaqs.org/" target="_blank" title="http://www.testingfaqs.org">http://www.testingfaqs.org/</a></p><p class="text"><br /></p>Unknownnoreply@blogger.com24tag:blogger.com,1999:blog-8961250684018374499.post-44795133104841352312008-03-21T21:52:00.000-07:002008-03-21T21:58:02.241-07:00Tips to Reach Six Sigma<a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj2xU1ttmd1JqERsjlSIllts6yFK2VH-q9jngBKuI-_VfpiXv_oDp_TqoR-hU6DrQHwJwEpHU2Q329gCHN3z0q0H6uCGapJ8f_w826wX0NOG1i1E4EjzTDWCbn9frUkCcmR3-H9GEZh3CuT/s1600-h/image005.jpg"><img style="margin: 0pt 10px 10px 0pt; float: left; cursor: pointer;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj2xU1ttmd1JqERsjlSIllts6yFK2VH-q9jngBKuI-_VfpiXv_oDp_TqoR-hU6DrQHwJwEpHU2Q329gCHN3z0q0H6uCGapJ8f_w826wX0NOG1i1E4EjzTDWCbn9frUkCcmR3-H9GEZh3CuT/s400/image005.jpg" alt="" id="BLOGGER_PHOTO_ID_5180425499272123906" border="0" /></a><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhedbnavKg_EnnFeL6G3n34yKm35qFz__TAepwLg49EBimGajRfrXM9T_sP0I33GjejorTCf5tTSgsQ8gnVJACxl6hG67lFp7xbG8FG33IxZemcuUYaDy0X7nbMQkQyWhWPB7xgiJxiIMBC/s1600-h/image004.jpg"><img style="margin: 0pt 10px 10px 0pt; float: left; cursor: pointer;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhedbnavKg_EnnFeL6G3n34yKm35qFz__TAepwLg49EBimGajRfrXM9T_sP0I33GjejorTCf5tTSgsQ8gnVJACxl6hG67lFp7xbG8FG33IxZemcuUYaDy0X7nbMQkQyWhWPB7xgiJxiIMBC/s400/image004.jpg" alt="" id="BLOGGER_PHOTO_ID_5180425503567091218" border="0" /></a><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgP4qL0FxgT-yCuTMnacN8z4ZtAwu4aLowAxa840cTx8RdXX0vsTeG15y2FR5er0z6brS5pDTrEWCCVyzEhWJ_4C8kkDVVTCkpyRsrBVh_PJYWD1ofTccYKslQ713_92Zzk7wksOsG-xPws/s1600-h/image003.jpg"><img style="margin: 0pt 10px 10px 0pt; float: left; cursor: pointer;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgP4qL0FxgT-yCuTMnacN8z4ZtAwu4aLowAxa840cTx8RdXX0vsTeG15y2FR5er0z6brS5pDTrEWCCVyzEhWJ_4C8kkDVVTCkpyRsrBVh_PJYWD1ofTccYKslQ713_92Zzk7wksOsG-xPws/s400/image003.jpg" alt="" id="BLOGGER_PHOTO_ID_5180425503567091234" border="0" /></a><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhSp1oC9hKf2ceV8lRiPDVd0pFAJFrL9Y871fKg_8dWo5WlWzOKa539Luvt_XcjevzozQ_Gx1YYKwD7T2u8BspmFnwsd36eC8YqV2tmeNsbdnv0QBwS8A2sP0oZVv2EmBZllTFd3dYiOOl6/s1600-h/image002.jpg"><img style="margin: 0pt 10px 10px 0pt; float: left; cursor: pointer;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhSp1oC9hKf2ceV8lRiPDVd0pFAJFrL9Y871fKg_8dWo5WlWzOKa539Luvt_XcjevzozQ_Gx1YYKwD7T2u8BspmFnwsd36eC8YqV2tmeNsbdnv0QBwS8A2sP0oZVv2EmBZllTFd3dYiOOl6/s400/image002.jpg" alt="" id="BLOGGER_PHOTO_ID_5180425507862058546" border="0" /></a><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhgK2QQ4VnttGD0f-IF7nZ94olT-79F_-fXFcwLo21PtP0p74PmSPNwn-ogv7pz7zX6E4YwClJ4scZjr5wRve1IHaQeOOXpq9amijKR0IKTwSss8NDJHhsHd78NGIXn2mjPHHnlbrtBLFzy/s1600-h/image010.jpg"><img style="margin: 0pt 10px 10px 0pt; float: left; cursor: pointer;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhgK2QQ4VnttGD0f-IF7nZ94olT-79F_-fXFcwLo21PtP0p74PmSPNwn-ogv7pz7zX6E4YwClJ4scZjr5wRve1IHaQeOOXpq9amijKR0IKTwSss8NDJHhsHd78NGIXn2mjPHHnlbrtBLFzy/s400/image010.jpg" alt="" id="BLOGGER_PHOTO_ID_5180425099840165298" border="0" /></a><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhh2DJSn9d6ihKHsQnyCmfb7y0a6s_ZymcOmuDwW1D_8R1bakvAAEHTtksKCi0yuOEdChlXcfVD_3Cpq5Jrx_2nQP0cZ68BOBw9TwahydkVZZyL50n16CtK8K3tKWWAremz126O9cz1DUw7/s1600-h/image009.jpg"><img style="margin: 0pt 10px 10px 0pt; float: left; cursor: pointer;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhh2DJSn9d6ihKHsQnyCmfb7y0a6s_ZymcOmuDwW1D_8R1bakvAAEHTtksKCi0yuOEdChlXcfVD_3Cpq5Jrx_2nQP0cZ68BOBw9TwahydkVZZyL50n16CtK8K3tKWWAremz126O9cz1DUw7/s400/image009.jpg" alt="" id="BLOGGER_PHOTO_ID_5180425104135132610" border="0" /></a><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjq6q6kEBlSIaxcZEImkNhUkkAPdCAgYJjNCvuGeo99WI2GsIAocylNromNRunPtpnXkhL7p0Rx7hWD8AV5O4aiiDjjWfuhxOezIHSeNNQHL395y9HO4RSnhNPMo8LMjGocb2k0vcA7UGek/s1600-h/image008.jpg"><img style="margin: 0pt 10px 10px 0pt; float: left; cursor: pointer;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjq6q6kEBlSIaxcZEImkNhUkkAPdCAgYJjNCvuGeo99WI2GsIAocylNromNRunPtpnXkhL7p0Rx7hWD8AV5O4aiiDjjWfuhxOezIHSeNNQHL395y9HO4RSnhNPMo8LMjGocb2k0vcA7UGek/s400/image008.jpg" alt="" id="BLOGGER_PHOTO_ID_5180425108430099922" border="0" /></a><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgwdVDMIOwzVvbpa6yi0lVIp3P7rRTqk_IZDDb4x1f_ykT20W0f_01eJuh04HQRiLRyTS37v6wIN_KTI3kvF28FEnfKYvpx3mWHa_i0PgU60KKFqFAh4refVORBbqM8LQPl3QsVbKzZ846W/s1600-h/image007.jpg"><img style="margin: 0pt 10px 10px 0pt; float: left; cursor: pointer;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgwdVDMIOwzVvbpa6yi0lVIp3P7rRTqk_IZDDb4x1f_ykT20W0f_01eJuh04HQRiLRyTS37v6wIN_KTI3kvF28FEnfKYvpx3mWHa_i0PgU60KKFqFAh4refVORBbqM8LQPl3QsVbKzZ846W/s400/image007.jpg" alt="" id="BLOGGER_PHOTO_ID_5180425112725067234" border="0" /></a><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhNqtSj8lNfU_fyfnQWxzYn9V3kqAGW39BdStWI6fvdeXzeoPlk-NIsEiieZyaF1PTEnIER0Kg9KIHvrLi-1s8mGwutDiT13WjPl8raJPK8Y0DxLp_PaVImFPBgv5dAYWIm8gvk2CmWgWYF/s1600-h/image006.jpg"><img style="margin: 0pt 10px 10px 0pt; float: left; cursor: pointer;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhNqtSj8lNfU_fyfnQWxzYn9V3kqAGW39BdStWI6fvdeXzeoPlk-NIsEiieZyaF1PTEnIER0Kg9KIHvrLi-1s8mGwutDiT13WjPl8raJPK8Y0DxLp_PaVImFPBgv5dAYWIm8gvk2CmWgWYF/s400/image006.jpg" alt="" id="BLOGGER_PHOTO_ID_5180425112725067250" border="0" /></a><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj2xU1ttmd1JqERsjlSIllts6yFK2VH-q9jngBKuI-_VfpiXv_oDp_TqoR-hU6DrQHwJwEpHU2Q329gCHN3z0q0H6uCGapJ8f_w826wX0NOG1i1E4EjzTDWCbn9frUkCcmR3-H9GEZh3CuT/s1600-h/image005.jpg"><img style="margin: 0pt 10px 10px 0pt; float: left; cursor: pointer;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj2xU1ttmd1JqERsjlSIllts6yFK2VH-q9jngBKuI-_VfpiXv_oDp_TqoR-hU6DrQHwJwEpHU2Q329gCHN3z0q0H6uCGapJ8f_w826wX0NOG1i1E4EjzTDWCbn9frUkCcmR3-H9GEZh3CuT/s400/image005.jpg" alt="" id="BLOGGER_PHOTO_ID_5180425499272123906" border="0" /></a>Unknownnoreply@blogger.com16tag:blogger.com,1999:blog-8961250684018374499.post-34218876580397562532007-12-28T00:53:00.001-08:002008-01-11T23:22:32.190-08:00v model to w model<p><span style="font-size:130%;"><span style="font-weight: bold;">V-Model:<br /></span></span><br />The V-model promotes the idea that the dynamic test stages (on the right hand side of the model) use the documentation identified on the left hand side as baselines for testing. The V-Model further promotes the notion of early test preparation.<br /><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgiTw5pULMQEEIrn_A_VUgtjV8i6SqCi2P6X0KssEX4eMU6hYNz6HNm7v9QnG-kouj1pJ1ZyElrGTeHHHqftPQSLooMfvI-Wllh1W3FRZccfButvgUkscqtwQn6A428OkkKhwds8j4j27A/s1600-h/1-V-model.bmp"><img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgiTw5pULMQEEIrn_A_VUgtjV8i6SqCi2P6X0KssEX4eMU6hYNz6HNm7v9QnG-kouj1pJ1ZyElrGTeHHHqftPQSLooMfvI-Wllh1W3FRZccfButvgUkscqtwQn6A428OkkKhwds8j4j27A/s400/1-V-model.bmp" alt="" id="BLOGGER_PHOTO_ID_5122552005427912194" border="0" /></a></p> <div style="text-align: center;"><span style="font-weight: bold;">The V-Model of testing</span><br /></div><br />Early test preparation finds faults in baselines and is an effective way of detecting faults early. This approach is fine in principle and the early test preparation approach is always effective. However, there are two problems with the V-Model as normally presented.<br /><br /><div style="text-align: center;"><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgZOPUPRFknoWLVF82oXgFT94Yb_Cqx20oYIys8VTHAHno8HtRmIeub0Kc0GQPmeIxur6Ojj-tLOi4UPTmlV32uLUFtJinBPrlwbHh1aHn0iKCN6lGAW61BXHowUCgwH6-mqn-ucFWFalA/s1600-h/2-V-model.bmp"><img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgZOPUPRFknoWLVF82oXgFT94Yb_Cqx20oYIys8VTHAHno8HtRmIeub0Kc0GQPmeIxur6Ojj-tLOi4UPTmlV32uLUFtJinBPrlwbHh1aHn0iKCN6lGAW61BXHowUCgwH6-mqn-ucFWFalA/s400/2-V-model.bmp" alt="" id="BLOGGER_PHOTO_ID_5122552297485688338" border="0" /></a><br /><span style="font-weight: bold;">The V-Model with early test preparation</span><br /></div><br />There is rarely a perfect, one-to-one relationship between the documents on the left hand side and the test activities on the right. For example, functional specifications don’t usually provide enough information for a system test. System tests must often take account of some aspects of the business requirements as well as physical design issues for example. System testing usually draws on several sources of requirements information to be thoroughly planned.<br /><br />V-Model has little to say about static testing at all. The V-Model treats testing as a back-door activity on the right hand side of the model. There is no mention of the potentially greater value and effectiveness of static tests such as reviews, inspections, static code analysis and so on. This is a major omission and the V-Model does not support the broader view of testing as a constantly prominent activity throughout the development lifecycle.<br /><br /><span style="font-weight: bold;font-size:130%;" >W Model:</span><br /><br /><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgvtu5FYNXnYWHLlBbco_1bx6ZFsXBmWnKQrFptOVWR9zGLjI0pK-z7RtF3jPnF5dpTWa_fzCuMmGjQ_dEyuWPkH6BcMl5oVnW4WHW94HGNXCdvHUug0EwSEk3qCl_mHCh2Osr2jqr2MZQ/s1600-h/3-W-model.bmp"><img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgvtu5FYNXnYWHLlBbco_1bx6ZFsXBmWnKQrFptOVWR9zGLjI0pK-z7RtF3jPnF5dpTWa_fzCuMmGjQ_dEyuWPkH6BcMl5oVnW4WHW94HGNXCdvHUug0EwSEk3qCl_mHCh2Osr2jqr2MZQ/s400/3-W-model.bmp" alt="" id="BLOGGER_PHOTO_ID_5122552718392483362" border="0" /></a> <div style="text-align: center;"><span style="font-weight: bold;">The W-Model of testing</span><br /></div><br />Paul Herzlich introduced the W-Model approach in 1993. The W-Model attempts to address shortcomings in the V-Model. Rather than focus on specific dynamic test stages, as the V-Model does, the W-Model focuses on the development products themselves. Essentially, every development activity that produces a work product is shadowed by a test activity. The purpose of the test activity specifically is to determine whether the objectives of a development activity have been met and the deliverable meets its requirements. In its most generic form, the W-Model presents a standard development lifecycle with every development stage mirrored by a test activity. On the left hand side, typically, the deliverables of a development activity (for example, write requirements) is accompanied by a test activity test the requirements and so on. If your organization has a different set of development stages, then the W-Model is easily adjusted to your situation. The important thing is this: the W-Model of testing focuses specifically on the product risks of concern at the point where testing can be most effective.<br /><br /><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi1HoCsZvf6P-6KxgQ9-EHgFTokMoaKW_wplAF9FLPBjvhutatli8MRinBdfB0UrqvDwn2TNF3ULLQBJrtviGElWxPtZhmNy9wA5FTMzxQ3Xi__orHx91yv578OstIdUpi3mOM7pF-tTNo/s1600-h/4-W-model.bmp"><img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi1HoCsZvf6P-6KxgQ9-EHgFTokMoaKW_wplAF9FLPBjvhutatli8MRinBdfB0UrqvDwn2TNF3ULLQBJrtviGElWxPtZhmNy9wA5FTMzxQ3Xi__orHx91yv578OstIdUpi3mOM7pF-tTNo/s400/4-W-model.bmp" alt="" id="BLOGGER_PHOTO_ID_5122553040515030578" border="0" /></a> <div style="text-align: center;"><span style="font-weight: bold;">The W-Model and static test techniques.</span><br /></div><br />If we focus on the static test techniques, you can see that there is a wide range of techniques available for evaluating the products of the left hand side. Inspections, reviews, walkthroughs, static analysis, requirements animation as well as early test case preparation can all be used.<br /><br /><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEioKm2D_cvSrUFipkJR-M_wu7yuJiPG52MAavJcpUcTHKY2y6sFzLImIKxNDTvJ-ApXJ6V1IZhvMJm82rWq55ZPXSSw2CyJpbrxiz35eceBygSwbq1jMl2QmGC4nXEVEUroAQglPxhyphenhyphen7SM/s1600-h/5-W-model.bmp"><img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEioKm2D_cvSrUFipkJR-M_wu7yuJiPG52MAavJcpUcTHKY2y6sFzLImIKxNDTvJ-ApXJ6V1IZhvMJm82rWq55ZPXSSw2CyJpbrxiz35eceBygSwbq1jMl2QmGC4nXEVEUroAQglPxhyphenhyphen7SM/s400/5-W-model.bmp" alt="" id="BLOGGER_PHOTO_ID_5122553474306727490" border="0" /></a><br /><div style="text-align: center;"><span style="font-weight: bold;">The W-Model and dynamic test techniques.</span><br /></div><br />If we consider the dynamic test techniques you can see that there is also a wide range of techniques available for evaluating executable software and systems. The traditional unit, integration, system and acceptance tests can make use of the functional test design and measurement techniques as well as the non-functional test techniques that are all available for use to address specific test objectives.<br /><br />The W-Model removes the rather artificial constraint of having the same number of dynamic test stages as development stages. If there are five development stages concerned with the definition, design and construction of code in your project, it might be sensible to have only three stages of dynamic testing only. Component, system and acceptance testing might fit your normal way of working. The test objectives for the whole project would be distributed across three stages, not five. There may be practical reasons for doing this and the decision is based on an evaluation of product risks and how best to address them. The W-Model does not enforce a project symmetry that does not (or cannot) exist in reality. The W-model does not impose any rule that later dynamic tests must be based on documents created in specific stages (although earlier documentation products are nearly always used as baselines for dynamic testing. In projects using these methods, requirements and designs might be documented in multiple models so system testing might be based on several of these models (spread over several documents).<br /><br />We use the W-Model in test strategy as follows. Having identified the specific risks of concern, we specify the products that need to be tested; we then select test techniques (static reviews or dynamic test stages) to be used on those products to address the risks; we then schedule test activities as close as practicable to the development activity that generated the products to be tested.Unknownnoreply@blogger.com30tag:blogger.com,1999:blog-8961250684018374499.post-85737790737673557172007-12-28T00:53:00.000-08:002008-01-06T21:31:55.837-08:00v model to w model<p><span style="font-size:130%;"><span style="font-weight: bold;">V-Model:<br /></span></span><br />The V-model promotes the idea that the dynamic test stages (on the right hand side of the model) use the documentation identified on the left hand side as baselines for testing. The V-Model further promotes the notion of early test preparation.<br /><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgiTw5pULMQEEIrn_A_VUgtjV8i6SqCi2P6X0KssEX4eMU6hYNz6HNm7v9QnG-kouj1pJ1ZyElrGTeHHHqftPQSLooMfvI-Wllh1W3FRZccfButvgUkscqtwQn6A428OkkKhwds8j4j27A/s1600-h/1-V-model.bmp"><img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgiTw5pULMQEEIrn_A_VUgtjV8i6SqCi2P6X0KssEX4eMU6hYNz6HNm7v9QnG-kouj1pJ1ZyElrGTeHHHqftPQSLooMfvI-Wllh1W3FRZccfButvgUkscqtwQn6A428OkkKhwds8j4j27A/s400/1-V-model.bmp" alt="" id="BLOGGER_PHOTO_ID_5122552005427912194" border="0" /></a></p> <div style="text-align: center;"><span style="font-weight: bold;">The V-Model of testing</span><br /></div><br />Early test preparation finds faults in baselines and is an effective way of detecting faults early. This approach is fine in principle and the early test preparation approach is always effective. However, there are two problems with the V-Model as normally presented.<br /><br /><div style="text-align: center;"><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgZOPUPRFknoWLVF82oXgFT94Yb_Cqx20oYIys8VTHAHno8HtRmIeub0Kc0GQPmeIxur6Ojj-tLOi4UPTmlV32uLUFtJinBPrlwbHh1aHn0iKCN6lGAW61BXHowUCgwH6-mqn-ucFWFalA/s1600-h/2-V-model.bmp"><img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgZOPUPRFknoWLVF82oXgFT94Yb_Cqx20oYIys8VTHAHno8HtRmIeub0Kc0GQPmeIxur6Ojj-tLOi4UPTmlV32uLUFtJinBPrlwbHh1aHn0iKCN6lGAW61BXHowUCgwH6-mqn-ucFWFalA/s400/2-V-model.bmp" alt="" id="BLOGGER_PHOTO_ID_5122552297485688338" border="0" /></a><br /><span style="font-weight: bold;">The V-Model with early test preparation</span><br /></div><br />There is rarely a perfect, one-to-one relationship between the documents on the left hand side and the test activities on the right. For example, functional specifications don’t usually provide enough information for a system test. System tests must often take account of some aspects of the business requirements as well as physical design issues for example. System testing usually draws on several sources of requirements information to be thoroughly planned.<br /><br />V-Model has little to say about static testing at all. The V-Model treats testing as a back-door activity on the right hand side of the model. There is no mention of the potentially greater value and effectiveness of static tests such as reviews, inspections, static code analysis and so on. This is a major omission and the V-Model does not support the broader view of testing as a constantly prominent activity throughout the development lifecycle.<br /><br /><span style="font-weight: bold;font-size:130%;" >W Model:</span><br /><br /><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgvtu5FYNXnYWHLlBbco_1bx6ZFsXBmWnKQrFptOVWR9zGLjI0pK-z7RtF3jPnF5dpTWa_fzCuMmGjQ_dEyuWPkH6BcMl5oVnW4WHW94HGNXCdvHUug0EwSEk3qCl_mHCh2Osr2jqr2MZQ/s1600-h/3-W-model.bmp"><img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgvtu5FYNXnYWHLlBbco_1bx6ZFsXBmWnKQrFptOVWR9zGLjI0pK-z7RtF3jPnF5dpTWa_fzCuMmGjQ_dEyuWPkH6BcMl5oVnW4WHW94HGNXCdvHUug0EwSEk3qCl_mHCh2Osr2jqr2MZQ/s400/3-W-model.bmp" alt="" id="BLOGGER_PHOTO_ID_5122552718392483362" border="0" /></a> <div style="text-align: center;"><span style="font-weight: bold;">The W-Model of testing</span><br /></div><br />Paul Herzlich introduced the W-Model approach in 1993. The W-Model attempts to address shortcomings in the V-Model. Rather than focus on specific dynamic test stages, as the V-Model does, the W-Model focuses on the development products themselves. Essentially, every development activity that produces a work product is shadowed by a test activity. The purpose of the test activity specifically is to determine whether the objectives of a development activity have been met and the deliverable meets its requirements. In its most generic form, the W-Model presents a standard development lifecycle with every development stage mirrored by a test activity. On the left hand side, typically, the deliverables of a development activity (for example, write requirements) is accompanied by a test activity test the requirements and so on. If your organization has a different set of development stages, then the W-Model is easily adjusted to your situation. The important thing is this: the W-Model of testing focuses specifically on the product risks of concern at the point where testing can be most effective.<br /><br /><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi1HoCsZvf6P-6KxgQ9-EHgFTokMoaKW_wplAF9FLPBjvhutatli8MRinBdfB0UrqvDwn2TNF3ULLQBJrtviGElWxPtZhmNy9wA5FTMzxQ3Xi__orHx91yv578OstIdUpi3mOM7pF-tTNo/s1600-h/4-W-model.bmp"><img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi1HoCsZvf6P-6KxgQ9-EHgFTokMoaKW_wplAF9FLPBjvhutatli8MRinBdfB0UrqvDwn2TNF3ULLQBJrtviGElWxPtZhmNy9wA5FTMzxQ3Xi__orHx91yv578OstIdUpi3mOM7pF-tTNo/s400/4-W-model.bmp" alt="" id="BLOGGER_PHOTO_ID_5122553040515030578" border="0" /></a> <div style="text-align: center;"><span style="font-weight: bold;">The W-Model and static test techniques.</span><br /></div><br />If we focus on the static test techniques, you can see that there is a wide range of techniques available for evaluating the products of the left hand side. Inspections, reviews, walkthroughs, static analysis, requirements animation as well as early test case preparation can all be used.<br /><br /><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEioKm2D_cvSrUFipkJR-M_wu7yuJiPG52MAavJcpUcTHKY2y6sFzLImIKxNDTvJ-ApXJ6V1IZhvMJm82rWq55ZPXSSw2CyJpbrxiz35eceBygSwbq1jMl2QmGC4nXEVEUroAQglPxhyphenhyphen7SM/s1600-h/5-W-model.bmp"><img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEioKm2D_cvSrUFipkJR-M_wu7yuJiPG52MAavJcpUcTHKY2y6sFzLImIKxNDTvJ-ApXJ6V1IZhvMJm82rWq55ZPXSSw2CyJpbrxiz35eceBygSwbq1jMl2QmGC4nXEVEUroAQglPxhyphenhyphen7SM/s400/5-W-model.bmp" alt="" id="BLOGGER_PHOTO_ID_5122553474306727490" border="0" /></a><br /><div style="text-align: center;"><span style="font-weight: bold;">The W-Model and dynamic test techniques.</span><br /></div><br />If we consider the dynamic test techniques you can see that there is also a wide range of techniques available for evaluating executable software and systems. The traditional unit, integration, system and acceptance tests can make use of the functional test design and measurement techniques as well as the non-functional test techniques that are all available for use to address specific test objectives.<br /><br />The W-Model removes the rather artificial constraint of having the same number of dynamic test stages as development stages. If there are five development stages concerned with the definition, design and construction of code in your project, it might be sensible to have only three stages of dynamic testing only. Component, system and acceptance testing might fit your normal way of working. The test objectives for the whole project would be distributed across three stages, not five. There may be practical reasons for doing this and the decision is based on an evaluation of product risks and how best to address them. The W-Model does not enforce a project symmetry that does not (or cannot) exist in reality. The W-model does not impose any rule that later dynamic tests must be based on documents created in specific stages (although earlier documentation products are nearly always used as baselines for dynamic testing. In projects using these methods, requirements and designs might be documented in multiple models so system testing might be based on several of these models (spread over several documents).<br /><br />We use the W-Model in test strategy as follows. Having identified the specific risks of concern, we specify the products that need to be tested; we then select test techniques (static reviews or dynamic test stages) to be used on those products to address the risks; we then schedule test activities as close as practicable to the development activity that generated the products to be tested.Unknownnoreply@blogger.com49tag:blogger.com,1999:blog-8961250684018374499.post-89775788159487470302007-12-28T00:52:00.001-08:002008-01-06T21:30:57.041-08:00Equivalence partitioning<p style="font-weight: bold;">Equivalence partitioning:</p><p><br /></p><p>Equivalence partitioning is a method for deriving test cases. In this method, classes of input conditions called equivalence classes are identified such that each member of the class causes the same kind of processing and output to occur.<br /><br />In this method, the tester identifies various equivalence classes for partitioning. A class is a set of input conditions that are is likely to be handled the same way by the system. If the system were to handle one case in the class erroneously, it would handle all cases erroneously.<br /><br />Equivalence partitioning drastically cuts down the number of test cases required to test a system reasonably. It is an attempt to get a good 'hit rate', to find the most errors with the smallest number of test cases.<br /><br />To use equivalence partitioning, you will need to perform four steps:<br /></p> <ul><li>Determining conditions to be Tested</li><li>Defining Tests</li><li>Designing test cases</li><li>Identifying Final set of Test Cases<br /></li></ul><br /><span style="font-weight: bold;">Defining Tests</span><br /><br />A number of items must be considered when determining the tests using the equivalence partitioning method, like:<br /><ul><li>All valid input data for a given condition are likely to go through the same process.</li><li>Invalid data can go through various processes and need to be evaluated more carefully. For example,</li><li>a blank entry may be treated differently than an incorrect entry,</li><li>a value that is less than a range of values may be treated differently than a value that is greater,</li><li>if there is more than one error condition within a particular function, one error may override the other, which means the subordinate error does not get tested unless the other value is valid.</li></ul> <span style="font-weight: bold;">Defining Test Cases</span><br /><br />Create test cases that incorporate each of the tests. For valid input, include as many tests as possible in one test case. For invalid input, include only one test in a test case in order to isolate the error. Only the invalid input test condition needs to be evaluated in such tests, because the valid condition has already been tested.<br /><br /><span style="font-weight: bold;">EXAMPLE OF EQUIVALENCE PARTITIONING</span><br /><br /><span style="font-weight: bold;">1. Conditions to be Tested</span><br /><br />The following input conditions will be tested:<br /><ul><li>For the first three digits of all social insurance (security) numbers, the minimum number is 111 and the maximum number is 222. </li><li>For the fourth and fifth digits of all social insurance (security) numbers, the minimum number is 11 and the maximum number is 99.</li></ul> <span style="font-weight: bold;">2. Defining Tests</span><br /><br />Identify the input conditions and uniquely identify each test, keeping in mind the items to consider when defining tests for valid and invalid data.<br /><br /><span style="font-weight: bold;">The tests for these conditions are:</span><br /><ul type="disc"><li class="MsoNormal" style="">The first three digits of the social insurance (security) number are:<o:p></o:p></li></ul> <ol start="1" type="1"><li class="MsoNormal" style="">= or > 111 and = or <><o:p></o:p></li><li class="MsoNormal" style=""><><o:p></o:p></li><li class="MsoNormal" style="">> 222, (invalid input, above the range),<o:p></o:p></li><li class="MsoNormal" style="">blank, (invalid input, below the range, but may be treated differently).<o:p></o:p></li></ol> <ul type="disc"><li class="MsoNormal" style="">The fourth and fifth digits of the social insurance (security) number are:<o:p></o:p></li></ul> <ol start="5" type="1"><li class="MsoNormal" style="">= or > 11 and = or <><o:p></o:p></li><li class="MsoNormal" style=""><><o:p></o:p></li><li class="MsoNormal" style="">> 99, (invalid input, above the range),</li><li class="MsoNormal" style="">blank, (invalid input, below the range, but may be treated differently).<br /></li></ol> Using equivalence partitioning, only one value that represents each of the eight equivalence classes needs to be tested.<br /><br /><span style="font-weight: bold;">3. Defining Test Cases</span><br /><br />After identifying the tests, create test cases to test each equivalence class, (i.e., tests 1 through 8).<br /><br />Create one test case for the valid input conditions, (i.e., tests 1 and 5), because the two conditions will not affect each other.<br /><br />Identify separate test cases for each invalid input, (i.e., tests 2 through 4 and tests 6 through 8).<br /><br />Both conditions specified, (i.e., condition 1 - first three digits, condition 2 - fourth and fifth digits), apply to the social insurance (security) number.<br /><br />Since equivalence partitioning is a type of black-box testing, the tester does not look at the code and, therefore, the manner in which the programmer has coded the error handling for the social insurance (security) number is not known. Separate tests are used for each invalid input, to avoid masking the result in the event one error takes priority over another.<br /><br />For example, if only one error message is displayed at one time, and the error message for the first three digits takes priority, then testing invalid inputs for the first three digits and the fourth and fifth digits together, does not result in an error message for the fourth and fifth digits. In tests B through G, only the results for the invalid input need to be evaluated, because the valid input was tested in test case A.<br /><br /><span style="font-weight: bold;">4. Suggested test cases:</span><br /><ol><li>Test Case A - Tests 1 and 5, (both are valid, therefore there is no problem with errors),</li><li>Test Case B - Tests 2 and 5, (only the first one is invalid, therefore the correct error should be produced),</li><li>Test Case C - Tests 3 and 5, (only the first one is invalid, therefore the correct error should be produced),</li><li>Test Case D - Tests 4 and 5, (only the first one is invalid, therefore the correct error should be produced),</li><li>Test Case E - Tests 1 and 6, (only the second one is invalid, therefore the correct error should be produced),</li><li>Test Case F - Tests 1 and 7, (only the second one is invalid, therefore the correct error should be produced),</li><li>Test Case G - Tests 1 and 8, (only the second one is invalid, therefore the correct error should be produced). </li></ol>Unknownnoreply@blogger.com8tag:blogger.com,1999:blog-8961250684018374499.post-14410957940394600362007-12-28T00:49:00.001-08:002008-01-06T21:28:56.496-08:00Cyclomatic complexity<p>Cyclomatic complexity is a software metric (measurement). It was developed by Thomas McCabe and is used to measure the complexity of a program. It directly measures the number of linearly independent paths through a program's source code. It is computed using a graph that describes the control flow of the program. The nodes of the graph correspond to the commands of a program. A directed edge connects two nodes if the second command might be executed immediately after the first command.<br /><br /><span style="font-size:130%;"><span style="font-weight: bold;"><br />Definition</span></span><br /><br /> M = E − N + 2P<br /><br />where<br /><br /> M = cyclomatic complexity<br /> E = the number of edges of the graph<br /> N = the number of nodes of the graph<br /> P = the number of connected components.<br /><br />"M" is alternatively defined to be one larger than the number of decision points (if/case-statements, while-statements, etc) in a module (function, procedure, chart node, etc.), or more generally a system.<br /><br />Separate subroutines are treated as being independent, disconnected components of the program's control flow graph.<br /><br /><span style="font-size:130%;"><span style="font-weight: bold;"><br />Alternative definition</span></span><br /><br /> v(G) = e − n + p<br /> G is a program's flowgraph<br /> e is the number of edges (arcs) in the flowgraph<br /> n is the number of nodes in the flowgraph<br /> p is the number of connected components<br /><br /><span style="font-size:130%;"><span style="font-weight: bold;"><br />Alternative way</span></span><br /><br />There is another simple way to determine the cyclomatic number. This is done by counting the number of closed loops in the flow graph, and incrementing that number by one.<br /><br />i.e.<br /><br /> M = Number of closed loops + 1<br /><br />where<br /><br /> M = Cyclomatic number.<br /><br /><br /><span style="font-size:130%;"><span style="font-weight: bold;">Implications for Software Testing:</span></span><br /></p><ul><li> M is a lower bound for the number of possible paths through the control flow graph.</li><li> M is an upper bound for the number of test cases that are necessary to achieve a complete branch coverage.</li></ul><br /><span style="font-size:130%;"><span style="font-weight: bold;">For example</span></span>, consider a program that consists of two sequential if-then-else statements.<br /><br />if (c1) {<br /> f1();<br />} else {<br /> f2();<br />}<br /><br />if (c2) {<br /> f3();<br />} else {<br /> f4();<br />}<br /><br /><ul><li> To achieve a complete branch coverage, two test cases are sufficient here.</li><li> For a complete path coverage, four test cases are necessary.</li><li> The cyclomatic number M is three, falling in the range between these two values, as it does for any program.<br /></li></ul><span style="font-size:130%;"><span style="font-weight: bold;"><br />Cyclomatic complexity can be applied in several areas</span></span>, including:<br /><ul><li> <span style="font-weight: bold;">Code development risk analysis</span>: While code is under development, it can be measured for complexity to assess inherent risk or risk buildup.</li><li> <span style="font-weight: bold;">Change risk analysis in maintenance</span>: Code complexity tends to increase as it is maintained over time. By measuring the complexity before and after a proposed change, this buildup can be monitored and used to help decide how to minimize the risk of the change.</li><li> <span style="font-weight: bold;">Test Planning:</span> Mathematical analysis has shown that cyclomatic complexity gives the exact number of tests needed to test every decision point in a program for each outcome. Thus, the analysis can be used for test planning. An excessively complex module will require a prohibitive number of test steps; that number can be reduced to a practical size by breaking the module into smaller, less-complex sub-modules.</li><li> <span style="font-weight: bold;">Re-engineering</span>: Cyclomatic complexity analysis provides knowledge of the structure of the operational code of a system. The risk involved in reengineering a piece of code is related to its complexity. Therefore, cost and risk analysis can benefit from proper application of such an analysis.</li></ul>Unknownnoreply@blogger.com70tag:blogger.com,1999:blog-8961250684018374499.post-26804277056911836122007-12-28T00:45:00.000-08:002008-01-03T08:00:57.963-08:00test coverage matrix vs traceblity matrix<span style="font-weight: bold;">Test coverage matrix:</span><br /><br /><span style="font-weight: bold;">Test coverage matrix</span> is a checklist which ensures that the functionality of the given screen(unit) is checked in all possible combinations (positive and negative) which have not been covered in test cases. Test coverage matrix is usually prepared for a screen having large number of controls (textboxes, dropdowns, buttons etc) usually, test coverage matrix is prepared in a spread sheet having all the controls (textboxes, dropdowns, buttons etc) in the columns and then all possible entries in those fields in the rows with an ''yes'' or ''no'' in the rows against the controls listed in the columns. For example, consider a ''login'' screen wherein we have ''username'' and ''password" textfields.<br /><br />While preparing test coverage matrix, the first column will be ''s.no'' and the second will be ''username" and ''password" will be the third field followed by ''ok'' and ''cancel'' button. Then, in the first row for s.no 1, enter ''yes'' for both ''user name'' and ''password'' columns, ''yes'' implying that a value is entered in that field. In the second row, enter ''yes'' and ''no'' and in the third row, ''no'' and 'yes'' and so on.<br /><br />The complexity increases with the number of controls in the screen. Each of the row is considered as one condition and executed while testing. This is how we prepare test coverage matrix. (this is a black box testing technique).<br /><br /><span style="font-weight: bold;">Traceability matrix:</span><br /><br />While, <span style="font-weight: bold;">Traceability matrix</span> serves in mapping the test cases to the requirements. It serves as a checklist wherein all the requirements (of srs) are listed and the test cases covering the corresponding requirement is listed against each requirement. Every company may have their own template for rtm, but they serve the same purpose as described above.Unknownnoreply@blogger.com7tag:blogger.com,1999:blog-8961250684018374499.post-16032004262062900672007-12-28T00:32:00.000-08:002007-12-28T00:34:10.679-08:00Top 24 replies by programmers when their programs don't work:<p><span style="font-family:Bookman Old Style;"><b>Top 24 replies by programmers when their programs don't work:</b><br /></span></p> <span style="font-family:Bookman Old Style;">24. "It works fine on MY computer"<br />23. "Who did you login as ?"<br />22. "It's a feature"<br />21. "It's WAD (Working As Designed)"<br />20. "That's weird..."<br />19. "It's never done that before."<br />18. "It worked yesterday."<br />17. "How is that possible?"<br />16. "It must be a hardware problem."<br />15. "What did you type in wrong to get it to crash?"<br />14. "There is something funky in your data."<br />13. "I haven't touched that module in weeks!"<br />12. "You must have the wrong version."<br />11. "It's just some unlucky coincidence."<br />10. "I can't test everything!"<br />9. "THIS can't be the source of THAT."<br />8. "It works, but it's not been tested."<br />7. "Somebody must have changed my code."<br />6. "Did you check for a virus on your system?"<br />5. "Even though it doesn't work, how does it feel?"<br />4. "You can't use that version on your system."<br />3. "Why do you want to do it that way?"<br />2. "Where were you when the program blew up?"<br />1. "I thought I fixed that."<br /></span>Unknownnoreply@blogger.com1tag:blogger.com,1999:blog-8961250684018374499.post-89758864827390777832007-12-23T20:53:00.000-08:002007-12-23T21:06:04.340-08:00A software BUG<a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg8-5BaTN5M0C6OQmKE-GVu6Hq3LJrWXAFnw8J9RM09jDh5k8-QdNuK92rFKTDSr0O6WJtTke4NaY46rRQmFljRDC7wnUrkhRr3jnO8BWYaC31HSb0SMlOU89SN8Jxn1O-ayz7-nnsE-YYu/s1600-h/image001.jpg"><img style="margin: 0pt 10px 10px 0pt; float: left; cursor: pointer;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg8-5BaTN5M0C6OQmKE-GVu6Hq3LJrWXAFnw8J9RM09jDh5k8-QdNuK92rFKTDSr0O6WJtTke4NaY46rRQmFljRDC7wnUrkhRr3jnO8BWYaC31HSb0SMlOU89SN8Jxn1O-ayz7-nnsE-YYu/s400/image001.jpg" alt="" id="BLOGGER_PHOTO_ID_5147399618740246482" border="0" /></a><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhlxrIQ_nkm4B6cIjy79kDiSQTRsPc-DStGFgyujvSlfVilkkdR04Qgemei_BIbqoKmsn6whRCJTxdH_m1_oYXfb30rltt8lFPNTCZdkU3NNg2DK1aQ7mbXbbODBoF7MVnysRNRP_CoFMxx/s1600-h/image002.jpg"><img style="margin: 0pt 10px 10px 0pt; float: left; cursor: pointer;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhlxrIQ_nkm4B6cIjy79kDiSQTRsPc-DStGFgyujvSlfVilkkdR04Qgemei_BIbqoKmsn6whRCJTxdH_m1_oYXfb30rltt8lFPNTCZdkU3NNg2DK1aQ7mbXbbODBoF7MVnysRNRP_CoFMxx/s400/image002.jpg" alt="" id="BLOGGER_PHOTO_ID_5147399618740246498" border="0" /></a><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi-FEydjWw75zf2jwe_yh-lv5wDm4814gqwrDGIxa97u3EqS8dJkmG5EeqkGszqcZvqJ0N57slzyGandRh2bUAVZpi6Wy7BHLLfETH3NNaMaSsomWQGxoDNra0jd6dQLtcfB7J2eM6ZYds1/s1600-h/image003.jpg"><img style="margin: 0pt 10px 10px 0pt; float: left; cursor: pointer;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi-FEydjWw75zf2jwe_yh-lv5wDm4814gqwrDGIxa97u3EqS8dJkmG5EeqkGszqcZvqJ0N57slzyGandRh2bUAVZpi6Wy7BHLLfETH3NNaMaSsomWQGxoDNra0jd6dQLtcfB7J2eM6ZYds1/s400/image003.jpg" alt="" id="BLOGGER_PHOTO_ID_5147399623035213810" border="0" /></a><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjXXW1hXd4iD4En9kkIj25BCxurjtF6LvGyppl-LT3bUn37weSEjU_Yjg-jNaIA8bewHoZchCWgn_XuU_R0P2g2lSyAhxFETyvtJUUeFmU5qUpP88PD2GmnQsLhxHQjTsgDpmkJIHYtYUEL/s1600-h/image004.jpg"><img style="margin: 0pt 10px 10px 0pt; float: left; cursor: pointer;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjXXW1hXd4iD4En9kkIj25BCxurjtF6LvGyppl-LT3bUn37weSEjU_Yjg-jNaIA8bewHoZchCWgn_XuU_R0P2g2lSyAhxFETyvtJUUeFmU5qUpP88PD2GmnQsLhxHQjTsgDpmkJIHYtYUEL/s400/image004.jpg" alt="" id="BLOGGER_PHOTO_ID_5147399623035213826" border="0" /></a><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiEdbCf-Yz-5A2eABvLql-0N6kAn1bAF5xIt9mtNDUBO-u8LlFx_LWV7gx10wfx0gUJP6Ie_uRTFt7qF4wsn_pqTQtziTSY9sGnqXT78VD8yXc4HQqI91ix9ExoX7HQ9SxwxkXuC0jDiPuX/s1600-h/image005.jpg"><img style="margin: 0pt 10px 10px 0pt; float: left; cursor: pointer;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiEdbCf-Yz-5A2eABvLql-0N6kAn1bAF5xIt9mtNDUBO-u8LlFx_LWV7gx10wfx0gUJP6Ie_uRTFt7qF4wsn_pqTQtziTSY9sGnqXT78VD8yXc4HQqI91ix9ExoX7HQ9SxwxkXuC0jDiPuX/s400/image005.jpg" alt="" id="BLOGGER_PHOTO_ID_5147399627330181138" border="0" /></a><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj-pC7PpPCgVUOrJdypr_Y5HU_62P5NoE8wja9ujeKaxQxbmxw8lAqK4i5U1JFV-rNLrXoy6KimZGXalTcnCYD88RU4RFSe-BzJA4YNpMEwx1KmBqYXTKNfnaIYC1o0vJa8TUqXp0rHw2B5/s1600-h/image006.jpg"><img style="margin: 0pt 10px 10px 0pt; float: left; cursor: pointer;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj-pC7PpPCgVUOrJdypr_Y5HU_62P5NoE8wja9ujeKaxQxbmxw8lAqK4i5U1JFV-rNLrXoy6KimZGXalTcnCYD88RU4RFSe-BzJA4YNpMEwx1KmBqYXTKNfnaIYC1o0vJa8TUqXp0rHw2B5/s400/image006.jpg" alt="" id="BLOGGER_PHOTO_ID_5147399915092989986" border="0" /></a><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhDieuyZBdTXiZsZqP8JzMztcMU7exAW60HX3IwM1UDrMMVRDAn9yaMQ7yj3wEEAcN26_h2D805ang2EQjZgarNffWcAQ3NAqlyZFqDH7rqzekQ-0JDa9EZ6249AtK0IZKDMsujR37y0Evk/s1600-h/image007.jpg"><img style="margin: 0pt 10px 10px 0pt; float: left; cursor: pointer;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhDieuyZBdTXiZsZqP8JzMztcMU7exAW60HX3IwM1UDrMMVRDAn9yaMQ7yj3wEEAcN26_h2D805ang2EQjZgarNffWcAQ3NAqlyZFqDH7rqzekQ-0JDa9EZ6249AtK0IZKDMsujR37y0Evk/s400/image007.jpg" alt="" id="BLOGGER_PHOTO_ID_5147399915092990002" border="0" /></a>Unknownnoreply@blogger.com3tag:blogger.com,1999:blog-8961250684018374499.post-28920679124953148832007-11-30T02:56:00.000-08:002007-11-30T03:22:53.872-08:00Some famous quotes about Software Testing"The last project generated a ton of paper and it was still a disaster, so this project will have to generate two tons." (<strong>Lister, DeMarco: "Peopleware</strong>")<br /><br />"Testing is a skill. While this may come as a surprise to some people it is a simple fact." (<strong>Fewster, Graham: "Software Test Automation")<br /><br /></strong><br />"To find the bugs that customers see - that are important to customers - you need to write tests that cross functional areas by mimicking typical user tasks. This type of testing is called scenario testing, task-based testing, or use-case testing." (<strong>Brian Marick)</strong><br /><br />"The more you improve the way you go about your work, the harder the work will be." <strong>(Lister, DeMarco: "Peopleware")</strong><br /><br />"Testing a product is a learning process." <strong>(Brian Marick)</strong><br /><br />"Most of us are pretty comfortable with the way we are, what we're doing and how we operate. But today the typical organization is telling the middle manager that he has to be a different kind of manager. These middle managers have been promoted throughout their careers and gotten bonuses based on their performance, but that's now history. ..."<strong> (Carr, Hard, Trahant: "Change Process")</strong><br /><br />"The projects most worth doing are the ones that will move you down one full level on your process scale." <strong>(Lister, DeMarco: "Peopleware")<br /><br /></strong><br />"First law of Bad Management: If something isn't working, do more of it." <strong>(DeMarco: "Slack")</strong><br /><br />"The real reason for the use of pressure and overtime may be to make everyone look better when the project fails." <strong>(DeMarco, "The Deadline")</strong><br /><br />"Projects that set out to achieve 'aggressive' schedules probably take longer to complete than they would have if they have started with more reasonable schedules."<strong> (DeMarco, "The Deadline")<br /><br /></strong><br />"The real complexity in our jobs is that all planning is done under conditions of uncertainty and ignorance. The code isn't the only think that changes. Schedules slip. New milestones are added for new features. Features are cut from the release. During development, everyone - marketers, developers and testers - comes to understand better what the product is really for." <strong>(Brian Marick)</strong><br /><br />"Companies that downsize are frankly admitting that their upper management has blown it." (<strong>Lister, DeMarco: "Peopleware")</strong><br /><br />"Everything really interesting that happens in software projects eventually comes down to people."<strong> (James Bach)</strong><br /><br />"We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools, working software over comprehensive documentation, customer collaboration over contract negotiation, responding to change over following a plan." (<strong>Agile Software Development Manifesto)<br /><br /></strong><br />"But there's more to defining processes and coordinating people than assigning someone to dream up a checklist and get it blessed in a staff meeting." <strong>(James Bach)</strong><br /><br />"If the date is missed, the schedule was wrong. It doesn't matter why the date was missed. The purpose of the schedule was planning, not goal-setting." (<strong>DeMarco: "Slack")</strong><br /><br />"Exploratory testing can be described as a martial art of the mind. It's how you deal with a product that jumps out from the bushes and challenges you to a duel of testing. Well, you don't become a black belt by reading books. You have to work on it. Happy practising." <strong>(James Bach)</strong><br /><br />"Management involves heart, gut, soul and nose. So ... lead with the heart, trust your gut ..., build soul into the organisation, develop a nose for bullshit." <strong>(DeMarco, "Deadline")<br /><br /></strong><br />"Process obsession is the problem. Process obsession is not just an anomaly that occurs now and again. It is an epidemic."<strong> (DeMarco: "Slack")<br /><br /></strong><br />"... our basic ideas about what are better or worse practices are strongly influenced by people we perceive as knowing how to make software." <strong>(James Bach)<br /><br /></strong><br />"The danger of standard process is that people will miss chances to take important shortcuts." <strong>(DeMarco, "Deadline")<br /><br /></strong><br />"I see design standards that don't tell you how to come up with a good design (only how to write it down), employee evaluation standards that don't help you build meaningful long-term relationships with staff, testing standards that don't tell you how to invent a test that is worth running."<strong> (DeMarco: "Slack")</strong><br /><br />"It's more about good enough than it is about right or wrong."<strong> (James Bach)<br /><br /></strong><br />"The ultimate management sin is wasting people's time."<strong> (Lister, DeMarco: "Peopleware")<br /><br /></strong><br />"The major problems of our work are not so much technological as sociological in nature." <strong>(Lister, DeMarco: "Peopleware")</strong><br /><br />"We all tend to tie our self-esteem strongly to the quality of the product we produce - not the quantity of the product, but the quality."<strong> (Lister, DeMarco: "Peopleware")<br /><br /></strong><br />"The only person who likes change is a wet baby." <strong>(Carr, Hard, Trahant: "Change Process")</strong><br /><br />"Documentation is not understanding, process is not discipline, formality is not skill." (Jim Highsmith)<br /><br />"A fool with a tool is still a fool."<strong> (Grady Booch)<br /><br /></strong><br />"We are still in the infancy of naming what is really happening on software development projects." <strong>(Alistair Cockburn, "Agile Software Development")<br /><br /></strong><br />"Quality is free, but only to those who are willing to pay heavily for it." <strong>(Lister, DeMarco: "Peopleware")</strong><br /><br />"A good model guides your thinking, a bad one warps it." <strong>(Brian Marick)<br /><br /></strong><br />“There is probably no job on earth for which an ability to believe six impossible things before breakfast is more of a requirement than software project management. .... The business of believing only what you have a right to believe is called risk management."<strong> (DeMarco, Lister: "Waltzing with Bears")</strong><br /><br />"Ever Tried. Ever failed. No matter.<br />Try again. Fail again. Fail better."<br /><strong>(Samuel Beckett, "Worstward Ho")</strong><br /><br />"People can't embrace change unless they feel safe. ... A lack of safety makes people risk-averse." (<strong>DeMarco, "The Deadline")</strong><br /><br />"A day lost at the beginning of a project hurts just as much as a day lost at the end. ... There are infinitely many ways to loose a day ..but not even one way to get one back."<strong> (DeMarco, "The Deadline")<br /><br /></strong><br />"This is not the end of the world, although you sure can see it from here." <strong>(The Tangent, "The music that died alone")<br /><br /></strong><br />"You can't get people to do anythink different without caring for them and about them. To get them to change, you have to understand (appreciate) where they're coming from and why. <strong>(DeMarco, "The Deadline")<br /><br /></strong><br />"If we fail, we fall. If we succeed - then we will face the next task."<strong> (Tolkien, "Lord of the Rings", Gandalf's comment on IT projects).</strong><br /><br />"It is ever so with the things that men begin: there is a frost in Spring, or a blight in Summer. and they fail of their promise."<strong> (Tolkien, "Lord of the Rings", Gimli's comment on IT projects).<br /><br /></strong><br />"Any process that tries to reduce software development to a "no brainer" will eventually produce just that: a product developed by people without brains."<strong> (Any Hunt, Dave Thomas, "Cook until done")</strong><br /><br />"Winners never talk about glorious victories. That's because they are the ones who see what the battlefield looks like afterwards. It's only the losers who have glorious victories." <strong>(Terry Pratchett, "Small Gods")<br /><br /></strong><br />"No counsel have I to give to those that despair. Yet counsel I could give, and words I could speak to you. Will you here them? They are not for all ears. ... Too long have you sat in shadows and trusted to twisted tales and crooked promptings."<strong> (Tolkien, "Lord of the Rings", the IT-Consultant Gandalf persuades a new customer)</strong><strong><br /></strong><strong></strong><div align="left"><br /></div>If I understand aright all that I have heard, I think that this task is appointed for you, ... and that if you don't find a way, no one will. This is the hour of the QA, when they arise from their quiet cubicles to shake the towers and counsels of the Great. Who of the Wise could have foreseen it? Or, if they are wise, why should they expect to know it, until the hour has struck?" (<strong>Tolkien, "Lord of the Rings", a motivational speech of CTO Elrond).</strong>Unknownnoreply@blogger.com34tag:blogger.com,1999:blog-8961250684018374499.post-44823261264224678332007-11-20T03:40:00.000-08:002007-11-20T03:40:21.569-08:00Inside AdSense: The story must go on...<a href="http://adsense.blogspot.com/2007/10/story-must-go-on.html">Inside AdSense: The story must go on...</a>: "L"Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-8961250684018374499.post-10194610343443464172007-11-19T00:04:00.000-08:002007-11-19T00:37:31.471-08:00Istqb,cste inforamtions and training centers in India<span style="font-family:arial;">About istqb:<br />The ISTQB was officially founded as an International Testing Qualifications Board in Edinburgh in November 2002 and it is responsible for the "ISTQB Certified Tester", which is an international qualification scheme.<br /><br />ISTQB is the parent body responsible for approving various national boards in addition to other tasks such as defining the syllabi for various certifications.<br />website url:<br /></span><span style=""><span class="a">www.<b>india</b>ntestingboard.com FAQ :http://208.116.30.129/faq.htm<br /><br />for examination and preparation and sample question papers available in below link<br /><br />will be helpful for ISTQB </span></span><span class="mainContent"><a href="http://208.116.30.129/resources.htm"><strong><u>http://india.istqb.org/resources.htm</u> </strong></a></span><br /><span style=""><span class="a"><br />http://www.geekinterview.com/quiz/Testing<br /><br />join yahoo groups:<br />in this group you can ask your queries about istqb examinations and certification related doubts and sample papers to certified testers..foundation level and advance level question keep on raised by members.<br /><br />ISTQB-India@ yahoogroups. com<br /><br />CSTE information:<br /><br />QAI, India, the premier knowledge corporation in the software engineering and management domain, has recently conducted the first Certified Software Test Engineer Certification examination in India. The CSTE certification is a formal recognition of proficiency-level attained in IT software testing by business and professional associates. According to Navyug Mohnot, Executive Director of QAI, “A CSTE is acknowledged to be proficient in the domains that make up the Common Body of Knowledge for the Information Systems Software Testing Profession”.<br /><br />CSTE certification is proof that you have mastered a basic skill set recognized worldwide in the Information Technology arena. It will also result in greater acceptance as an advisor to upper management. The candidates will be required to demonstrate proficiency in the following knowledge domains which make up the Common Body of Knowledge for the Information Systems Software Testing profession. The CBOK consists of topics such as Test Tactics, Quality Principles and Concepts, Design, Methods for Software Development and Maintenance,Defect Tracking and Management, Verification and Validation Methods, Quantitative Measurement, Test Reporting Risk Analysis, etc.<br /><br />Held simultaneously at Delhi, Bangalore, and Mumbai, the participants of the examination were from leading software companies like Cognizant Technology Solutions, Melstar, Satyam GE Software Services, IBM Global Services, and Patni Computer Systems.<br /><br />The Certification process<br />The CSTE brochure and exam application form can be obtained from QAI, on any working day. The eligibility criteria to appear for the examination is a bachelor’s degree or an associate degree with two years of test work experience or six years of testing experience.<br /><br />url for the site:http://www.qaiasia.com/News_room/News/qai_conducts_cert.htm<br /><br />Top Companies hiring Certified Testers:<br /><br /><br />1.Accenture India<br /><br />2.Itc info tech ,bangalore<br /><br />3.Ibm India labs<br /><br />4.US technologies<br /><br />5.Hcl<br /><br />6.Tata consultancy Services<br /><br />7.Syman tech<br /></span></span><span style="font-family:arial;"><br /></span>Unknownnoreply@blogger.com30tag:blogger.com,1999:blog-8961250684018374499.post-40812364556465445882007-04-19T23:07:00.000-07:002007-04-19T23:08:17.680-07:00testing advanced interview questions<h3 class="post-title"> <a href="http://softwaretestingqueries.blogspot.com/2007/04/testing-advanced-interview-questions.html"><br /></a> </h3> <div class="post-body"> <p><span style="font-weight: bold;">Gray Box Testing</span><br />Definition: Gray Box testing refers to the technique of testing a system with limited knowledge of the internals of the system. Gray Box testers have access to detailed design documents with information beyond requirement documents. Gray Box tests are generated based on information such as state-based models or architecture diagrams of the target system.<br /><br />So typically we can say that the Gray box testing technique is a combination of both Black box and white box testing (Partially) technique.<br /><br />Gray box testing is nothing but combination of both black box and<br />white box testing. For this tester should have knowledge of both<br />internal and external knowledge of logic.<br /><br /><span style="font-weight: bold;">what are the Essential Documents require to write manual test cases ?</span><br /><br />-Requirement Documents<br />-Use Case Documents<br />-Any previously written test cases on eairlier<br />builds.<br />-User manuals if any<br />-Walkthrough notes etc.<br /><br />what i<span style="font-weight: bold;"> CAR</span> in testing?<br /><br /><span style="font-weight: bold;"> CAR</span> stands for Causal Analysis Resolution.Causal Analysis and Resolution tool is a defect tracking mechanism. It gives the view of various defects or problems found in projects.Not only defects are analysed also if there are no defects in a project then CAR analysis can be done to check what is that the project actual does where the project didnt even faced a single defect.<br />Once the defects are analysed then a Brainstorming session will be conducted to know the problem statement.Then inputs will be discussed and also preventive action items will be taken to ensure that the defects which occurred will not appear again.Generally pareto chart and fish bone analysis diagram is used for CAR.<br /><br /><span style="font-weight: bold;">Functionality testing?<br /><br /></span><span style="font-weight: bold;">Functionality testing</span> is nothing but Requirements Testing. During this tesing Test engineer can validate the correctness of the functionality w.r.t customer requirements.<br /><br />we can validate correctness of functionality interms of Caliculation coverage, Behaviour coverage, Error Handling coverage and Back-end coverage.<br /><br />1.<span style="font-weight: bold;">caliculation coverage </span>is nothing but, can we can proper output or not ( for example<br />we have to additon operation 10+5 =12 it is not valid additon right instead of 12, 15 will be displayed)<br /><br />2.<span style="font-weight: bold;">Behaviour coverage</span>: we can check the behaviour of application<br />3.<span style="font-weight: bold;">Error Handling</span>: Occurrences of Error Message(popup messages) to prevent negative navigation.<br />4.<span style="font-weight: bold;">Back-End </span>: Impact of front end operation on back-end tables interms of Data validation and Data integrity.<br /><br /><br /><span style="font-weight: bold;"> System Testing:</span><br />System Testing is nothing to test the overall functionality of application. it is a end-to-end testing for example login -logout . In this testing tester expected to testing the application from login to logout the application. The requirements of application will be covered in System testing. It is based SRS.<br /><br /><span style="font-weight: bold;">Sytstem testing </span>consists of Usablity, Functional, Performance, Security testings.<br /><br /><br /><span style="font-weight: bold;">Fuzz testing</span> ?<br />fuzz testing is a technique that provides random data ("fuzz") to the inputs of a program. If the program fails (for example, by crashing, or by failing built-in code assertions), the defects can be noted.<br /><br />What is difference between system testing and integration testing? Can the test cases<br />written for system testing can be used for integration testing?<br />Integration testing concentrates on testing the interfaces and communication between<br />different modules. Here the assumption is since the component (modules) testing has<br />already completed we don't concentrate on the functionality.<br /><br />Coming to System testing, all the components(modules) should be ready with functionality<br />and integration testing, now we will test the functionality of the entire system as one<br />component. Generally system testing compares the system with the requirement documents<br />and is performed from end user prospective.<br /><br />Fuzz testing or fuzzing is asoftware testing technique that provides random data ("fuzz") to the inputs of a program. If the program fails (for example, by crashing, or by failing built-in code assertions), the defects can be noted.<br /><br /><br /><br />Fuzz testing or fuzzing is a software testing technique that provides random data ("fuzz") to the inputs of a program. If the program fails (for example, by crashing, or by failing built-in code assertions), the defects can be noted.<br /><br /><span style="font-weight: bold;">USES:</span><br /><br />Fuzz testing is often used in large software development projects that perform black box testing. These usually have a budget to develop test tools, and fuzz testing is one of the techniques which offers a high benefit to cost ratio.<br /><br />Fuzz testing is also used as a gross measurement of a large software system's quality. The advantage here is that the cost of generating the tests is relatively low. For example, third party testers have used fuzz testing to evaluate the relative merits of different operating systems and application programs.<br /><br />Fuzz testing is thought to enhance software security and software safty because it often finds odd oversights and defects which human testers would fail to find, and even careful human test designers would fail to create tests for.<br /><br />However, fuzz testing is not a substitute for exhaustive testing or formal methods: it can only provide a random sample of the system's behavior, and in many cases passing a fuzz test may only demonstrate that a piece of software handles exceptions without crashing, rather than behaving correctly. Thus, fuzz testing can only be regarded as a proxy for program correctness, rather than a direct measure, with fuzz test failures actually being more useful as a bug-finding tool than fuzz test passes as an assurance of quality.<br /><br /><span style="font-weight: bold;">what is Bespoke and off -the- self means?<br /><br /></span>A Software customized for a particular user group, or<br />organization is known as<span style="font-weight: bold;"> bespoke </span>software.<br /><br />It is typically in contrast with "<span style="font-weight: bold;">off-the-shelf"</span><br />software that is run by thousand or even million of<br />users.<br /><br /><span style="font-weight: bold;">characteristics of a good test case?</span><br />1. Accurate<br />2. Economical<br />3. Self standing<br />4. Appropriate<br />5. Traceable</p> </div> <div class="post-footer"> <p class="post-footer-line post-footer-line-1"> <span class="post-author"> Posted by hi </span> <span class="post-timestamp"> at <a class="timestamp-link" href="http://softwaretestingqueries.blogspot.com/2007/04/testing-advanced-interview-questions.html" title="permanent link">10:44 PM</a> </span> <span class="post-comment-link"> <a class="comment-link" href="comment.g?blogID=6205548418882643132&postID=3104900521180472401" onclick="">0 comments</a> </span> <span class="post-backlinks post-comment-link"> </span> <span class="post-icons"> <span class="item-control blog-admin pid-2125673735"> <a href="post-edit.g?blogID=6205548418882643132&postID=3104900521180472401" title="Edit Post"> <span class="quick-edit-icon"> </span> </a> </span> </span> </p> <p class="post-footer-line post-footer-line-2"> <span class="post-labels"> </span> </p> </div> <h2 class="date-header">Thursday, April 12, 2007</h2> <a name="3142131164844097930"></a> <h3 class="post-title"> <a href="http://softwaretestingqueries.blogspot.com/2007/04/advance-software-testing-terms-and.html">advance software testing terms and definations</a> </h3> <span style="font-family: verdana;"><span style="font-weight: bold;">what is testharness?</span><br /><br />Test Harness is nothing but a tool or set of tools to perform the testing of a program unit in a fully automated scenario. All the testing parameters are set in the “test script repository” of “test harnessing” tool(s) (which is nothing but testing softwares). In brief test harness includes:<br /><br /> * Predefined set of parameters, functions and inputs<br /> * A standard way to specify setup (i.e., creating an artificial runtime environment) and cleanup.<br /> * A method for selecting individual tests to run, or all tests.<br /> * A means of analyzing output for expected (or unexpected) results.<br /> * A standardized form of failure reporting.<br /><br />Test Harness engine runs in an automated manner to produce the different result scenarios based on the parameters, functions and inputs defined in the test script repository. this is a part of testing preferably large applications where manual testing will be very time consuming (or practically impossible).<br /><br />2:<span style="font-weight: bold;">Test bed</span>:Testing environment creation i.e. all required software installation, etc.<br /><br />3:<span style="font-weight: bold;">Test Plan</span> : is the document which describes whole test planning, strategy, entry exit criteria etc.<br /><span style="font-weight: bold;">QA Plan</span>: Is related to Process we will folow for testing (not sure)<br /><span style="font-weight: bold;">QA:</span> person who is involved in standards and process for testing.<br /><span style="font-weight: bold;">QC</span>: is quality control which is actal testing of software</span>Unknownnoreply@blogger.com0