tag:blogger.com,1999:blog-34795919967865577302024-03-08T10:11:04.214-08:00Quality Assurance and SW Testing AnswersKrishantha Samaraweerahttp://www.blogger.com/profile/02749322474453605527noreply@blogger.comBlogger55125tag:blogger.com,1999:blog-3479591996786557730.post-72441122199038331462008-06-19T23:12:00.000-07:002008-06-19T23:15:39.795-07:00Reduce testing cost by QA outsourcingThere are all manner of outsourcing firms who can provide you with impressive powerpoint presentations showing how you can cut your QA costs by 30% or more by outsourcing the work. I would caution you to consider the source however.<br /><br />Of course Outsourcing firms will produce evidence showing why their service is a valuable cost savings, they will even have little problem letting the managers and executives who decided to use them generate the metrics that show how much of a cost savings it was to outsource. In the case of the Outsourcing firm, it is little more than marketing speak trying to generate new business, expecting them to say any different would be like expecting a Cigarette company executive to go on Television and say "Of course Cigarettes kill people but as long as they are willing to buy them we'll be happy to take their money". As far as their Customers, well admitting that a decision to outsource was a failure would effectively end most executive's or manager's careers so they have little incentive to look too critically at the numbers.<br /><br />So how much is the cost savings?<br /><br />That depends on a LOT of factors. First, how much do your inhouse testers cost? Not just their salaries but their total cost.<br /><br />In the US and UK the total cost of an employee is considered to be around double their salary (that varies some based on the level of benefits offered, location, and other similar factors) and QA testers earn between $45,000 and $90,000 a year depending on experience level, industry, and location. This would mean that on average a Tester in the US should have an employment cost somewhere around $60 - $75 per hour. Only you would have any clue what your costs would be, I'm just including that as a reference point.<br /><br />The Bill Rates for Outsourced testers ranges from $25 - $40 per hour in places like India and China up to as much as $60 an hour for outsourced testers in industrialized countries (and it can be MUCH higher than that in some locations of if you require specialized knowledge, I've personally seen them as high as $150 per hour).<br /><br />On top of that bill rate from the outsourcing firm there are additional costs that would work out to an extra $5 - $10 per hour to cover the legal expenses of negotiating the contract with them, the necessary network infrastructure work to allow the outsourcing vendor's network interface with yours securely and so on.<br /><br />So, a reasonable projection is that in most cases Outsourcing IT work will cost around Half of what it cost to do the work in house on a per hour basis (at least for companies based in the US).<br /><br />We're not at the end of the caluclation yet though. See that is a Per Hour cost. It assumes that the Outsourced testers are able to work exactly as efficiently as your inhouse testers and with the same skill. While the question of tester skills is highly random from company to company the question of efficiency is actually fairly static. Simply moving your testers into a different building within the same complex creates enough inefficiency to make testing projects take 25 to 50% longer than they would have if they sat next to the developers. Adding in different corporate cultures or even worse national cultures, language barriers, time zone differientals, etc. and the man hour increase is closer to an additional 100% to as much as 200%.<br /><br />So a 50% reduction in cost per man hour but it takes you 2 to 3 times as many man hours says that Outsourcing is anything from a break even to a money loosing proposition until you factor in variability in skill levels between your existing test staff and the staff at whoever you outsource to. If you have very weak testers and are unable to recruit better ones the it may be that outsourcing will produce a small cost savings of maybe 10 to 20% of your testing costs.<br /><br />I have yet to encounter an Outsourced testing situation where it actually saved money. Many VP's, Director's, and Manager's claimed it did on the basis of reduced per hour labor costs but never one that was a net positive to the company once all of the outsourcing costs were factored in.<div class="blogger-post-footer"><!-- Begin BlogToplist tracker code -->
<a href="http://www.blogtoplist.com" title="Blog Directory">
<img src="http://www.blogtoplist.com/tracker.php?u=9123" alt="Blog Directory" border="0" /></a>
<noscript><a href="http://www.blogtoplist.com/rss/bollywood.html">Bollywood</a></noscript>
<!-- End BlogToplist tracker code --></div>Krishantha Samaraweerahttp://www.blogger.com/profile/02749322474453605527noreply@blogger.com5tag:blogger.com,1999:blog-3479591996786557730.post-63348824062067173792008-03-19T05:30:00.000-07:002008-03-19T05:32:39.964-07:00Leap Year TestingA bug has been discovered in the Community Technology Previews (CTP) of SQL<br />Server 2008 related to leap year. The result of this bug is that SQL Server<br />2008 services will not start during the 24 hours of Feb 29 GMT.<br /><br />This issue affects customers using any version of SQL Server 2008 on any<br />supported operating system. Although there is no known impact on SQL Server<br />2005 or prior versions at this time, we are continuing research on all<br />versions.<br /><br />* Do not start or stop SQL Server 2008 Database Engine services during the<br />24 hour period of Feb 29, GMT<br />* Do not install or upgrade SQL Server 2008 during the 24 hour period of Feb<br />29, GMT.<br /><br />So how my site visitors testing their product for leap year bugs?<div class="blogger-post-footer"><!-- Begin BlogToplist tracker code -->
<a href="http://www.blogtoplist.com" title="Blog Directory">
<img src="http://www.blogtoplist.com/tracker.php?u=9123" alt="Blog Directory" border="0" /></a>
<noscript><a href="http://www.blogtoplist.com/rss/bollywood.html">Bollywood</a></noscript>
<!-- End BlogToplist tracker code --></div>Krishantha Samaraweerahttp://www.blogger.com/profile/02749322474453605527noreply@blogger.com0tag:blogger.com,1999:blog-3479591996786557730.post-52236246234922679112008-03-19T05:21:00.000-07:002008-03-19T05:25:45.561-07:00Selenium core vs Selenium IDE vs Selenium RC<style type="text/css">-- @page { size: 8.5in 11in; margin: 0.79in } P { margin-bottom: 0.08in } --> </style> <p style="margin-bottom: 0in;">I got a chance to use this valuable tool which is light weighted and user friendly. It can be used by any technical or non-technical users as well. I really love this tool.<br /></p> <p style="margin-bottom: 0in;"><br /></p><p style="margin-bottom: 0in;">Selenium IDE is a plugin or call it an extension to Firefox, just like Firebug, Chatzilla but with a different functionality and purpose altogether. The recording mode plugin is not available for IE.<br /><br />Basically Selenium IDE records its tests in HTML and then uses those tests to execute through browser. But users can covert HTML script to ruby,php,phython,C# or java by Options->Format.<br /><br />But when you need them to execute the tests altogether as a test suite then follow the link change the test according the requirements and also modify different execution mechanism as required.<br /><br /><a href="http://wiki.%20openqa.org/%20display/SIDE/%20Automating+%20Selenium+%20IDE+tests" target="_blank">http://wiki. openqa.org/ display/SIDE/ Automating+ Selenium+ IDE+tests</a><br /><br /></p> <p style="margin-bottom: 0in;">Selenium Core and Selenium RC are used to execute the recorded script.<br /><br /></p> <p style="margin-bottom: 0in;">If you application does not work on Firefox or if it is not intended to work on Firefox according to the requirements then its better to use Selenium Core.<br /><br /></p> <p style="margin-bottom: 0in;">Some useful resource like tutorials and downloads on the net for beginners<br /><a href="http://selenium.openqa.org/" target="_blank">http://selenium. openqa.org/</a><br /><a href="http://en.wikipedia.org/wiki/Selenium_%28software%29" target="_blank">http://en.wikipedia .org/wiki/ Selenium_ %28software% 29</a></p><p style="margin-bottom: 0in;"><br /></p><p style="margin-bottom: 0in;"><a href="http://en.wikipedia.org/wiki/Selenium_%28software%29" target="_blank"><br /></a></p><div class="blogger-post-footer"><!-- Begin BlogToplist tracker code -->
<a href="http://www.blogtoplist.com" title="Blog Directory">
<img src="http://www.blogtoplist.com/tracker.php?u=9123" alt="Blog Directory" border="0" /></a>
<noscript><a href="http://www.blogtoplist.com/rss/bollywood.html">Bollywood</a></noscript>
<!-- End BlogToplist tracker code --></div>Krishantha Samaraweerahttp://www.blogger.com/profile/02749322474453605527noreply@blogger.com3tag:blogger.com,1999:blog-3479591996786557730.post-26875517399393227832008-03-02T09:35:00.000-08:002009-02-19T23:05:23.298-08:00I missed a BUGMost of the testers/QAs are concern about external issues that they have missed. Carrier wise external issues are not good for testers profile inside their organization. More external issues may destroy the testers reputation within organization. On the other hand it is not fair to put 100% responsibility of external issues to testers. Why testers miss bugs?.<br /><br />1.Lack of project management.<br />2.Not enough time to test.<br />3.Requirement change in last moment before releases.<br />4.Lack of domain knowledge.<br />5.Lack of QA/test resources.<br />6.Poor requirement specifications.<br />7.Limited time to acquire domain knowledge.<br />8.Selecting automation testing in the earlier stage of project. ( Where manually testing is required.)<br />9.High coupling with developers. ( testers who depends of developers to get domain/technical knowledge may influence by developers.<br />10.Not enough motivation towards testing. ( more open bugs, ignorance of QA team within organization, lost of existing functionalities due to new bugs, less salary.... )<br />11.Developers/QA/tester attitude towards bugs.<br /><br />Surely, there are more to add for above reasons list, Above points can be categorized in to two.<br /><br />1.Self factors<br />2.Organization factors.<br /><br />Anyway most of the above factors caused due to lots of sub reasons. Head of the organization or middle layer management should take actions to treat the organization factors. Immediate supervisor should care about the testes self factors.<br /><br />I would like to mention one of my story here. Last week I found a bug which was missed in first release of the project. Luckily that bug was found by me after the release. If external user report that bug, things may have got worse. The project is small one so it can be tested by one QA resource. “Unnecessary text” is appeared top left had corner of the screen. Actually text was an e-mail password of one of our developer. Mistakenly he has type it in JSP file . I have been testing that project around one month before the release. It is shame of me. Why I have missed this idiot UI bug? What are the precautions that I can take to eliminate this kind of bugs in future.<br /><br />Main Reasons (My excuse)<br />1.UI theme has changed 3 days before final release. So little time to test new UI theme.<br /><br />But could have found this bug If I had used JSP/HTML/CSS validation tool. Yes it is good to learn by mistakes. And it may be more than good to share that mistake with others (to learn by others mistakes)<br /><br />Some of the tool that you can use for this kind of work are given below.<br /><br /><a href="http://validator.w3.org/">http://validator.w3.org </a><br /><a href="http://jigsaw.w3.org/css-validator">http://jigsaw.w3.org/css-validator/</a><br />J2EE verifier tool – JSP validation.<br /><br />I have heard that Australian wicket keeper Adam Gilchrist going to retire from cricket due to the reason that he missed a catch. According to him what I should do?<div class="blogger-post-footer"><!-- Begin BlogToplist tracker code -->
<a href="http://www.blogtoplist.com" title="Blog Directory">
<img src="http://www.blogtoplist.com/tracker.php?u=9123" alt="Blog Directory" border="0" /></a>
<noscript><a href="http://www.blogtoplist.com/rss/bollywood.html">Bollywood</a></noscript>
<!-- End BlogToplist tracker code --></div>Krishantha Samaraweerahttp://www.blogger.com/profile/02749322474453605527noreply@blogger.com0tag:blogger.com,1999:blog-3479591996786557730.post-12166970138176841212008-02-06T21:45:00.000-08:002008-02-06T21:46:41.250-08:00Cross Browser Testing<p style="margin-bottom: 0in;">It is critical to test across many browser and operating system combinations because the page can look different in each scenario. Another concern is the screen resolution and color depth. A page might look good at a resolution of 600 x 800, but parts of it might get cut off at 640 x 480. Different color depths should be used on the test machines also. Colors might vary unpredictably if a browser-safe palette is not used. As a QA, we should look for:<br /><br />Color of links<br />Broken images<br />Low color contrast<br />Spacing in tables<br />Text wrapping issues<br />Margins<br />Alignment, formatting, and size of text </p> <p style="margin-bottom: 0in;">Alignment of controls such as radio buttons and check boxes<br />Switch Javascript off<br />Switch cookies off<br />Switch plug-ins off<br />Switch images off<br />Printing - Do not forget to test printing of your Web pages by printing on a variety of popular printers. Printing can be unpredictable, particularly with frames. Keep an eye on what is printed, the readability of content, and the speed of the print job.</p> <p style="margin-bottom: 0in;"><br /></p> <p style="margin-bottom: 0in;">Be sure to use clean machines when you start testing and make sure no plug-ins are installed. If the plug-ins are already installed,you might miss a defect that has a dependency on the plug-in. There should always be some test cases that involve using a browser as it is first installed,with no extra components.<br /><br /></p> <p style="margin-bottom: 0in;">Netscape Navigator requires a plug-in.Netscape users must be aware that the plug-in is required and should be given instructions on how to install it. (Anyway Netscape is a dying browser)<br /><br /></p> <p style="margin-bottom: 0in;">View in text browser (Incidentally the Opera browser has a built-in text-browser emulator) </p><div class="blogger-post-footer"><!-- Begin BlogToplist tracker code -->
<a href="http://www.blogtoplist.com" title="Blog Directory">
<img src="http://www.blogtoplist.com/tracker.php?u=9123" alt="Blog Directory" border="0" /></a>
<noscript><a href="http://www.blogtoplist.com/rss/bollywood.html">Bollywood</a></noscript>
<!-- End BlogToplist tracker code --></div>Krishantha Samaraweerahttp://www.blogger.com/profile/02749322474453605527noreply@blogger.com0tag:blogger.com,1999:blog-3479591996786557730.post-43596022417908290542008-01-18T00:40:00.000-08:002008-01-18T00:42:19.097-08:00Suggestions to Improve Testing.1) List down the modules to be tested.This include functional and non-functional testing<br /><br />2) List down the functionality that you will not test either because of incompleteness of module, data dependency or hardware limitations etc.<br /><br />3) Pl. get formal approval from your manager for the activities/schedule that you are planning.This will endorse your deliverables and validity.<br /><br />4) Make sure that you have the defect tracking system in place with severity norms and owners defined.The defect logging format should be approved by your manager.<br /><br />5) Make sure that you have set of data that will help you in testing various test scenarios.If data is not available, pl. check how you can generate the same.<br /><br />6) Make sure that you take daily back-up of your test logs and discuss progress and issues with your management team every day.<br /><br />7) Keep talking with developers. That will help you to increase product understanding.<br /><br />8) Release notes from Developer team to Testing team will be entry criteria to start testing activity. The release notes will include information like the defects fixed in the build, any work around ,features not addressed.<br /><br />9) Multiple iterations of testing will bring up new defects. Periodically update the test cases checking the possibility of new scenerios.Once the defect probability starts reducing in further testing iterations, this may be the indication of product getting stable. Introducing multiple testing heads will also help to filter new defects.<br /><br />10)Try to set the processes with help of your manager. Eventually that will be helpful in long run.<div class="blogger-post-footer"><!-- Begin BlogToplist tracker code -->
<a href="http://www.blogtoplist.com" title="Blog Directory">
<img src="http://www.blogtoplist.com/tracker.php?u=9123" alt="Blog Directory" border="0" /></a>
<noscript><a href="http://www.blogtoplist.com/rss/bollywood.html">Bollywood</a></noscript>
<!-- End BlogToplist tracker code --></div>Krishantha Samaraweerahttp://www.blogger.com/profile/02749322474453605527noreply@blogger.com0tag:blogger.com,1999:blog-3479591996786557730.post-46939649803167809062008-01-18T00:34:00.001-08:002008-01-18T00:35:01.623-08:00process defect and shipment defectIf a defect is detected in testing department while testing the application is called in process defect.<br /><br />After release the software if a client finds the bug in their environment (production environment) then it is called as post shipment defect.<div class="blogger-post-footer"><!-- Begin BlogToplist tracker code -->
<a href="http://www.blogtoplist.com" title="Blog Directory">
<img src="http://www.blogtoplist.com/tracker.php?u=9123" alt="Blog Directory" border="0" /></a>
<noscript><a href="http://www.blogtoplist.com/rss/bollywood.html">Bollywood</a></noscript>
<!-- End BlogToplist tracker code --></div>Krishantha Samaraweerahttp://www.blogger.com/profile/02749322474453605527noreply@blogger.com1tag:blogger.com,1999:blog-3479591996786557730.post-43183394851714477142008-01-10T23:29:00.000-08:002008-01-10T23:32:53.290-08:00Balanced QA team<p>Balanced team.. may be a traditional management term. However, I am trying to understand the term in quality assurance perspective. In my experience most of the QA teams do not consist of the right set of skill combinations required to get the maximum out of available resources. First I believe the following members should be included in a balanced QA team.</p> <ul><li>Domain/subject matter expert</li><li>Test automation expert</li><li>Deployment/build expert</li><li>Security testing expert</li><li>Performance testing expert</li><li>Database technology expert</li></ul>read more from : <a href="http://charithaka.blogspot.com/">http://charithaka.blogspot.com/</a><br /><br />I have came across this nice blog post written by Charitha. I totally agree with what he says in the post .<div class="blogger-post-footer"><!-- Begin BlogToplist tracker code -->
<a href="http://www.blogtoplist.com" title="Blog Directory">
<img src="http://www.blogtoplist.com/tracker.php?u=9123" alt="Blog Directory" border="0" /></a>
<noscript><a href="http://www.blogtoplist.com/rss/bollywood.html">Bollywood</a></noscript>
<!-- End BlogToplist tracker code --></div>Krishantha Samaraweerahttp://www.blogger.com/profile/02749322474453605527noreply@blogger.com0tag:blogger.com,1999:blog-3479591996786557730.post-16944753237244236802007-12-07T00:24:00.000-08:002007-12-07T00:25:33.569-08:00How to approach towards the powered product1. First your Org. need to propose the Study phase.Customer should mutually agree on this with your org. for the schedule and the billing the resources during this activity.<br /><br />2. Need to analyze the existing application from the feature, technology ,architecture , usability and maintenance point of view. Document the existing as well as new requirements which are not addressed by the current application. Document all the issues categorizing them as major and minor.<br /><br />3. Check that what is the needful support and mechanism presently available to address the existing issues and new requirements.<br /><br />4. Propose the reverse engineering phase to support the existing application. Propose documentation project for existing application from maintenance point of view.<br /><br />5. Check if your org. has executed any such projects in the past history. This is to understand the the issues in prior implementation and risk associated. You should able to project the domain expertise needful for this assignment by studying the past project history.<br /><br />6. Check customer has any budget allocation for new software development and any plans to upgrade / change the existing application.<br /><br />With all this analysis , you will be in the position to propose new project to the customer. You need to present the case studies ,domain expertise , the cost effectiveness for the solution that your org. is suggesting over the existing products in the market and timeline to the solution. Iterative discussions with your internal teams and the customer will help you to go ahead.<div class="blogger-post-footer"><!-- Begin BlogToplist tracker code -->
<a href="http://www.blogtoplist.com" title="Blog Directory">
<img src="http://www.blogtoplist.com/tracker.php?u=9123" alt="Blog Directory" border="0" /></a>
<noscript><a href="http://www.blogtoplist.com/rss/bollywood.html">Bollywood</a></noscript>
<!-- End BlogToplist tracker code --></div>Krishantha Samaraweerahttp://www.blogger.com/profile/02749322474453605527noreply@blogger.com0tag:blogger.com,1999:blog-3479591996786557730.post-4000021057322495342007-11-27T22:52:00.000-08:002007-11-27T22:53:59.095-08:00What is the advantage of running the virtual user as thread?VuGen provides the facility to use multithreading. This enables more virtual user to be run per generator. If the Vuser is run as a process, the same driver program is loaded into memory for each Vuser, thus taking up a large amount of memory. This limits the number of virtual user that can be run on a single generator. If the Vuser is run as a thread, only one instance of the driver program is loaded into memory for the given number of virtual user (say 100). Each thread shares the memory of the parent driver program, thus enabling more virtual user to be run per generator<div class="blogger-post-footer"><!-- Begin BlogToplist tracker code -->
<a href="http://www.blogtoplist.com" title="Blog Directory">
<img src="http://www.blogtoplist.com/tracker.php?u=9123" alt="Blog Directory" border="0" /></a>
<noscript><a href="http://www.blogtoplist.com/rss/bollywood.html">Bollywood</a></noscript>
<!-- End BlogToplist tracker code --></div>Krishantha Samaraweerahttp://www.blogger.com/profile/02749322474453605527noreply@blogger.com0tag:blogger.com,1999:blog-3479591996786557730.post-15056973762954279572007-11-27T22:49:00.000-08:002007-11-27T22:50:06.454-08:00Regarding testing techniques in the field of space researchmmmmmmmmmm, really a different !!!!!!!!!! see we can test operations on different temprature conditions,and we can test it in minus gravitational force. We can test it further by giving different virus(!!) to it. Virus means infected programs that may cause severe damage,atleast there will be such chance in some % atleast.We can do adhoc testing 2 test operation so that we get to know,how they work in chaotic condiotions.By giving stress we can get to know the exactly that what system do exactly??<div class="blogger-post-footer"><!-- Begin BlogToplist tracker code -->
<a href="http://www.blogtoplist.com" title="Blog Directory">
<img src="http://www.blogtoplist.com/tracker.php?u=9123" alt="Blog Directory" border="0" /></a>
<noscript><a href="http://www.blogtoplist.com/rss/bollywood.html">Bollywood</a></noscript>
<!-- End BlogToplist tracker code --></div>Krishantha Samaraweerahttp://www.blogger.com/profile/02749322474453605527noreply@blogger.com0tag:blogger.com,1999:blog-3479591996786557730.post-27122785632892262262007-11-27T22:25:00.000-08:002007-11-27T22:27:31.577-08:00DbFit 0.92: Better error reporting and easier regression testsA new release of DbFit is available for download from <span style="border-bottom: 1px dashed rgb(0, 102, 204); cursor: pointer;" class="yshortcuts" id="lw_1196231048_0">SourceForge </span>(<a rel="nofollow" target="_blank" href="http://sourceforge.net/project/showfiles.php?group_id=191053&package_id=224326&release_id=556930">http://sourceforge. net/project/ showfiles. php?group_ id=191053& package_id= 224326&release_ id=556930</a>).<br /><br />DbFit is a free extension library for FIT/FitNesse testing framework. It allows developers to manipulate database objects in a relational style, making it much easier to manage and test database objects than with xUnit-style tests. DbFit supports .NET and Java integration tests, and Oracle, SQL Server and MySQL database engines.<br /><br />Release 0.92 (2007-11-26) brings:<br /><br />- Better error handling, DbFit now prints out missing column/parameter names and warns if table/procedure could not be found new Inspect fixture to help with regression tests: DatabaseTest has three methods to automate it: InspectQuery, InspectProcedure and InspectTable. These methods will quickly print out entire query results, structure of a procedure or a table/view in a form that can be easily converted to a regression test, or used as a template for<br />ExecuteProcedure, Insert or Update tables. support for Oracle procedure and package synonyms Type details are read from SqlServer in a more efficient way,<br />supporting objects with dots in names and fixing few edge cases where<br />duplicate records were retrieved with 0.91 null keyword handled correctly in Java<br /><br />For more information on DbFit, see <a rel="nofollow" target="_blank" href="http://gojko.net/fitnesse/dbfit"><span class="yshortcuts" id="lw_1196231048_1">http://gojko. net/fitnesse/ dbfit</span></a><div class="blogger-post-footer"><!-- Begin BlogToplist tracker code -->
<a href="http://www.blogtoplist.com" title="Blog Directory">
<img src="http://www.blogtoplist.com/tracker.php?u=9123" alt="Blog Directory" border="0" /></a>
<noscript><a href="http://www.blogtoplist.com/rss/bollywood.html">Bollywood</a></noscript>
<!-- End BlogToplist tracker code --></div>Krishantha Samaraweerahttp://www.blogger.com/profile/02749322474453605527noreply@blogger.com0tag:blogger.com,1999:blog-3479591996786557730.post-4223528611041935762007-11-16T03:59:00.001-08:002008-03-02T10:01:53.735-08:00QA Time EstimationThere are a great many people who will tell you there is a "standard" ratio of QA hours to Development hours. Don't listen to them. Anyone who makes that claim probably does not know what they are talking about.<br /><br />Take for example the difference between implementing a new desktop application for internal use and implementing a new web app that is available to the general public.<br /><br />In the first case, you have to verify that the application works on 1 machine configuration (the weakest CPU/Memory combination with the supported OS in your company), Security testing is restricted to making sure that the user roles are configured (if you even have role based security, there might not need to be any security testing on an internal app). Depending on a myriad of factors the QA hours for a project like this could range anywhere between 30% and 120% of the dev hours.<br /><br />In the second case you need to verify that the app works on somewhere between 5 and 50 different OS/Browser combinations with several different Hardware configurations thrown in for good measure plus you now need to start throwing in web security testing where you have someone who knows what they are doing validate that your site is protected at least against the most common hacker attacks. Again depending on other factors for a project like this the QA/Dev hour ratio could be anywhere from 2/3 (66%) to 2.5/1 (250%).<br /><br />This is just looking at the differences between 2 different types of new applications, some other factors that will influence the QA/Dev hour ratio are...<br /><br /><br />Maturity of the product,<br />Quality of the requirements,<br />Level of domain knowledge of the Dev/Business/ QA team members,<br />Development model followed (waterfall, agile, etc.),<br />Breakdown of roles and responsibilities between the teams (different companies have different expectations between Dev and QA) ,<br />Physical proximity of the Dev/Business/ QA teams (people are more efficient when they work together)<br />Level of quality needed (Banking and health care industries have much stricter quality requirements than an entertainment application)<br />Team Sizes (Smaller teams are more efficient than larger ones)<br />Effectiveness of Change Control Procedures<br />Scale of the project (Defects increase exponentially with the scale of the project, more defects means more QA time and therefore a higher ratio of QA hrs to dev hrs)<br />Quality of the Code (The single largest factor)<br />Quality of Documentation<br />Availability of test data (only applies to some projects)<br />Quality of the QA team (actually a much more minor factor than you'd think)<br /><br /><br />And I am sure there are several dozen more than I'm not thinking of off the top of my head. I have seen projects the ratio of QA hours to dev hours was as little as 1/10 (10%) and as high as 5/1 (500%) .<br /><br /><br />Now what you can do is over time develop a set of standard ratios for different types of projects at your company. You do this by first accurately measuring your projects for a year or two, then going back, finding reasonable groupings of similar projects and deriving average ratios between the two sets of time then when the next project comes up you can do a relatively simple analysis of which type of project it was most like and use that average in planning. If you do this you also need to keep measuring all future projects to ensure that the averages hold and do not drift too far over time<div class="blogger-post-footer"><!-- Begin BlogToplist tracker code -->
<a href="http://www.blogtoplist.com" title="Blog Directory">
<img src="http://www.blogtoplist.com/tracker.php?u=9123" alt="Blog Directory" border="0" /></a>
<noscript><a href="http://www.blogtoplist.com/rss/bollywood.html">Bollywood</a></noscript>
<!-- End BlogToplist tracker code --></div>Krishantha Samaraweerahttp://www.blogger.com/profile/02749322474453605527noreply@blogger.com2tag:blogger.com,1999:blog-3479591996786557730.post-66753810887348310242007-11-16T03:55:00.000-08:002007-11-16T03:56:15.415-08:00Approve or disapprove the releaseThe same situation mostly happens with most of us. I think the most important thing here is QA setup similar to Production environment. This is the right time to highlight the risk factors which can cause the release unsuccessful b/c of unavailability of proper testing environment. This is only one side which can be seen this time, that you can't test the email sending at the time of order placement. What about in next requirement list or wish list, if an other option is require by user which also contain this auto email sending option. What you will do next time?<br /><br />If the testing environment can't be setup as production environment<br />Sit with your project management team (top players)...keep the situation in front of them...get the things document (not only risk factors but your suggestion also)....discuss with them....confirm more about white box testing and/or unit testing for complete order placement code...give your standing and take the mutual decision.... and document them against your (QA) response.<br /><br />Its definitely better to get things document b/c this can only be your evidence if things goes worse. With my experience I always try t<div class="blogger-post-footer"><!-- Begin BlogToplist tracker code -->
<a href="http://www.blogtoplist.com" title="Blog Directory">
<img src="http://www.blogtoplist.com/tracker.php?u=9123" alt="Blog Directory" border="0" /></a>
<noscript><a href="http://www.blogtoplist.com/rss/bollywood.html">Bollywood</a></noscript>
<!-- End BlogToplist tracker code --></div>Krishantha Samaraweerahttp://www.blogger.com/profile/02749322474453605527noreply@blogger.com0tag:blogger.com,1999:blog-3479591996786557730.post-66039722019149213652007-11-16T03:48:00.001-08:002007-11-16T03:48:29.605-08:00Test Execution EstimatesEven though you can not estimate exactly, but you can estimate the execution time efforts depending on the Function Points in your Test Cases.<br /><br />You will have to categorize your test cases in 3 different categories e.g. Critical / Major / Minor and then can check timing for 5 test cases from each group. Take average of that and multiply with number of test cases in respective groups.<br /><br />This will not give you exact estimate, but it will definitely give estimate near to actual time.<br /><br />I have tried this in my past projects and could successfully delviered my product within given time frame.<br /><br />I will also recommend to add 10 to 15 % extra time, so that if you get stuck some where or considering some obstacles in testing, you can deliver product within your estimated time.<div class="blogger-post-footer"><!-- Begin BlogToplist tracker code -->
<a href="http://www.blogtoplist.com" title="Blog Directory">
<img src="http://www.blogtoplist.com/tracker.php?u=9123" alt="Blog Directory" border="0" /></a>
<noscript><a href="http://www.blogtoplist.com/rss/bollywood.html">Bollywood</a></noscript>
<!-- End BlogToplist tracker code --></div>Krishantha Samaraweerahttp://www.blogger.com/profile/02749322474453605527noreply@blogger.com1tag:blogger.com,1999:blog-3479591996786557730.post-75005670570010265312007-11-16T03:41:00.001-08:002007-11-16T03:46:07.210-08:00QA Time vs. Development TimeWell, if this was an interview question, maybe the interviewer was looking to find out how you would think through the problem. As was stated by the moderator and others, there really isn’t a good formula. Different groups have different methods/processes/ tools/models by which they arrive at their estimates. I think it’s safe to make a statement that those methods/processes/ tools/models take into consideration some of the variables that are outlined below.<br /><br />Specifically speaking to the models, they should be reviewed periodically based on historical data to see if there are updates that are required. In my current organization, one of the items on our plates is to revisit our current estimation model. We’ve got our first release under our belts and are part way through our second release. We have some data to begin refining our estimation model. This will be an ongoing process where the model is periodically reviewed and updated.<br /><br />Getting back to the original question, if this was an interview question, then you might want to explore an answer within the context of your current role and explain to the interviewer that this is the context in which you’re answering your question.<br /><br />Just a different way to explore it<br /><br />There is no formula.There are too many variables: the maturity of the product, the quality of the developers' work, the skill of the developers, the skill of the<br />testers, development and test environments, etc.. In the end, there is no formula based on developers' time<div class="blogger-post-footer"><!-- Begin BlogToplist tracker code -->
<a href="http://www.blogtoplist.com" title="Blog Directory">
<img src="http://www.blogtoplist.com/tracker.php?u=9123" alt="Blog Directory" border="0" /></a>
<noscript><a href="http://www.blogtoplist.com/rss/bollywood.html">Bollywood</a></noscript>
<!-- End BlogToplist tracker code --></div>Krishantha Samaraweerahttp://www.blogger.com/profile/02749322474453605527noreply@blogger.com1tag:blogger.com,1999:blog-3479591996786557730.post-87049126839488242892007-07-17T04:28:00.000-07:002007-07-17T04:52:19.774-07:00What’s the difference between Severity and Priority?Severity rates a defect in terms of its impact on the software under test (SUT) and/or on its environment; Priority (a.k.a URGENCY or CRITICALITY) rates it in terms of its impact on human stakeholders (the customer, users, developers, testers …).<br /><br />A common (rather subjective) scale of SEVERITY goes like this (sometimes the numbers are reversed):<br /><br />1. Critical - The defect results in the termination of the complete SUT or one or more component applications of the SUT (or of associated software such as the operating system), and/or causes extensive corruption of stored data. The failed function is unusable and there is no acceptable alternative method to achieve the required results.<br /><br />2. Major - The defect results in the termination of the complete SUT or one or more component applications of the SUT (or of associated software such as the operating system), or causes extensive corruption of stored data; but although the failed function is unusable, there exists an acceptable alternative method to achieve the required results.<br /><br />3. Moderate - The defect does not result in a termination, but causes the system to produce incorrect, incomplete, or inconsistent results, or the defect impairs the systems usability.<br /><br />4. Minor - The defect does not result in a termination, and does not impair usability, and the desired processing results are easily obtained by working around the defect.<br /><br />5. Cosmetic - The defect is the result of non-conformance to a standard, is related to the aesthetics of the system, or is a request for an enhancement. Defects at this level may be deferred or even ignored.<br /><br />PRIORITY will be partially based on Severity, but should take into account other factors such as the frequency with which the defect results in failure, the degree of “visibility” of failure (e.g., how many users it will affect, with what impact on their work, and whether it will be visible to external<br />customers), and project-related factors such as the impact on continued development or testing.<br /><br />A commonly-used scale of PRIORITY reads:<br /><br />1. Resolve Immediately - Further development and/or testing cannot occur until the defect has been repaired. The system cannot be used until the repair has been effected.<br /><br />2. Give High Attention - The defect must be resolved as soon as possible because it is impairing development/and or testing activities. System use will be severely affected until the defect is fixed.<br /><br />3. Normal Queue - The defect should be resolved in the normal course of development activities. It can wait until a new build or version is created.<br /><br />4. Low Priority - The defect is an irritant which should be repaired, but repair can be deferred until after more serious defect have been fixed.<br /><br />5. Suspend - The defect repair can be put off indefinitely. It can be resolved in a future major system revision or not resolved at all.<div class="blogger-post-footer"><!-- Begin BlogToplist tracker code -->
<a href="http://www.blogtoplist.com" title="Blog Directory">
<img src="http://www.blogtoplist.com/tracker.php?u=9123" alt="Blog Directory" border="0" /></a>
<noscript><a href="http://www.blogtoplist.com/rss/bollywood.html">Bollywood</a></noscript>
<!-- End BlogToplist tracker code --></div>Krishantha Samaraweerahttp://www.blogger.com/profile/02749322474453605527noreply@blogger.com0tag:blogger.com,1999:blog-3479591996786557730.post-11765315389388490532007-07-17T04:26:00.000-07:002007-07-17T04:28:07.634-07:00Define Test Scenario<p class="MsoNormal"><b style=""><span style="font-size: 10pt; font-family: Georgia; color: rgb(51, 51, 51);">Test Scenario:</span></b><span style="font-size: 10pt; font-family: Georgia; color: rgb(51, 51, 51);"> Test Scenario is the user workflow in the application.<!--[if !supportLineBreakNewLine]--><br /> <!--[endif]--><o:p></o:p></span></p> <p class="MsoNormal"><span style="font-size: 10pt; font-family: Georgia; color: rgb(51, 51, 51);">Example: Checking Mail in Yahoo is a scenario, where user login, check the mail in inbox and then logoff. This application can have 2 different test case one for login and other one for inbox.<o:p><br /></o:p></span></p> <p class="MsoNormal"><span style="font-size: 10pt; font-family: Georgia; color: rgb(51, 51, 51);">So Test Scenario can consist of different test cases.</span><span style="font-family: Georgia;"><o:p></o:p></span></p><div class="blogger-post-footer"><!-- Begin BlogToplist tracker code -->
<a href="http://www.blogtoplist.com" title="Blog Directory">
<img src="http://www.blogtoplist.com/tracker.php?u=9123" alt="Blog Directory" border="0" /></a>
<noscript><a href="http://www.blogtoplist.com/rss/bollywood.html">Bollywood</a></noscript>
<!-- End BlogToplist tracker code --></div>Krishantha Samaraweerahttp://www.blogger.com/profile/02749322474453605527noreply@blogger.com0tag:blogger.com,1999:blog-3479591996786557730.post-78905889510359293002007-07-10T05:18:00.000-07:002007-07-10T05:21:11.548-07:00How keep track of Test cases and Testing done by the testersBelieve in doing the right thing the first time...<br /><br />Start creating the test wares based on the flow charts (or activity diagram) of the module you wish to test...<br /><br />This flowchart must be approved by the R&D counterparts.<br /><br />It is also recommended that you create an integration map of the module with other related modules. This will help you to develop the integration cases. So once you receive the release notes with a bug fix,you know which all integration cases you need to execute.<br /><br />Traceability matrix is a very useful tool in case you need to keep track that none of the requirements are missed out while writing cases. The flow chart will ensure that none of the paths/scenarios are skipped out.<br /><br />Maintain the cases in excel so that you can use formulas to track the cases written/executed and even the pass/fail statistics easily... Some of the useful columns for tracking purposes are date of execution,defect id (for failed cases), Requirement number, Test case id<div class="blogger-post-footer"><!-- Begin BlogToplist tracker code -->
<a href="http://www.blogtoplist.com" title="Blog Directory">
<img src="http://www.blogtoplist.com/tracker.php?u=9123" alt="Blog Directory" border="0" /></a>
<noscript><a href="http://www.blogtoplist.com/rss/bollywood.html">Bollywood</a></noscript>
<!-- End BlogToplist tracker code --></div>Krishantha Samaraweerahttp://www.blogger.com/profile/02749322474453605527noreply@blogger.com0tag:blogger.com,1999:blog-3479591996786557730.post-14900338129532097422007-06-19T05:01:00.000-07:002007-06-19T05:02:09.483-07:00A tipical Test Plan contentSummery<br />Objectives<br />Test Approach and Assumptions<br />Major Test Responsibilities<br />Features and Functionality to Test<br />Expected Result of Tests<br />Deliverables<br />Test Documentation<br />Test Data<br />Interactions with Other organizations<br />Testing Procedures and Walkthrough<br />Testing Setup<br />Testing Procedure<br />Testing Walkthrough<br />Tracking and Reporting Status<br />Test Resource Requirements<br />Environmental Needs<br />Staffing & Training Needs<br />Test Tool Requirements<br />Bug Reporting Tools and Methods<br />Bug Reporting Tool Strategy<br />Bug Classification Strategy<br />Triage Strategy<br />Bug Closure Ciretria<br />Schedule<br />Risks & Dependencies<br />Open Issues<br />Appendix<br />Appendix A - Test Case Specification Example<div class="blogger-post-footer"><!-- Begin BlogToplist tracker code -->
<a href="http://www.blogtoplist.com" title="Blog Directory">
<img src="http://www.blogtoplist.com/tracker.php?u=9123" alt="Blog Directory" border="0" /></a>
<noscript><a href="http://www.blogtoplist.com/rss/bollywood.html">Bollywood</a></noscript>
<!-- End BlogToplist tracker code --></div>Krishantha Samaraweerahttp://www.blogger.com/profile/02749322474453605527noreply@blogger.com0tag:blogger.com,1999:blog-3479591996786557730.post-81570986245039350622007-06-19T04:48:00.000-07:002007-06-19T04:51:56.240-07:00ISO Certification standards in Quality Assurance perspectiveThe ISO 9001:2000 Quality Management System certification enables you to demonstrate your commitment to quality and customer satisfaction, as well as continuously improving your quality systems and integrating the realities of a changing world<br /><br />ISO 9001:2000 is based on eight quality management principles<br /><br />customer focus<br />leadership<br />involvement of people<br />process approach<br />system approach<br />continual improvement<br />fact-based decision making<br />mutually beneficial supplier relationships<div class="blogger-post-footer"><!-- Begin BlogToplist tracker code -->
<a href="http://www.blogtoplist.com" title="Blog Directory">
<img src="http://www.blogtoplist.com/tracker.php?u=9123" alt="Blog Directory" border="0" /></a>
<noscript><a href="http://www.blogtoplist.com/rss/bollywood.html">Bollywood</a></noscript>
<!-- End BlogToplist tracker code --></div>Krishantha Samaraweerahttp://www.blogger.com/profile/02749322474453605527noreply@blogger.com0tag:blogger.com,1999:blog-3479591996786557730.post-91513489835251592302007-06-19T04:47:00.000-07:002007-06-19T04:48:29.954-07:00whats is testing effort estimationEffort estimation can be done, based on different techniques available like Function Point Analysis, COCOMO, Use Case Point Analysis, Test Case Point Analysis, Metrics based.<br /><br />Effort estimation is basically done any of the above techniques for different test activities like Test Case Preparation, Automation Script Creation and Test Execution.<br /><br />Let me explain the metrics based and very commonly used effort estimation procedure in doing effort estimation for Yahoo Mail application.<br /><br /><br />Identify the requirements (Login Page, Inbox, Compose, Address)<br /><br />Classify the requirements in different complexity (Simple, Average, High)<br /><br />Based on the past experience, metrics will be collected on how much time it took to write test case for simple, average and high functionality. Similarly it is collected for other testing<br />activities.<br /><br />Now multiply your complexity with the time factor which you derived from metrics to calculate the effort.<br /><br />Don't report the total has your total effort, always use buffer time, it various based on the domain, tool and other factors. Example we use 20% on the previous total. This buffer will save you<br />on risk and other deadline factors<br /><br />Now add you the buffer time and the effort calculated from metrics, and this is your Total effort for the activity.<br /><br />Test Case Point Analysis: You can use this effort estimation technique<br />for Test Automation and Test Execution.<br /><br />1. Identify the total number of test cases to be automated or executed.<br />2. Classify the steps into High, Medium and Low complexity based on the<br />business process it performs.<br />3. Based on the previous experience (metrics based) on how much time it<br />would take to execute High complexity steps. You can have the average<br />time.<br />4. Multiply this average time with total number of steps and get the<br />total<br />5. Add the buffer time with the total to get Final estimation time. This<br />buffer time will vary based on the application, domain and other<br />factors.<br /><br />Most of these effort estimation techniques use Metrics Based, which you are going to calculate the actual time for all effort and then take the average.<div class="blogger-post-footer"><!-- Begin BlogToplist tracker code -->
<a href="http://www.blogtoplist.com" title="Blog Directory">
<img src="http://www.blogtoplist.com/tracker.php?u=9123" alt="Blog Directory" border="0" /></a>
<noscript><a href="http://www.blogtoplist.com/rss/bollywood.html">Bollywood</a></noscript>
<!-- End BlogToplist tracker code --></div>Krishantha Samaraweerahttp://www.blogger.com/profile/02749322474453605527noreply@blogger.com1tag:blogger.com,1999:blog-3479591996786557730.post-75568614847865167112007-06-11T05:30:00.001-07:002007-06-11T05:30:57.536-07:00Manual Testing or Automation Testing<o:p></o:p>Here are few points to share on Manual Testing or Automation Testing:<o:p></o:p> <p class="MsoNormal"><o:p> </o:p></p> <p class="MsoNormal">1) Any Automation testing scripts can cover only 60 to 80 % of entire product testing<o:p><br /></o:p></p> <p class="MsoNormal">2) There should be separate team other than testing team to develop and maintain automation test scripts Should never mix testing team and automation test script development team.<o:p><br /></o:p></p> <p class="MsoNormal">3) Automation is good for the products where software product is tending to stable condition and there are marginal feature changes in next coming releases. Here the manual testing team is moved to some other product testing assignment and test scripts are sufficient to check core features of the software product.<o:p><br /></o:p></p> <p class="MsoNormal">4) Automation and manual testing should be of right mix. Manual testing can not be avoided.<o:p><br /></o:p></p> <p class="MsoNormal">5) It is decision of project manager for budgeting the automation test script development.<o:p><br /></o:p></p> <p class="MsoNormal">6) Certainly, there are pros and cons for both manual and automation testing.<o:p><br /></o:p></p> <p class="MsoNormal">7) The decision based on type of the application, type of the resources available[software, hardware and human] , product deliverable time line and most important - the budget.</p><div class="blogger-post-footer"><!-- Begin BlogToplist tracker code -->
<a href="http://www.blogtoplist.com" title="Blog Directory">
<img src="http://www.blogtoplist.com/tracker.php?u=9123" alt="Blog Directory" border="0" /></a>
<noscript><a href="http://www.blogtoplist.com/rss/bollywood.html">Bollywood</a></noscript>
<!-- End BlogToplist tracker code --></div>Krishantha Samaraweerahttp://www.blogger.com/profile/02749322474453605527noreply@blogger.com0tag:blogger.com,1999:blog-3479591996786557730.post-74279929499742660862007-06-11T00:39:00.000-07:002007-06-11T00:41:36.051-07:00What is the Bug Free Zone?<p class="MsoNormal">The Bug Free Zone is a membership-based community of professionals sponsored by the International Institute for Software Testing providing a wealth of information for software test and QA professionals. <o:p></o:p></p><p class="MsoNormal"><o:p> </o:p></p> <p class="MsoNormal">- Get acess to Articles - Software Testing Articles written by practitioners for practitioners<o:p></o:p></p> <p class="MsoNormal">- Get access to Conference Presentations – Complete decks from past PSQT Conferences <o:p></o:p></p> <p class="MsoNormal">- Get access to Test Process Templates - Downloadable templates for different tasks in the test process.<o:p></o:p></p> <p class="MsoNormal">- Discussion Board - Communicate and Interact with other QA and Test Professionals.<o:p></o:p></p> <p class="MsoNormal">- Download papers on different Testing and QA Topics<o:p></o:p></p> <p class="MsoNormal">- Get access to the IIST Unified Testing Terminology<o:p></o:p></p> <p class="MsoNormal">- Listen to Industry experts offering software quality and testing tips on a regular basis<o:p></o:p></p> <p class="MsoNormal">- Post jobs or look at job postings<o:p></o:p></p> <p class="MsoNormal">- Get answers to many questions you may have on different testing and QA topics<o:p></o:p></p> <p class="MsoNormal"><o:p> </o:p><br />Membership is free at <a href="http://www.iist.org">http://www.iist.org</a></p><div class="blogger-post-footer"><!-- Begin BlogToplist tracker code -->
<a href="http://www.blogtoplist.com" title="Blog Directory">
<img src="http://www.blogtoplist.com/tracker.php?u=9123" alt="Blog Directory" border="0" /></a>
<noscript><a href="http://www.blogtoplist.com/rss/bollywood.html">Bollywood</a></noscript>
<!-- End BlogToplist tracker code --></div>Krishantha Samaraweerahttp://www.blogger.com/profile/02749322474453605527noreply@blogger.com0tag:blogger.com,1999:blog-3479591996786557730.post-16600369796741218742007-06-10T21:52:00.000-07:002007-06-10T21:55:22.558-07:00Development hours Vs QA hours<p class="MsoNormal">Variable that change ratio of development hours to QA hours.<span style=""></span><span style=""></span><o:p></o:p></p> <p class="MsoNormal"><span style=""> </span><o:p></o:p></p> <ul><li>Are the QA and Dev teams equivalently skilled between the 2 projects?</li></ul><p class="MsoNormal"><!--[if !supportLineBreakNewLine]--> <!--[endif]--><o:p></o:p></p> <ul><li>Are the QA and Dev teams equivalently knowledgable between the 2 projects?<o:p><br /></o:p></li></ul> <ul><li>In the business envrionment similar between the 2 projects?<o:p><br /></o:p></li></ul> <ul><li>Is the Development model similar between the 2 projects?<o:p><br /></o:p></li></ul> <ul><li>Is the structure of the 2 projects similar? (testing an engancement to an existing system is a vastly different animal from testing new development)<o:p><br /></o:p></li></ul> <ul><li>Are the breakdown of responsibilities for each team the same between the 2 projects?(maybe in 1 Dev handles Configuration Management and deployment, in another QA Does for example)<o:p><br /></o:p></li></ul> <ul><li>Do both Projects have similar data requirements? (testing a system which has a large database behind it is vastly different from tesing one with a rudimentary one)<o:p><br /></o:p></li></ul> <ul><li>Do both Projects have similar target audiences? (Code intended for trained specialists has different requirements from code intended for the general public)<o:p><br /></o:p></li></ul> <ul><li>Do both Projects run in the same sets of operational envrionments? (Hardware, OS, Browser, JDK, .Net Framework, etc.)<o:p><br /></o:p></li></ul> <ul><li>Do both projects support the same number of sets of operational envrionments<o:p></o:p></li></ul> <p class="MsoNormal"><span style=""> </span><br />And that is just off the top of my head I have come up with 10 variables that will vastly change the ratio of development time to QA time and I'm sure there are at least another 10 I've missed.<span style=""> </span><o:p></o:p></p> <p class="MsoNormal">So really the discussion needs to be not on what percentage of development hours should QA take but rather how do we accurately estimate how long it will take to test a project. We also need to be vigilant and immediately challenge ANYONE who mentions a ratio between Development hours and QA hours in any context except "Well Project X is similar to Project Y and in Project X QA time was Z% of Dev time so in Project Y the Ratio should be close to Z%".</p><div class="blogger-post-footer"><!-- Begin BlogToplist tracker code -->
<a href="http://www.blogtoplist.com" title="Blog Directory">
<img src="http://www.blogtoplist.com/tracker.php?u=9123" alt="Blog Directory" border="0" /></a>
<noscript><a href="http://www.blogtoplist.com/rss/bollywood.html">Bollywood</a></noscript>
<!-- End BlogToplist tracker code --></div>Krishantha Samaraweerahttp://www.blogger.com/profile/02749322474453605527noreply@blogger.com1