tag:blogger.com,1999:blog-15786771785616457172024-03-20T19:24:29.539-07:00SoftWare TestinGThis Blog Contains information on Unit Testing, Integration Testing, System Testing, User Acceptance Testing, SAP Testing, SOA Testing, Web Testing, End to End Testing, Web Services Testing, Regression Testing, Testing Automation, Performance Testing, Stress Testing, Load Testing, Volume Testing, Security Testing, Testing COTS, Defects, Bug ,Fixes, Testing Tools like QTP, Load Runner, Quality Center, Rational Robot and many more related to software testing.Software Testinghttp://www.blogger.com/profile/03753363363746376712noreply@blogger.comBlogger200125tag:blogger.com,1999:blog-1578677178561645717.post-34218575618024211962013-01-21T04:30:00.000-08:002013-01-21T04:31:14.132-08:00Methodology of Test Effort Estimation<br><div><font face="Arial" style="color:rgb(1,0,42);background-color:rgb(237,237,237)"><font face="Arial"><p><span class="GRcorrect">est</span> Estimation in Software Testing industry is similar to time management that we do in our day to day lives. In order to understand what test effort estimation is, let us understand the term estimation first.</p> <p>Estimation is the intelligent anticipation of the amount of work that must be done and the resources (human, financial resources, equipment resources and time resources) needed to perform the work at a future date, in a defined environment, using specific methods.</p> <p>Most of you who have never done Test estimation before must have actually done it though you haven't realized it.</p><p>Let's consider an example for this. You want to attend your office at 9:00. So you estimate the time it would take you to reach office say, 45 minutes. And you take 15 minutes for your morning walk, 30 minutes to get ready & 20 minutes for breakfast. So to reach office on time you would need to wake up no later than 7:10AM.</p> <b><p>Now let us understand test effort estimation.</p></b><p>Test estimation is the process of estimating the testing cost, testing effort, testing size & schedule of testing for a particular project on software testing under a specific environment, with the help of specified methods, testing tools & test techniques.</p> <p>Software Testing estimation is important as it is directly linked with the project cost & deadline. Estimation is based on:</p></font></font><b style="color:rgb(1,0,42);font-family:Arial,Helvetica,sans-serif;font-size:13px;background-color:rgb(237,237,237)"><font color="#800000" face="Arial"><font color="#800000" face="Arial"><font color="#800000" face="Arial"></font></font></font></b><font color="#800000" face="Arial" style="background-color:rgb(237,237,237)"><font color="#800000" face="Arial"><font color="#800000" face="Arial"></font></font></font><p style="color:rgb(1,0,42);font-family:Arial,Helvetica,sans-serif;font-size:13px;background-color:rgb(237,237,237)"> <font color="#800000" face="Arial"><font color="#800000" face="Arial"><font color="#800000" face="Arial"><b># Documents/Knowledge available:</b></font></font></font><font face="Arial"> Requirement Specification Document, Domain Knowledge, Tool Understanding<br> </font></p><b style="color:rgb(1,0,42);font-family:Arial,Helvetica,sans-serif;font-size:13px;background-color:rgb(237,237,237)"><font color="#800000" face="Arial"><font color="#800000" face="Arial"><font color="#800000" face="Arial"></font></font></font></b><font color="#800000" face="Arial" style="background-color:rgb(237,237,237)"><font color="#800000" face="Arial"><font color="#800000" face="Arial"></font></font></font><p style="color:rgb(1,0,42);font-family:Arial,Helvetica,sans-serif;font-size:13px;background-color:rgb(237,237,237)"> <font color="#800000" face="Arial"><font color="#800000" face="Arial"><font color="#800000" face="Arial"><b># Assumptions:</b></font></font></font><font face="Arial"> Requirement Doc is complete, builds will be stable etc.<br> </font></p><b style="color:rgb(1,0,42);font-family:Arial,Helvetica,sans-serif;font-size:13px;background-color:rgb(237,237,237)"><font color="#800000" face="Arial"><font color="#800000" face="Arial"><font color="#800000" face="Arial"></font></font></font></b><p style="color:rgb(1,0,42);font-family:Arial,Helvetica,sans-serif;font-size:13px;background-color:rgb(237,237,237)"> <b><font color="#800000" face="Arial"><font color="#800000" face="Arial"><font color="#800000" face="Arial"># Calculated Risks:</font></font></font><font face="Arial"><font face="Arial"> </font></font></b><font face="Arial">Manpower cost, lack of system understanding, backup resources available or not etc.<br> </font></p><b style="color:rgb(1,0,42);font-family:Arial,Helvetica,sans-serif;font-size:13px;background-color:rgb(237,237,237)"><font color="#800000" face="Arial"><font color="#800000" face="Arial"><font color="#800000" face="Arial"></font></font></font></b><font color="#800000" face="Arial" style="background-color:rgb(237,237,237)"><font color="#800000" face="Arial"><font color="#800000" face="Arial"></font></font></font><p style="color:rgb(1,0,42);font-family:Arial,Helvetica,sans-serif;font-size:13px;background-color:rgb(237,237,237)"> <font color="#800000" face="Arial"><font color="#800000" face="Arial"><font color="#800000" face="Arial"><b># Past Experience:</b></font></font></font><font face="Arial"> Past experience or historical data</font></p><font face="Arial" style="color:rgb(1,0,42);background-color:rgb(237,237,237)"><font face="Arial"><p> There are different standard & non-standard methods of doing test estimation. <span class="GRcorrect">Many</span> Managers/Leads are not comfortable in doing estimation as it is a time consuming activity. So they follow a non-standard way of estimation based on their past experience. But, if they are asked to work on some new technology/domain then it is difficult for them to do test estimation.</p> </font></font><b style="color:rgb(1,0,42);font-family:Arial,Helvetica,sans-serif;font-size:13px;background-color:rgb(237,237,237)"><font color="#000080" face="Arial"><font color="#000080" face="Arial"><font color="#000080" face="Arial"><p> Methods of software test estimation:<br></p></font></font></font></b><font color="#000080" face="Arial" style="background-color:rgb(237,237,237)"><font color="#000080" face="Arial"><font color="#000080" face="Arial"></font></font></font><p style="color:rgb(1,0,42);font-family:Arial,Helvetica,sans-serif;font-size:13px;background-color:rgb(237,237,237)"> <font color="#000080" face="Arial"><font color="#000080" face="Arial"><font color="#000080" face="Arial"><b>1) Function Point Analysis / Test Point Analysis:<br></b></font></font></font><font face="Arial">FPA is an ISO recognized method. Measure the functional size of an information system / application. Size reflects the amount of functionality from the <span class="GRcorrect">functional</span> or user, point of view. Independent of the technology used to implement the system and is totally dependent on the SRS (Specification Requirement Document)</font></p> <font face="Arial" style="color:rgb(1,0,42);background-color:rgb(237,237,237)"><font face="Arial"><p>Formula to calculate FP:</p><p>FP = UFP * VAF</p><p>Where UFP – Sum of complexities of basic functions - <i>Internal logical files (known as ILF), External interface files (known as EIF), External inputs (known as EI), External outputs (known as EO), External <span class="GRcorrect">enquiries</span> (known as EQ)</i></p> <p>VAF – Value adjustment factor.</p><p><span class="GRcorrect">Number</span> of the test cases = FP *1<span class="GRcorrect">.</span>2 (Caper Jones formula)</p><p>Test effort = Number of the test cases * (%age of development effort/100)</p> <b></b><p><b>Drawback:</b> Detailed SRS <span class="GRcorrect">is required</span>.</p></font></font><b style="color:rgb(1,0,42);font-family:Arial,Helvetica,sans-serif;font-size:13px;background-color:rgb(237,237,237)"><font color="#000080" face="Arial"><font color="#000080" face="Arial"><font color="#000080" face="Arial"></font></font></font></b><font color="#000080" face="Arial" style="background-color:rgb(237,237,237)"><font color="#000080" face="Arial"><font color="#000080" face="Arial"></font></font></font><p style="color:rgb(1,0,42);font-family:Arial,Helvetica,sans-serif;font-size:13px;background-color:rgb(237,237,237)"> <font color="#000080" face="Arial"><font color="#000080" face="Arial"><font color="#000080" face="Arial"><b>2) Work Breakdown Structure (WBS):<br></b></font></font></font><font face="Arial">Break down each testing task <i>(map the task with each deliverable as per requirement document)</i> into the smallest chunk or sub-tasks. Now do the estimation for each sub task.</font></p> <b style="color:rgb(1,0,42);font-family:Arial,Helvetica,sans-serif;font-size:13px;background-color:rgb(237,237,237)"><font color="#000080" face="Arial"><font color="#000080" face="Arial"><font color="#000080" face="Arial"></font></font></font></b><font color="#000080" face="Arial" style="background-color:rgb(237,237,237)"><font color="#000080" face="Arial"><font color="#000080" face="Arial"></font></font></font><p style="color:rgb(1,0,42);font-family:Arial,Helvetica,sans-serif;font-size:13px;background-color:rgb(237,237,237)"> <font color="#000080" face="Arial"><font color="#000080" face="Arial"><font color="#000080" face="Arial"><b>3) Point Estimation Technique:<br></b></font></font></font><font face="Arial">It resembles with WBS estimation method, break down every testing task into sub task & then do following three estimations on each entity:</font></p> <b style="color:rgb(1,0,42);font-family:Arial,Helvetica,sans-serif;font-size:13px;background-color:rgb(237,237,237)"><font color="#800000" face="Arial"><font color="#800000" face="Arial"><font color="#800000" face="Arial"></font></font></font></b><font color="#800000" face="Arial" style="background-color:rgb(237,237,237)"><font color="#800000" face="Arial"><font color="#800000" face="Arial"></font></font></font><p style="color:rgb(1,0,42);font-family:Arial,Helvetica,sans-serif;font-size:13px;background-color:rgb(237,237,237)"> <font color="#800000" face="Arial"><font color="#800000" face="Arial"><font color="#800000" face="Arial"><b># Best Case/ Positive scenarios:</b></font></font></font><font face="Arial"> Where everything goes right, P</font></p> <b style="color:rgb(1,0,42);font-family:Arial,Helvetica,sans-serif;font-size:13px;background-color:rgb(237,237,237)"><font color="#800000" face="Arial"><font color="#800000" face="Arial"><font color="#800000" face="Arial"></font></font></font></b><font color="#800000" face="Arial" style="background-color:rgb(237,237,237)"><font color="#800000" face="Arial"><font color="#800000" face="Arial"></font></font></font><p style="color:rgb(1,0,42);font-family:Arial,Helvetica,sans-serif;font-size:13px;background-color:rgb(237,237,237)"> <font color="#800000" face="Arial"><font color="#800000" face="Arial"><font color="#800000" face="Arial"><b># Worst Case/Negative scenarios:</b></font></font></font><font face="Arial"> Where everything goes wrong, N<br></font></p> <b style="color:rgb(1,0,42);font-family:Arial,Helvetica,sans-serif;font-size:13px;background-color:rgb(237,237,237)"><font color="#800000" face="Arial"><font color="#800000" face="Arial"><font color="#800000" face="Arial"></font></font></font></b><font color="#800000" face="Arial" style="background-color:rgb(237,237,237)"><font color="#800000" face="Arial"><font color="#800000" face="Arial"></font></font></font><p style="color:rgb(1,0,42);font-family:Arial,Helvetica,sans-serif;font-size:13px;background-color:rgb(237,237,237)"> <font color="#800000" face="Arial"><font color="#800000" face="Arial"><font color="#800000" face="Arial"><b># Average Case/Exceptional scenarios:</b></font></font></font><font face="Arial"> Where few things go right & few deviates from the actual <span class="GRcorrect">plan</span>, A</font></p> <font face="Arial" style="color:rgb(1,0,42);background-color:rgb(237,237,237)"><font face="Arial"><p>Test Effort Estimate = P + 4*N + A/6</p><p></p></font></font><b style="color:rgb(1,0,42);font-family:Arial,Helvetica,sans-serif;font-size:13px;background-color:rgb(237,237,237)"><font color="#000080" face="Arial"><font color="#000080" face="Arial"><font color="#000080" face="Arial"></font></font></font></b><font color="#000080" face="Arial" style="background-color:rgb(237,237,237)"><font color="#000080" face="Arial"><font color="#000080" face="Arial"></font></font></font><p style="color:rgb(1,0,42);font-family:Arial,Helvetica,sans-serif;font-size:13px;background-color:rgb(237,237,237)"> <font color="#000080" face="Arial"><font color="#000080" face="Arial"><font color="#000080" face="Arial"><b>4) Delphi Method:<br></b></font></font></font><font face="Arial">It is similar to <span class="GRcorrect">WBS estimation method</span>; here task & sub-tasks are allocated to the team members or some experts. Then team members/experts give the estimate that how much time they will take to complete each task. And finally their estimates are consolidated to reach the final estimate for each task.</font></p> <b style="color:rgb(1,0,42);font-family:Arial,Helvetica,sans-serif;font-size:13px;background-color:rgb(237,237,237)"><font color="#000080" face="Arial"><font color="#000080" face="Arial"><font color="#000080" face="Arial"></font></font></font></b><font color="#000080" face="Arial" style="background-color:rgb(237,237,237)"><font color="#000080" face="Arial"><font color="#000080" face="Arial"></font></font></font><p style="color:rgb(1,0,42);font-family:Arial,Helvetica,sans-serif;font-size:13px;background-color:rgb(237,237,237)"> <font color="#000080" face="Arial"><font color="#000080" face="Arial"><font color="#000080" face="Arial"><b>5) Use Case Points:<br></b></font></font></font><font face="Arial"><span class="GRcorrect">Use case</span> is a document, which describes the behavior and interaction of the system as the reaction to a specific query or action of an actor. Here actor means either an end-user or the stakeholder. An interaction is initiated by the primary actor with some specific objectives in mind. The system then provides response by safeguarding the interests of all concerned actors. According to the requests made & various conditions surrounding those requests, system behavior/ flow can be opened up. Test cases are based on the Use Cases.</font></p> <b style="color:rgb(1,0,42);font-family:Arial,Helvetica,sans-serif;font-size:13px;background-color:rgb(237,237,237)"><font color="#000080" face="Arial"><font color="#000080" face="Arial"><font color="#000080" face="Arial"></font></font></font></b><font color="#000080" face="Arial" style="background-color:rgb(237,237,237)"><font color="#000080" face="Arial"><font color="#000080" face="Arial"></font></font></font><p style="color:rgb(1,0,42);font-family:Arial,Helvetica,sans-serif;font-size:13px;background-color:rgb(237,237,237)"> <font color="#000080" face="Arial"><font color="#000080" face="Arial"><font color="#000080" face="Arial"><b>Conclusion:</b></font></font></font><font face="Arial"><font face="Arial"> <i>Estimation is not a close-ended document, but a live document. You should keep your estimation document updated as and when you sense a change from actual happening in <span class="GRcorrect">field</span>. It should be reviewed continuously during <span class="GRcorrect">course</span>.</i></font></font></p> </div> Software Testinghttp://www.blogger.com/profile/03753363363746376712noreply@blogger.com15tag:blogger.com,1999:blog-1578677178561645717.post-37412461711978774802013-01-08T14:06:00.001-08:002013-01-08T14:06:36.470-08:00SAP Test Acceleration and Optimization (SAP TAO)<table width="600" border="0" align="center" cellpadding="0" cellspacing="0" style="color:rgb(0,0,0);font-family:Tahoma,Arial,Helvetica,sans-serif;font-size:13px"><tbody><tr><td height="30" align="left" valign="middle" class="subh3" style="font-family:'Trebuchet MS',Verdana,Arial,Helvetica,sans-serif;font-size:13px;font-weight:bold;color:rgb(244,4,4)"> SAP Test Acceleration and Optimization (SAP TAO):</td></tr><tr><td height="656" align="left" valign="top" class="style1" style="font-family:Tahoma,Arial,Helvetica,sans-serif;font-size:13px;text-align:justify;color:rgb(51,51,51)"> <br><span class="subh1" style="font-family:'Trebuchet MS',Verdana,Arial,Helvetica,sans-serif;font-size:14px;font-weight:bold;color:rgb(10,108,206)">Purpose Of SAPTAO:</span><br><br>The highly secure and mission-critical nature of enterprise resource planning (ERP) data requires many SAP customers to test their ERP applications and business processes regularly. Many SAP customers use expensive customized manual procedures to test processes and applications. Manual testing is time-consuming, and frequently requires a team of experienced quality assurance (QA) professionals. Subject matter experts also often need to spend a lot of time communicating the process data flow to testers. <br> SAP Test Acceleration and Optimization streamlines the creation and maintenance of ERP business process testing. <br><br>SAP Test Acceleration and Optimization helps QA specialists to break down a test into components which are:<br> <br>Assembled into test cases in a simple interface, using drag and drop <br>Parameterized for flexible reuse, such as reusing a test that has updated data <br>Maintained easily and inexpensively, even when screens, flows, or service packs change <br> <br>SAP Test Acceleration and Optimization is designed for SAP-GUI-based applications. SAP Test Acceleration and Optimization users should be experienced quality managers who are familiar with the SAP Quality Center application <span class="GRcorrect">by</span> HP, SAP GUI ERP applications, and business process testing.<br> <br>Automatic testing with SAP Test Acceleration and Optimization maximizes: <br><br><span class="subh1" style="font-family:'Trebuchet MS',Verdana,Arial,Helvetica,sans-serif;font-size:14px;font-weight:bold;color:rgb(10,108,206)">Testing deployment</span> <br> SAP Test Acceleration and Optimization, with <span class="GRcorrect">SAP Quality Center</span>, dramatically reduces the amount of time required to build and execute test scripts. <br><br><span class="subh1" style="font-family:'Trebuchet MS',Verdana,Arial,Helvetica,sans-serif;font-size:14px;font-weight:bold;color:rgb(10,108,206)">Reuse</span> <br> SAP Test Acceleration and Optimization eliminates the need to create new tests whenever a component changes. If one component in a group of tests changes, replace that component, and re-consolidate the tests<br><br><span class="subh1" style="font-family:'Trebuchet MS',Verdana,Arial,Helvetica,sans-serif;font-size:14px;font-weight:bold;color:rgb(10,108,206)">Maintenance</span> <br> SAP Test Acceleration and Optimization records component parameters. It provides a Microsoft Excel spreadsheet to save parameters for reuse and maintenance. SAP Test Acceleration and Optimization helps you to determine the need for repairs, and helps you to repair your components.<br> <br><span class="subh1" style="font-family:'Trebuchet MS',Verdana,Arial,Helvetica,sans-serif;font-size:14px;font-weight:bold;color:rgb(10,108,206)">Robustness</span> <br>The SAP Test Acceleration and Optimization inspection process ensures that SAP Test Acceleration and Optimization tests are more robust during changes. Inspection examines the parameter in a component, not just the screen object behavior.</td> </tr><tr><td height="342" align="left" valign="top" class="style1" style="font-family:Tahoma,Arial,Helvetica,sans-serif;font-size:13px;text-align:justify;color:rgb(51,51,51)"><img src="http://www.mysaptesting.com/images/sap-tao-arch.jpg" width="590" height="463"></td> </tr><tr><td height="278" align="left" valign="top" class="style1" style="font-family:Tahoma,Arial,Helvetica,sans-serif;font-size:13px;text-align:justify;color:rgb(51,51,51)"><span class="subh1" style="font-family:'Trebuchet MS',Verdana,Arial,Helvetica,sans-serif;font-size:14px;font-weight:bold;color:rgb(10,108,206)">SAP TAO</span><br> <br>The SAP Test Acceleration and Optimization Clent application runs on <span class="GRcorrect">Windows System</span>. It Performs 6 Key functions <br>1 .PFA (Process Flow Analyzer)<br>2. Inspection/UI Scanner<br>3. Import/Export<br> 4. Change Analysis<br>5. Repository<br>6. Consolidator<br><br><span class="subh1" style="font-family:'Trebuchet MS',Verdana,Arial,Helvetica,sans-serif;font-size:14px;font-weight:bold;color:rgb(10,108,206)">Configuration</span><br> <br>License Validation:<br>* Once Installation is complete, Double Click on the SAPTAO Icon on the Desktop. SAPTAO UI Appears. <br>* Click on the "Configuration" Link on the top right of the screen and select the "License" Tab<br> * Select the Solution Manager system from the <span class="GRcorrect">System</span> List <br>* Click on Test SAP Connection (The text box on the right SAP TAO License with Text Enabled turns Green</td></tr><tr><td height="342" align="left" valign="top" class="style1" style="font-family:Tahoma,Arial,Helvetica,sans-serif;font-size:13px;text-align:justify;color:rgb(51,51,51)"> <img src="http://www.mysaptesting.com/images/sap-tao-arch-2.jpg" width="590" height="380"></td></tr><tr><td height="342" align="left" valign="top" class="style1" style="font-family:Tahoma,Arial,Helvetica,sans-serif;font-size:13px;text-align:justify;color:rgb(51,51,51)"> <img src="http://www.mysaptesting.com/images/sap-tao-arch-3.jpg" width="590" height="366"></td></tr><tr><td height="134" align="left" valign="top" class="style1" style="font-family:Tahoma,Arial,Helvetica,sans-serif;font-size:13px;text-align:justify;color:rgb(51,51,51)"> <span class="subh1" style="font-family:'Trebuchet MS',Verdana,Arial,Helvetica,sans-serif;font-size:14px;font-weight:bold;color:rgb(10,108,206)">Connection Settings:</span><br><br>* Click on the Connect Module on the Left hand Side Panel of SAPTAO UI.<br> * Select the SAP Managed system from the list and provide valid credentials<br>* Click on "Test SAP Connection" Button and then Click on "Save" Button<br>* The ICON displaying the selected current Backend system turns Green<br> * Provide Valid QC Connection details along with <span class="GRcorrect">Domain</span> and project details and click on "Save" Button<br>* The ICON displaying the connection state of QC turns Green</td></tr><tr><td height="374" align="left" valign="top" class="style1" style="font-family:Tahoma,Arial,Helvetica,sans-serif;font-size:13px;text-align:justify;color:rgb(51,51,51)"> <img src="http://www.mysaptesting.com/images/sap-tao-arch-4.jpg" width="590" height="367"></td></tr><tr><td height="342" align="left" valign="top" class="style1" style="font-family:Tahoma,Arial,Helvetica,sans-serif;font-size:13px;text-align:justify;color:rgb(51,51,51)"> <span class="subh1" style="font-family:'Trebuchet MS',Verdana,Arial,Helvetica,sans-serif;font-size:14px;font-weight:bold;color:rgb(10,108,206)">Configuration Settings</span><br><br>Click on the Configuration Link and set the following in the respective tabs as described below.<br> <br><span class="subh1" style="font-family:'Trebuchet MS',Verdana,Arial,Helvetica,sans-serif;font-size:14px;font-weight:bold;color:rgb(10,108,206)">Inspection /UI Scanner</span><br><br>The Inspection tab page in the SAP Test Acceleration and Optimization client selects multiple SAP GUI screens and transactions for testing, in an easy-to-use interface. It then determines whether these screens are valid, and sends them to <span class="GRcorrect">SAP Quality Center</span> as screen components. <br> <br><span class="subh1" style="font-family:'Trebuchet MS',Verdana,Arial,Helvetica,sans-serif;font-size:14px;font-weight:bold;color:rgb(10,108,206)">Set up Inspection</span><br><br><span class="subh4" style="font-family:Verdana,Arial,Helvetica,sans-serif;font-size:11px;font-weight:bold">Upload components to SAP Quality Center:</span><br> <br>To upload the screen components to <span class="GRcorrect">SAP Quality Center</span> If this option is not selected, the parameters Overwrite components and Delimiter for Component/Unique Identifier on the Import/Export tab page are used to name new components<br> <br><span class="subh4" style="font-family:Verdana,Arial,Helvetica,sans-serif;font-size:11px;font-weight:bold">Component path</span><br><br>The location of components created during <span class="GRcorrect">inspection</span> <br> Duplicate components are overwritten without confirmation. <br><br><span class="subh1" style="font-family:'Trebuchet MS',Verdana,Arial,Helvetica,sans-serif;font-size:14px;font-weight:bold;color:rgb(10,108,206)">UI Scanner: </span><br> A plug-in module for HP Quickest Professional enables you to collect information from one screen at a time, and sends the screen objects to HP Quality Center as a component. The UI Scanner scans all objects <span class="GRcorrect">in</span> the screen including dynamically generated objects. The UI scanner requires an active Quick Test Professional installation on your local <span class="GRcorrect">work station</span>.<br> <br><span class="subh1" style="font-family:'Trebuchet MS',Verdana,Arial,Helvetica,sans-serif;font-size:14px;font-weight:bold;color:rgb(10,108,206)">Import/export </span><br>Import/export <span class="GRcorrect">exchanges</span> components between the SAP Test Acceleration and Optimization client and SAP Quality Center. The import/export module does the following. <br> <br>Export components from the inspector in the SAP Test Acceleration and Optimization client <span class="GRcorrect">to</span> SAP Quality Center <br>Import components from SAP Quality Center to the SAP Test Acceleration and Optimization client <br> Export components <span class="GRcorrect">from</span> the local memory to SAP Quality Center <br>Export a component from the UI scanner and send it to <span class="GRcorrect">SAP Quality Center</span>, in the background <br> <br>PFA also uses import/export while creating the test components<br><br><span class="subh4" style="font-family:Verdana,Arial,Helvetica,sans-serif;font-size:11px;font-weight:bold">Procedure</span> <br>1. Choose Import/Export tab page. <br> 2. Select the required options. <br><br><span class="subh1" style="font-family:'Trebuchet MS',Verdana,Arial,Helvetica,sans-serif;font-size:14px;font-weight:bold;color:rgb(10,108,206)">Process flow analyzer:</span><br> The process flow analyzer (PFA) records all user interactions, and the sequence of screens, in a business process, and stores them in the SAP Test Acceleration and Optimization repository. It automates inspection, retrieval of dynamic SAP GUI properties at runtime, and creation of components. <br> <br><span class="subh4" style="font-family:Verdana,Arial,Helvetica,sans-serif;font-size:11px;font-weight:bold">Procedure</span> <br>On the PFA tab page, make the following settings: <br>The PFA will create a second spreadsheet to store the recorded <span class="GRcorrect">outputs</span>. <br> Do Not Use Screen Components <br>Whether screen components are to be inserted in the test. If selected, only default components will be used. Do not select this option unless required. <br><br><span class="subh4" style="font-family:Verdana,Arial,Helvetica,sans-serif;font-size:11px;font-weight:bold">Steps <span class="GRcorrect">for</span> Process Flow analysis are:- </span><br> 1. To add a transaction, choose. <br>2. Select a transaction e.g. VA01. Name for analysis is already populated with time stamp concatenated to it. You may change it. <br>3. Choose "Start" for Process Flow Analysis.</td></tr> <tr><td height="370" align="left" valign="top" class="style1" style="font-family:Tahoma,Arial,Helvetica,sans-serif;font-size:13px;text-align:justify;color:rgb(51,51,51)"><img src="http://www.mysaptesting.com/images/sap-tao-arch-5.jpg" width="590" height="361"></td> </tr><tr><td height="247" align="left" valign="top" class="style1" style="font-family:Tahoma,Arial,Helvetica,sans-serif;font-size:13px;text-align:justify;color:rgb(51,51,51)"><img src="http://www.mysaptesting.com/images/sap-tao-arch-6.jpg" width="590" height="237"></td> </tr><tr><td height="342" align="left" valign="top" class="style1" style="font-family:Tahoma,Arial,Helvetica,sans-serif;font-size:13px;text-align:justify;color:rgb(51,51,51)">Execute the process flow as a business user. <br> 6. After executing the transaction <span class="GRcorrect">completely</span>, stop the PFA by clicking on "Stop the PFA" button in the PFA controller window. <br>7. A report is generated which captures the activities performed by <span class="GRcorrect">business user</span> <br> <br><span class="subh1" style="font-family:'Trebuchet MS',Verdana,Arial,Helvetica,sans-serif;font-size:14px;font-weight:bold;color:rgb(10,108,206)">Change analysis:</span><br>Change analysis analyzes the impact of changes due to upgrades, SAP patches, or custom development, on a test, component, or consolidated component. The impact is found by comparing the results of the technical bill of materials (TBOM), transport requests and SAP patches.<br> <br><span class="subh4" style="font-family:Verdana,Arial,Helvetica,sans-serif;font-size:11px;font-weight:bold">Set Folder for BPCA</span> <br>In this section, you specify: <br>The folder created in SAP Quality Center to store the test set created by BPCA <br> Whether to use BPCA result ID as the test set name <br>Change analyzer functionality helps in repairing tests, which are impacted by a software change. SAP Test Acceleration and Optimization relies on SAP Solution Manager – Business Process Change Analyzer (BPCA) result. The BPCA result Id could be searched on the basis of a solution or project<br> <br>Steps for Change Analysis:- <br>1. Input your result Id, and choose "Change Impact Analysis". <br><br><span class="subh1" style="font-family:'Trebuchet MS',Verdana,Arial,Helvetica,sans-serif;font-size:14px;font-weight:bold;color:rgb(10,108,206)">Repository</span> <br> The SAP Test Acceleration and Optimization repository is part of the SAP Solution Manager system, and stores data required to create, optimize and maintain components and tests. The repository contains the following:<br> User interactions and the sequence of screens in a business process <br> Information specific to SAP Test Acceleration and Optimization, that cannot be retrieved by other tools <br>Results or states during process flow analysis, before the component is created <br><br>The SAP Test Acceleration and Optimization repository tools comprise the following. <br> <br><span class="subh4" style="font-family:Verdana,Arial,Helvetica,sans-serif;font-size:11px;font-weight:bold">Component Explorer</span> <br>The user can see the list of all the components created by himself for a specified QC Domain and QC Project.<br> <br><span class="subh4" style="font-family:Verdana,Arial,Helvetica,sans-serif;font-size:11px;font-weight:bold">PFA Explorer</span> <br>The user can search for PFAs created till now, depending on search strings. The user can specify property to search on. The different properties which are possible to be searched on are:- <br> • User <br>• Analysis Name <br>• Transaction <br>• System <br>• Client <br>• Date Time <br>• Language <br><br>Once the search is done the user can click on one of the PFA to see more technical details.<br><br><span class="subh4" style="font-family:Verdana,Arial,Helvetica,sans-serif;font-size:11px;font-weight:bold">Consolidation</span><br> Consolidation creates a single component from the objects and data in an SAP Quality Center test. The component contains all the code and screen elements in a test. It executes much faster than the individual components and helps you to maintain business processes. Consolidation also takes dependent tests into account.</td> </tr></tbody></table> Software Testinghttp://www.blogger.com/profile/03753363363746376712noreply@blogger.com5tag:blogger.com,1999:blog-1578677178561645717.post-23201008401999385722013-01-04T05:09:00.000-08:002013-01-04T05:10:08.880-08:00GUI and Usability Test Scenarios<br> <div><h3 style="padding:0px;margin:1.6667em 0px 0.5556em;font-size:1.3846em;line-height:1.1111em;font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;background-color:rgb(255,255,255)"><span style="padding:0px;margin:0px;text-decoration:underline">GUI and Usability Test Scenarios</span></h3> <div><span style="padding:0px;margin:0px;text-decoration:underline"><br></span></div><p style="padding:0px;margin:0px 0px 1.5385em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;line-height:30px;background-color:rgb(255,255,255)"> 1. All fields on page (e.g. <span class="GRcorrect">text</span> box, radio options, <span class="GRcorrect">dropdown</span> lists) should be aligned properly<br style="padding:0px;margin:0px">2. Numeric values should be right justified unless specified otherwise<br style="padding:0px;margin:0px"> 3. Enough space should be provided between field labels, columns, rows, error messages etc.<br style="padding:0px;margin:0px">4. Scroll bar should be enabled only when necessary<br style="padding:0px;margin:0px">5. Font size, style and color for <span class="GRcorrect">headline</span>, description text, labels, infield data, and grid info should be standard as specified in <span class="GRcorrect">SRS</span><br style="padding:0px;margin:0px"> 6. <span class="GRcorrect">Description text box</span> should be multi-line<br style="padding:0px;margin:0px">7. Disabled fields should be grayed out and <span class="GRcorrect">user</span> should not be able to set focus on these fields<br style="padding:0px;margin:0px"> 8. Upon click <span class="GRcorrect">of</span> any input text field, <span class="GRcorrect">mouse arrow pointer</span> should get changed to cursor<br style="padding:0px;margin:0px">9. User should not be able to type in drop down <span class="GRcorrect">select</span> lists<br style="padding:0px;margin:0px"> 10. Information <span class="GRcorrect">filled</span> by users should remain intact when there is <span class="GRcorrect">error message</span> on page submit. <span class="GRcorrect">User</span> should be able to submit the form again by correcting the errors<br style="padding:0px;margin:0px"> 11. Check if proper field labels are used in error messages<br style="padding:0px;margin:0px">12. Dropdown field values should be displayed in <span class="GRcorrect">defined</span> sort order<br style="padding:0px;margin:0px"> 13. Tab and Shift+Tab order should work properly<br style="padding:0px;margin:0px">14. Default radio options should be pre-selected on page load<br style="padding:0px;margin:0px">15. Field specific and page level help messages should be available<br style="padding:0px;margin:0px"> 16. Check if correct fields are highlighted in case of errors<br style="padding:0px;margin:0px">17. Check if dropdown list options are readable and not truncated due to <span class="GRcorrect">field size limit</span><br style="padding:0px;margin:0px"> 18. All buttons on <span class="GRcorrect">page</span> should be <span class="GRcorrect">accessible</span> by keyboard shortcuts and user should be able to perform all operations using <span class="GRcorrect">keyboard</span><br style="padding:0px;margin:0px"> 19. Check all pages for broken images<br style="padding:0px;margin:0px">20. Check all pages for broken links<br style="padding:0px;margin:0px">21. All pages should have <span class="GRcorrect">title</span><br style="padding:0px;margin:0px"> 22. Confirmation messages should be displayed before performing any update or delete operation<br style="padding:0px;margin:0px">23. <span class="GRcorrect">Hour glass</span> should be displayed when application is busy<br style="padding:0px;margin:0px"> 24. Page text should be left justified<br style="padding:0px;margin:0px">25. <span class="GRcorrect">User</span> should be able to select only one radio option and any combination <span class="GRcorrect">for</span> check boxes.</p> </div> Software Testinghttp://www.blogger.com/profile/03753363363746376712noreply@blogger.com19tag:blogger.com,1999:blog-1578677178561645717.post-59351112810141371482013-01-04T05:08:00.002-08:002013-01-04T05:09:09.343-08:00General Web Testing Scenarios<h3 style="padding:0px;margin:1.6667em 0px 0.5556em;font-size:1.3846em;line-height:1.1111em;font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;background-color:rgb(255,255,255)"><span style="padding:0px;margin:0px;text-decoration:underline">General Test Scenarios</span></h3> <div><span style="padding:0px;margin:0px;text-decoration:underline"><br></span></div><p style="padding:0px;margin:0px 0px 1.5385em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;line-height:30px;background-color:rgb(255,255,255)"> 1. All mandatory fields should be validated and indicated by <span class="GRcorrect">asterisk</span> (*) symbol<br style="padding:0px;margin:0px">2. Validation error messages should be displayed properly at correct position<br style="padding:0px;margin:0px"> 3. All error messages should be displayed in same CSS style (e.g. <span class="GRcorrect">using</span> red color)<br style="padding:0px;margin:0px">4. General confirmation messages should be displayed using CSS style other than error <span class="GRcorrect">messages</span> style (e.g. <span class="GRcorrect">using</span> green color)<br style="padding:0px;margin:0px"> 5. Tool <span class="GRcorrect">tips</span> text should be meaningful<br style="padding:0px;margin:0px">6. <span class="GRcorrect">Dropdown</span> fields should have <span class="GRcorrect">first entry</span> as blank or text like 'Select'<br style="padding:0px;margin:0px"> 7. Delete functionality for any record on <span class="GRcorrect">page</span> should ask for confirmation<br style="padding:0px;margin:0px">8. Select/deselect all <span class="GRcorrect">records</span> options should be provided if page supports record add/delete/update functionality<br style="padding:0px;margin:0px"> 9. Amount values should be displayed with correct currency symbols<br style="padding:0px;margin:0px">10. Default page sorting should be provided<br style="padding:0px;margin:0px">11. Reset button functionality should set default values for all fields<br style="padding:0px;margin:0px"> 12. All numeric values should be formatted properly<br style="padding:0px;margin:0px">13. Input fields should be checked for max field value. Input values greater than <span class="GRcorrect">specified max limit</span> should not be accepted or stored in <span class="GRcorrect">database</span><br style="padding:0px;margin:0px"> 14. Check all input fields for special characters<br style="padding:0px;margin:0px">15. Field labels should be standard e.g. <span class="GRcorrect">field</span> accepting user's first name should be labeled properly as 'First Name'<br style="padding:0px;margin:0px"> 16. Check page sorting functionality after add/edit/delete operations on any record<br style="padding:0px;margin:0px">17. Check for timeout functionality. Timeout values should be configurable. Check application behavior after operation timeout<br style="padding:0px;margin:0px"> 18. Check cookies used in an application<br style="padding:0px;margin:0px">19. Check if downloadable files are pointing to correct file paths<br style="padding:0px;margin:0px">20. All resource keys should be configurable in config files or <span class="GRcorrect">database</span> instead of hard coding<br style="padding:0px;margin:0px"> 21. Standard conventions should be followed throughout for naming resource keys<br style="padding:0px;margin:0px">22. Validate markup for all web pages (validate HTML and CSS for syntax errors) to make sure it is compliant with the standards<br style="padding:0px;margin:0px"> 23. Application crash or unavailable pages should be redirected to <span class="GRcorrect">error page</span><br style="padding:0px;margin:0px">24. Check text on all pages for spelling and grammatical errors<br style="padding:0px;margin:0px"> 25. Check numeric input fields with character input values. <span class="GRcorrect">Proper validation message</span> should appear<br style="padding:0px;margin:0px">26. Check for negative numbers if allowed for numeric fields<br style="padding:0px;margin:0px"> 27. Check amount fields with decimal number values<br style="padding:0px;margin:0px">28. Check <span class="GRcorrect">functionality</span> of <span class="GRcorrect">buttons</span> available on all pages<br style="padding:0px;margin:0px"> 29. User should not be able to submit page twice by pressing submit button in quick succession.<br style="padding:0px;margin:0px">30. Divide by zero errors should be handled for any calculations<br style="padding:0px;margin:0px"> 31. Input data with first and last position blank should be handled correctly</p> Software Testinghttp://www.blogger.com/profile/03753363363746376712noreply@blogger.com3tag:blogger.com,1999:blog-1578677178561645717.post-47110055691074973722013-01-04T05:08:00.001-08:002013-01-04T05:08:25.250-08:00Cloud Testing: Issues and Challenges<span style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)">Over the past few years, Cloud has evolved as a buzz word in most of the IT industries. Testing in the cloud has greatly reduced the cost involved especially for mobile applications. Cloud manifests itself in three forms viz. Software-as-a-Service (SaaS), Platform-as-a-Service (PaaS) and Infrastructure-as-a-Service (IaaS). However, Software-as-a-Service and Infrastructure-as-a-Service has recently emerged as the most important software testing services.</span><br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"> <br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"><span style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)">Jerry Gao, Xiaoying Bai and Wei- Tek Tsai in a white paper titled "Cloud Testing – Issues, Challenges, Needs and Practice" published in Software Engineering: An International Journal highlights the major issues and challenges in cloud testing.</span><br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"> <br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"><strong style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)">1. On – Demand Test Environment Construction</strong><br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"> <span style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)">The question that often arises is how to build a testing environment for on- demand cloud testing services which is either systematic or automatic. According to Gao et al, the current cloud technology does not have any supporting solutions that will help cloud engineers build a cost effective cloud test environment.</span><br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"> <br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"><strong style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)">2. Scalability and Performance Testing</strong><br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"> <span style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)">A survey by Gao and others found that many of the published papers have discussed about </span>performance testing<span style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"> and solutions; however, they only "focus on scalability evaluation metrics and frameworks for parallel and distributed systems." The current metrics, frameworks and solutions, <span class="GRcorrect">does not support</span> the features such as dynamic scalability, cost – models and others.</span><br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"> <br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"><strong style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)">3. On – demand Testing Issues and Challenges</strong><br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"> <span style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)">Software testing services in <span class="GRcorrect">TaaS</span> should be controlled and managed by keeping in mind the on demand testing requests and this raises many issues and challenges such as identifying the test process for </span><span class="GRcorrect">TaaS</span><span style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"> which will support on-demand automated testing, or to identify the various approaches to help engineers cope with the breakdown of test cases or test scripts.</span><br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"> <br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"><strong style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)">4. <span class="GRcorrect">Regresson</span> Testing Issues and Challenges</strong><br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"> <span style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)">Software challenges and bug fixing brings in regression testing issues and challenges. The on – demand cloud testing services should address the various issues and challenges. </span> Software Testinghttp://www.blogger.com/profile/03753363363746376712noreply@blogger.com2tag:blogger.com,1999:blog-1578677178561645717.post-79278391573971769792012-12-20T05:04:00.001-08:002012-12-20T05:04:56.985-08:003 Reasons Behind Inadequate Testing of Mobile Apps<br clear="all"><div> <span style="background-color:rgb(255,255,255);font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px"><span class="GRcorrect">he</span> present century ushered in the era of mobile technology which has opened up many avenues for organizations to grow. This era also brought in various innovations. One such innovation is mobile applications that we now highly depend on for almost everything. The Strategy Analytics App Ecosystem Opportunities (AEO) forecast - Mobile Apps Revenue Forecast: 2008 – 2017 – predicts that by 2017 the mobile app <span class="GRcorrect">smartphone</span> market will generate more than $35B growing from less than $1B in 2009.</span></div> <br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"><span style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)">However, according to a recent study by Capgemini and Sogeti in conjunction with HP, two- thirds of mobile application companies are inadequately testing their apps. It was found that in organizations that conducts quality assurance on mobile apps, 64% of them focused on performance, 46% on functionality while only 18 % <span class="GRcorrect">on</span> security. "Consistent and reliable software applications have become critical to the operations of many <span class="GRcorrect">organisations</span>. Yet the lack of confidence in <span class="GRcorrect">most companies' internal abilities</span> to monitor and test the quality of their software is resounding, particularly when it comes to mobile applications," said Michel <span class="GRnoSuggestion GRcorrect">de</span> Meijer, Global Service Line Testing Lead, Capgemini Group.</span><br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"> <br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"><span style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)">Jennifer Lent on <a href="http://searchsoftwarequality.com">searchsoftwarequality.com</a> highlighted some of the reasons why many software testing organizations are not giving </span>mobile app testing <span style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)">the priority it deserves. Take a look at what she has to say.</span><br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"> <br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"><strong style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)">Testing organizations are not serious about mobile apps</strong><br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"> <br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"><span style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)">Many of the testing organizations look at mobile apps as "mini <span class="GRcorrect">smartphone</span> apps". Steve Woodward from Cloud Perspectives said that many testing organizations have a mentality that the applications should work and it wouldn't be a big problem if there are defects in the application. Testing organizations shouldn't have this type of mentality as many of the applications that are flooding the market today are designed keeping in mind the various objectives of a business organization.</span><br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"> <br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"><strong style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)">Evaluating the app performance in various <span class="GRcorrect">environment</span></strong><br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"> <span style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)">Mobile applications are expected to perform in the same way across different real world conditions.</span> Testing mobile applications<span style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"> <span class="GRcorrect">is restricted</span> only to the labs and it is impossible to replicate the various conditions mobile application users will experience in the real world informed Matt Johnston from <span class="GRcorrect">uTest</span>.</span><br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"> <br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"><strong style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)">A Low Price Tag</strong><br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"> <span style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)">With the number of mobile applications increasing day by day, there is a cut throat completion among many developers to deliver an app with a lower price tag before the deadline for the release. Thus, to bring down the cost, many may restrict testing only to the performance and functionality aspects and ignoring the need <span class="GRcorrect">to</span> security test their apps.</span> Software Testinghttp://www.blogger.com/profile/03753363363746376712noreply@blogger.com29tag:blogger.com,1999:blog-1578677178561645717.post-42752741731311623842012-12-20T05:03:00.001-08:002012-12-20T05:03:59.185-08:005 Tips to Choose the Best Automated Mobile Testing Tool<br clear="all"><div><div> <span style="background-color:rgb(255,255,255);font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px">Mobile applications have revolutionized our lives. Today, with the touch of an option, we can access any amount of information such as getting directions to a restaurant, booking our flight tickets or even order a cab service. The shift from the more traditional desktops to <span class="GRcorrect">smartphones</span> has resulted in an increase in the demand for mobile applications.</span></div> <br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"><span style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)">However; the number of <span class="GRcorrect">smartphones</span> having different features and specifications are increasing daily and this poses many </span>challenges <span style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)">to the testers. Brian MacKenzie in a blog post on <a href="http://northwaysolutions.com">northwaysolutions.com</a> highlighted some tips to help mobile app testers choose the best <span class="GRcorrect">automation</span> tools to test applications. </span><br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"> <br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"><strong style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)">1) Reusable Scripts</strong><br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"> <span style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)">Testers should ensure that the test scripts can be reused across the various devices running the same operating systems irrespective of the version. There are various solutions in the market today that claim to meet this requirement, however the reality is many of them don't although they come with tag lines such as "object based scripting" and "cross OS scripting". </span><br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"> <br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"><strong style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)">2) Support Emulators/Simulators and other Physical Devices</strong><br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"> <span style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)">Testers should be able to run and record scripts across physical devices as well as simulators and emulators.</span><br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"> <br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"><strong style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)">3) Web Application Support</strong><br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"> <span style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)">Hybrid apps, web based apps and native apps have their own advantages and disadvantages not only to the developer but also to the testers and users. Hybrid and Web Based apps are becoming popular and they are likely to replace native apps. Before selecting the tool, the tester should ensure that it <span class="GRcorrect">support</span> all types of apps.</span><br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"> <span style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"> </span><br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"> <strong style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)">4) Interruptions Shouldn't Cause the Test to Fail</strong><br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"> <span style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)">Common interruptions such as phone calls and messages shouldn't cause the test to fail. Testers should ensure that the tool doesn't get affected by the various interruptions and it should be able to resume once the interruption is over.</span><br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"> <br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"><strong style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)">5) Integration with Performance Testing Tools</strong><br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"> <span style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)">As poor application performance can affect the revenue, testers should ensure that the solution they plan to select can be integrated with <span class="GRcorrect">other performance testing tool</span>. Furthermore, the solution should be able to measure the performance of the RAM, disk, the battery and the CPU. </span></div> Software Testinghttp://www.blogger.com/profile/03753363363746376712noreply@blogger.com0tag:blogger.com,1999:blog-1578677178561645717.post-19871339036272755192012-12-20T05:01:00.001-08:002012-12-20T05:01:26.810-08:005 Skills Every Tester Should Have<br clear="all"><div><span style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)">The ever increasing complexity of applications and the need of software applications in various business organizations have changed the face </span><span style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"></span><span style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"></span><span style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"></span><span style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"></span><span style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"></span><span style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"></span><span style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"></span><span style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"></span><span style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"></span><span style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"></span><span style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"></span><span style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"></span><span style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)">of </span>software<a href="http://qa.siliconindia.com/news/The-5-Ws-of-Software-Testing-nid-128897.html?utm_source=clicktrack&utm_medium=hyperlink&utm_campaign=linkinnews" style="color:rgb(0,102,153);text-decoration:initial;font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"></a><a href="http://qa.siliconindia.com/news/The-5-Ws-of-Software-Testing-nid-128897.html?utm_source=clicktrack&utm_medium=hyperlink&utm_campaign=linkinnews" style="color:rgb(0,102,153);text-decoration:initial;font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"></a><a href="http://qa.siliconindia.com/news/The-5-Ws-of-Software-Testing-nid-128897.html?utm_source=clicktrack&utm_medium=hyperlink&utm_campaign=linkinnews" style="color:rgb(0,102,153);text-decoration:initial;font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"></a><a href="http://qa.siliconindia.com/news/The-5-Ws-of-Software-Testing-nid-128897.html?utm_source=clicktrack&utm_medium=hyperlink&utm_campaign=linkinnews" style="color:rgb(0,102,153);text-decoration:initial;font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"></a><a href="http://qa.siliconindia.com/news/The-5-Ws-of-Software-Testing-nid-128897.html?utm_source=clicktrack&utm_medium=hyperlink&utm_campaign=linkinnews" style="color:rgb(0,102,153);text-decoration:initial;font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"></a><a href="http://qa.siliconindia.com/news/The-5-Ws-of-Software-Testing-nid-128897.html?utm_source=clicktrack&utm_medium=hyperlink&utm_campaign=linkinnews" style="color:rgb(0,102,153);text-decoration:initial;font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"></a><a href="http://qa.siliconindia.com/news/The-5-Ws-of-Software-Testing-nid-128897.html?utm_source=clicktrack&utm_medium=hyperlink&utm_campaign=linkinnews" style="color:rgb(0,102,153);text-decoration:initial;font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"></a><a href="http://qa.siliconindia.com/news/The-5-Ws-of-Software-Testing-nid-128897.html?utm_source=clicktrack&utm_medium=hyperlink&utm_campaign=linkinnews" style="color:rgb(0,102,153);text-decoration:initial;font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"></a><a href="http://qa.siliconindia.com/news/The-5-Ws-of-Software-Testing-nid-128897.html?utm_source=clicktrack&utm_medium=hyperlink&utm_campaign=linkinnews" style="color:rgb(0,102,153);text-decoration:initial;font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"></a><a href="http://qa.siliconindia.com/news/The-5-Ws-of-Software-Testing-nid-128897.html?utm_source=clicktrack&utm_medium=hyperlink&utm_campaign=linkinnews" style="color:rgb(0,102,153);text-decoration:initial;font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"></a><a href="http://qa.siliconindia.com/news/The-5-Ws-of-Software-Testing-nid-128897.html?utm_source=clicktrack&utm_medium=hyperlink&utm_campaign=linkinnews" style="color:rgb(0,102,153);text-decoration:initial;font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"></a><a href="http://qa.siliconindia.com/news/The-5-Ws-of-Software-Testing-nid-128897.html?utm_source=clicktrack&utm_medium=hyperlink&utm_campaign=linkinnews" style="color:rgb(0,102,153);text-decoration:initial;font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"></a> testing<span style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)">. The users expect their applications to be not only be user friendly but also defect free and this increased the responsibility of a tester. Testers are now viewed not only as a person who is responsible to find any bugs and defects in software but they are now viewed as a person who can instill some confidence into the minds of the users.</span><br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"> <br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"><span style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)">Milind Limaye on </span><em style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"><span class="GRcorrect">beyondtesting</span></em><span style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"> highlighted some of the skills that every tester is expected to possess.</span><br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"> <br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"><strong style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)">1. Communication</strong><br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"> <span style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)">Testers are not only expected to be good listeners; however they are also expected to be good presenters as well. Testers need to communicate with the management, the users and the developers before, during and after development, </span>prepare test cases<span style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)">, test logs and present the test reports. Communication skills of a tester include his/her body language, the tone, their writing style as well as the words they use.</span><br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"> <br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"><strong style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)">2. Domain Knowledge</strong><br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"> <span style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)">Although testers are not expected to be domain experts; however they are expected to have a brief understanding about the application. This will help them identify the possible defects a user might face. According to Millind, the tester should keep the domain in mind when deciding on the priority of the bugs and defects, the test cases and the priority of the requirements. They should also be aware of the various domain complexities and the challenges.</span><br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"> <br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"><strong style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)">3. Desire to Learn</strong><br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"> <span style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)">Testers are expected to keep themselves up to date with the various technologies, approaches, tools and techniques and apply them during testing. Testers should always remember that new tools may offer then some new and exciting features which can enhance their testing capabilities.</span><br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"> <br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"><strong style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)">4. Differentiate the Defects</strong><br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"> <span style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)">Testers should have the ability to identify and differentiate the defects which need immediate attention and those that are severe. The test plan should include the various levels with regards to the priorities and severities of the bugs.</span><br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"> <br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"><strong style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)">5. Planning</strong><br style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)"> <span style="font-family:Georgia,'Times New Roman',Times,serif;font-size:15px;line-height:25px;background-color:rgb(255,255,255)">Testers must be able to plan the testing process accordingly. The test plan should include the priorities of the various test cases, the number of defects that they are targeting, as well as all the functionalities, requirements and features. A well planned test will lead to a high customer satisfaction.</span></div> Software Testinghttp://www.blogger.com/profile/03753363363746376712noreply@blogger.com0tag:blogger.com,1999:blog-1578677178561645717.post-36192984434799597272012-12-06T04:19:00.001-08:002012-12-06T04:19:59.437-08:00To Unlock the QTP Script<div><span style="font-family:Arial,Helvetica,'Nimbus Sans L',sans-serif;font-size:13px;line-height:15px;background-color:rgb(255,255,255)"><br></span></div><span style="font-family:Arial,Helvetica,'Nimbus Sans L',sans-serif;font-size:13px;line-height:15px;background-color:rgb(255,255,255)"><div> <h3 class="groups title" style="margin:0px;padding:0px;border:0px;outline:0px;font-weight:inherit;font-size:16px;vertical-align:baseline;color:rgb(51,51,51)">Is there any way in which <span class="GRcorrect">i</span> can unlock the QTP tests which are locked when QTP or QC is closed abruptly.</h3> </div><div>To unlock the QTP scripts when locked by some other user</div><div><br></div><div><span style="font-family:Arial,Helvetica,'Nimbus Sans L',sans-serif;font-size:13px;line-height:15px;background-color:rgb(255,255,255)"><br> </span></div><div><span style="font-family:Arial,Helvetica,'Nimbus Sans L',sans-serif;font-size:13px;line-height:15px;background-color:rgb(255,255,255)"><br></span></div>Set QCConnection=QCUtil<span class="GRcorrect">.</span><span class="GRcorrect">QCConnection</span> </span><br style="font-family:Arial,Helvetica,'Nimbus Sans L',sans-serif;font-size:13px;line-height:15px;background-color:rgb(255,255,255)"> <span style="font-family:Arial,Helvetica,'Nimbus Sans L',sans-serif;font-size:13px;line-height:15px;background-color:rgb(255,255,255)">Set con=QCConnection.command </span><br style="font-family:Arial,Helvetica,'Nimbus Sans L',sans-serif;font-size:13px;line-height:15px;background-color:rgb(255,255,255)"> <span style="font-family:Arial,Helvetica,'Nimbus Sans L',sans-serif;font-size:13px;line-height:15px;background-color:rgb(255,255,255)"><span class="GRcorrect">con</span><span class="GRcorrect">.</span>CommandText="DELETE FROM LOCKS WHERE LK_USER = 'USERID' " </span><br style="font-family:Arial,Helvetica,'Nimbus Sans L',sans-serif;font-size:13px;line-height:15px;background-color:rgb(255,255,255)"> <span style="font-family:Arial,Helvetica,'Nimbus Sans L',sans-serif;font-size:13px;line-height:15px;background-color:rgb(255,255,255)">Set recset=con<span class="GRcorrect">.</span>execute </span><br style="font-family:Arial,Helvetica,'Nimbus Sans L',sans-serif;font-size:13px;line-height:15px;background-color:rgb(255,255,255)"> <br style="font-family:Arial,Helvetica,'Nimbus Sans L',sans-serif;font-size:13px;line-height:15px;background-color:rgb(255,255,255)"><span style="font-family:Arial,Helvetica,'Nimbus Sans L',sans-serif;font-size:13px;line-height:15px;background-color:rgb(255,255,255)">*Mention your QC or ALM USER ID in above code</span><br> <br> Software Testinghttp://www.blogger.com/profile/03753363363746376712noreply@blogger.com0tag:blogger.com,1999:blog-1578677178561645717.post-20709927429935163202012-12-04T07:12:00.001-08:002012-12-04T07:12:27.656-08:00CATT stands 4 Computer Aided Testing Tool<p style="font-family:Verdana,Arial,Helvetica,sans-serif;font-size:11px;background-color:rgb(249,253,166)"><font>Although CATT is meant for as a testing <span class="GRcorrect">tools</span>, many SAP users <span class="GRcorrect">have now use</span> CATT frequently to upload vendors master data and make changes to other master record.</font></p> <p style="font-family:Verdana,Arial,Helvetica,sans-serif;font-size:11px;background-color:rgb(249,253,166)"><font>SAP Consultant and Abapers tends to <span class="GRcorrect">used</span> it for creating test data.</font></p> <p style="font-family:Verdana,Arial,Helvetica,sans-serif;font-size:11px;background-color:rgb(249,253,166)"><font>With CATT, you don't have to create any ABAP upload programs and this <span class="GRcorrect">save</span> on development time. However, you still have to spend time on data mapping <span class="GRcorrect">into</span> the spreadsheet format.</font></p> <p style="font-family:Verdana,Arial,Helvetica,sans-serif;font-size:11px;background-color:rgb(249,253,166)"><font>The transactions run without user interaction. You can check system <span class="GRcorrect">mesages</span> and test database changes. All tests are logged.</font></p> <p style="font-family:Verdana,Arial,Helvetica,sans-serif;font-size:11px;background-color:rgb(249,253,166)"><font>What CATT does is record you <span class="GRcorrect">performing</span> the actual transaction once.</font></p> <p style="font-family:Verdana,Arial,Helvetica,sans-serif;font-size:11px;background-color:rgb(249,253,166)"><font>You then identify the fields that you wish to change in that view.</font></p><p style="font-family:Verdana,Arial,Helvetica,sans-serif;font-size:11px;background-color:rgb(249,253,166)"> <font>Then export this data to a spreadsheet to populate with the data required.</font></p><p style="font-family:Verdana,Arial,Helvetica,sans-serif;font-size:11px;background-color:rgb(249,253,166)"><font>This is uploaded and executed saving you keying in the data manually.</font></p> <p style="font-family:Verdana,Arial,Helvetica,sans-serif;font-size:11px;background-color:rgb(249,253,166)"><font>To perform CATT, it has to be enabled in your production environment (your system administrator should be able to do this - SCC4).</font></p> <p style="font-family:Verdana,Arial,Helvetica,sans-serif;font-size:11px;background-color:rgb(249,253,166)"><font>You will also need access to your development system to create the CATT script.</font></p> Software Testinghttp://www.blogger.com/profile/03753363363746376712noreply@blogger.com0tag:blogger.com,1999:blog-1578677178561645717.post-81847818109394375322012-12-04T07:11:00.001-08:002012-12-04T07:11:26.682-08:00SAP R/3 Testing Tool:<div>SAP R/3 Testing Tool:</div><div>SAP R/3 comes with an internal recording tool known as CATT (<span class="GRcorrect">eCATT</span>). One of the advantages of CATT (<span class="GRnoSuggestion GRcorrect">eCATT</span>) is that since it is part of the standard SAP system it’s free of charge. However CATT does have some limitations which impel many companies to procure other test tools. </div> <div><br></div><div>There are many vendors offering commercial automated test tools and test management tools for testing SAP. Companies purchasing automated test tools expect and erroneously believe that the test tools will be the panacea to their entire SAP recording and testing needs. Unfortunately, this is not the case, since no two SAP implementations are exactly the same across two or more companies or at times even within different divisions of the same company. Consequently, a company implementing SAP might need to procure test tools from more than one vendor in addition to the CATT (<span class="GRnoSuggestion GRcorrect">eCATT</span>) tool. </div> <div><br></div><div>An SAP implementation could be implementing SAP add-ons such as BW (Business Warehouse), APO (Advanced Planning Optimization), SEM (Strategic Enterprise Management) or even modules such as PS (Project Systems) that generate graphs and charts that a recording tool does not recognize. Furthermore, a company may move its SAP GUI from the desktop (fat client) to running SAP as web-based (thin client) or through an emulated Citrix session which could render the existing test tools useless. </div> <div><br></div><div>Companies that wish to move to an automated testing strategy should articulate and document what SAP modules and SAP add-ons they <span class="GRcorrect">areinstalling</span> in addition to any legacy applications integrating with SAP. This information should be provided to the vendors of automated test tools in order to determine what can actually be recorded and tested with the test tools. The company should further investigate with the vendor what additional benefits over CATT (<span class="GRnoSuggestion GRcorrect">eCATT</span>) the automated test tools provide. The objective is to get the test tools that will maximize SAP recording.</div> <div><br></div><div><br></div><div><br></div><div><br></div> Software Testinghttp://www.blogger.com/profile/03753363363746376712noreply@blogger.com0tag:blogger.com,1999:blog-1578677178561645717.post-3804938586574761382012-11-30T07:15:00.001-08:002012-11-30T07:15:38.624-08:00Top 10 Signs You’re Not Ready To Be A Security Tester<h2 style="margin:0px;padding:0px 0px 0px 1px;font-size:23px;clear:both;color:rgb(77,77,77);font-family:arial,helvetica,sans-serif;background-color:rgb(255,255,255)"><a href="http://blog.utest.com/top-10-signs-youre-not-ready-to-be-a-security-tester/2012/11/" rel="bookmark" style="text-decoration:initial;color:rgb(0,168,204)">Top 10 Signs You're Not Ready To Be A Security Tester</a></h2> <div><br></div><div><p style="margin:0px;padding:10px 0px 5px;color:rgb(77,77,77);font-family:arial,helvetica,sans-serif;font-size:12px;line-height:22px;background-color:rgb(255,255,255)">Becoming a security tester can be tough. It requires deep training and expertise in system architecture, computer engineering, network theory, and human psychology. Learning these skills can take considerable time, and it may take years for a tester to truly become a security master.</p> <p style="margin:0px;padding:10px 0px 5px;color:rgb(77,77,77);font-family:arial,helvetica,sans-serif;font-size:12px;line-height:22px;background-color:rgb(255,255,255)">If you are learning to be a security <span class="GRcorrect">testers</span>, here are 10 signs you're not quite ready for the job:</p> <p style="margin:0px;padding:10px 0px 5px;color:rgb(77,77,77);font-family:arial,helvetica,sans-serif;font-size:12px;line-height:22px;background-color:rgb(255,255,255)">10. Your password appears on <a href="http://www.cnn.com/2012/10/25/tech/web/worst-passwords-2012/index.html" style="color:rgb(0,168,204)">this list</a>.</p> <p style="margin:0px;padding:10px 0px 5px;color:rgb(77,77,77);font-family:arial,helvetica,sans-serif;font-size:12px;line-height:22px;background-color:rgb(255,255,255)">9. Your concept of <a href="http://en.wikipedia.org/wiki/Social_engineering_%28security%29" style="color:rgb(0,168,204)">social engineering</a> is to throw a really great party and then figure out how each person can have the best possible time.</p> <p style="margin:0px;padding:10px 0px 5px;color:rgb(77,77,77);font-family:arial,helvetica,sans-serif;font-size:12px;line-height:22px;background-color:rgb(255,255,255)">8. You think 56 bit <a href="http://en.wikipedia.org/wiki/Data_Encryption_Standard" style="color:rgb(0,168,204)">DES</a> ought to be good enough for anyone.</p> <p style="margin:0px;padding:10px 0px 5px;color:rgb(77,77,77);font-family:arial,helvetica,sans-serif;font-size:12px;line-height:22px;background-color:rgb(255,255,255)">7. You can't remember if your doctor gave you a <a href="http://en.wikipedia.org/wiki/Sql_injection" style="color:rgb(0,168,204)">SQL injection</a> with your last set of vaccinations.</p> <p style="margin:0px;padding:10px 0px 5px;color:rgb(77,77,77);font-family:arial,helvetica,sans-serif;font-size:12px;line-height:22px;background-color:rgb(255,255,255)">6. You think <a href="http://en.wikipedia.org/wiki/Van_Eck_Phreaking" style="color:rgb(0,168,204)">Van Eck phreaking</a> is the title of Armin Van Buuren's latest album.</p> <p style="margin:0px;padding:10px 0px 5px;color:rgb(77,77,77);font-family:arial,helvetica,sans-serif;font-size:12px;line-height:22px;background-color:rgb(255,255,255)">5. You start looking for a mop when you hear someone mention a <a href="http://en.wikipedia.org/wiki/Buffer_overflow" style="color:rgb(0,168,204)">buffer overflow</a>.</p> <p style="margin:0px;padding:10px 0px 5px;color:rgb(77,77,77);font-family:arial,helvetica,sans-serif;font-size:12px;line-height:22px;background-color:rgb(255,255,255)">4. You think <a href="http://en.wikipedia.org/wiki/Phishing" style="color:rgb(0,168,204)"><span class="GRcorrect">phishing</span></a> means getting stoned and going to a concert <span class="GRcorrect">by</span> that <a href="http://en.wikipedia.org/wiki/Phish" style="color:rgb(0,168,204)">band from Vermont</a>.</p> <p style="margin:0px;padding:10px 0px 5px;color:rgb(77,77,77);font-family:arial,helvetica,sans-serif;font-size:12px;line-height:22px;background-color:rgb(255,255,255)">3. When you hear <a href="http://en.wikipedia.org/wiki/OWASP" style="color:rgb(0,168,204)">OWASP</a>, you reach for a can of bug spray.</p> <p style="margin:0px;padding:10px 0px 5px;color:rgb(77,77,77);font-family:arial,helvetica,sans-serif;font-size:12px;line-height:22px;background-color:rgb(255,255,255)">2. You think that <a href="http://en.wikipedia.org/wiki/Cross_site_scripting" style="color:rgb(0,168,204)">cross-site scripting</a> is a fancy form of calligraphy.</p> <p style="margin:0px;padding:10px 0px 5px;color:rgb(77,77,77);font-family:arial,helvetica,sans-serif;font-size:12px;line-height:22px;background-color:rgb(255,255,255)">1. You worry that if the <a href="http://en.wikipedia.org/wiki/Private_key" style="color:rgb(0,168,204)">private key</a> doesn't open up a little more, it will never be accepted by its friends and public_key will always be the popular one.</p> </div> Software Testinghttp://www.blogger.com/profile/03753363363746376712noreply@blogger.com0tag:blogger.com,1999:blog-1578677178561645717.post-56835618504901589272012-11-30T07:11:00.001-08:002012-11-30T07:11:47.015-08:00Mobile Testing<p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;background-color:rgb(255,255,255);color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;line-height:21px">Today's Mobile Applications deliver complex functionality on platforms having limited resources for computing. The Mobile environment comprises of plethora of devices with diverse hardware & software configurations. This diversity in Mobile computing environment presents unique challenges in quality assurance thus requiring unique testing strategies.</p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;background-color:rgb(255,255,255);color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;line-height:21px"><strong style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;background-color:transparent;background-repeat:initial initial"><span style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;background-color:transparent;text-decoration:underline;background-repeat:initial initial">Challenges in Mobile Testing:</span></strong></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;background-color:rgb(255,255,255);color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;line-height:21px">The challenges in Mobile testing arise from the diversity of device environment, hardware & networking considerations and methodologies of application development. The prime challenges are:</p> <ul style="margin:0px 0px 1.5em;padding:0px 0px 0px 30px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;background-color:rgb(255,255,255);list-style:none;color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;line-height:21px"> <li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;background-color:transparent;list-style-type:disc;background-repeat:initial initial">Device Environment – There are almost 100 types of devices available in market with more than 40 Mobile browsers running on several operating systems. Rendering images, positioning of elements on screen, application runtime etc are just few of the areas one need to test across devices.</li> <li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;background-color:transparent;list-style-type:disc;background-repeat:initial initial">Hardware & Network – Limitations in processing speed, Memory size of mobile devices, protocols used to communicate with outer world, network latency, gateways etc are the major challenges from a hardware & network perspective for Mobile testing.</li> <li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;background-color:transparent;list-style-type:disc;background-repeat:initial initial">Scripts – This challenge arises from the choice of manual or automation testing scripts. Because of several different user interfaces working on several devices the script has to be build accordingly.</li> </ul><p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;background-color:rgb(255,255,255);color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;line-height:21px"> <strong style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;background-color:transparent;background-repeat:initial initial"><span style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;background-color:transparent;text-decoration:underline;background-repeat:initial initial">Critical Factors:</span></strong></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;background-color:rgb(255,255,255);color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;line-height:21px">The critical factors that determine the success of any Mobile Testing project are:</p> <ul style="margin:0px 0px 1.5em;padding:0px 0px 0px 30px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;background-color:rgb(255,255,255);list-style:none;color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;line-height:21px"> <li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;background-color:transparent;list-style-type:disc;background-repeat:initial initial">Mobile Environment testing</li><li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;background-color:transparent;list-style-type:disc;background-repeat:initial initial"> Application complexity testing</li><li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;background-color:transparent;list-style-type:disc;background-repeat:initial initial">Use of emulators & actual devices</li> <li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;background-color:transparent;list-style-type:disc;background-repeat:initial initial">Use of test automation</li></ul><p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;background-color:rgb(255,255,255);color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;line-height:21px"> <strong style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;background-color:transparent;background-repeat:initial initial"><span style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;background-color:transparent;text-decoration:underline;background-repeat:initial initial">Mobile Testing Features:</span></strong></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;background-color:rgb(255,255,255);color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;line-height:21px">The major features of Mobile Testing are:</p> <ul style="margin:0px 0px 1.5em;padding:0px 0px 0px 30px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;background-color:rgb(255,255,255);list-style:none;color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;line-height:21px"> <li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;background-color:transparent;list-style-type:disc;background-repeat:initial initial"><strong style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;background-color:transparent;background-repeat:initial initial">Functional Testing</strong> – Under functional testing the tests which are performed are Installation testing, System testing, Mobile Web content testing & Usability Testing. Security Testing is also done for Input Validation Checks & Authentication Checks.</li> <li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;background-color:transparent;list-style-type:disc;background-repeat:initial initial"><strong style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;background-color:transparent;background-repeat:initial initial">Performance Testing</strong> – Under performance testing the focus is on Test application responsiveness to user events, measure server response time in case of API calls, simulate multiple use request to perform load test & bandwidth choking to simulate mobile network speed.</li> <li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;background-color:transparent;list-style-type:disc;background-repeat:initial initial"><strong style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;background-color:transparent;background-repeat:initial initial">Usability & Compatibility Testing</strong> – This testing is done to understand how people interact with the platform, observe how the mass market use, avg. time taken for a use case, ease of use and recall, compliance against mobile usability standards, mobile browser compatibility test & multi-device compatibility check for OS, resolution, device level features etc</li> <li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;background-color:transparent;list-style-type:disc;background-repeat:initial initial"><strong style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;background-color:transparent;background-repeat:initial initial">Network Testing</strong> – In network testing, we test the application using multiple carriers, on different modes of connectivity, perform memory profiling, battery usage test for high data volume apps etc</li> </ul><p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;background-color:rgb(255,255,255);color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;line-height:21px"> <strong style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;background-color:transparent;background-repeat:initial initial"><span style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;background-color:transparent;text-decoration:underline;background-repeat:initial initial">Test Automation tools:</span></strong></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;background-color:rgb(255,255,255);color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;line-height:21px">For building automation test scripts various tools are available in market (Open source as well as Commercial). Below is a sample list of the tools available:</p> <table border="1" cellspacing="0" cellpadding="0" style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;background-color:rgb(255,255,255);border-collapse:collapse;border-spacing:0px;color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;line-height:21px;text-align:start"> <tbody style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;background-color:transparent;background-repeat:initial initial"><tr style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;background-color:transparent;background-repeat:initial initial"> <td valign="top" width="85" style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;background-color:transparent;background-repeat:initial initial"><strong style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;background-color:transparent;background-repeat:initial initial">Unit Testing</strong></td> <td valign="top" width="265" style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;background-color:transparent;background-repeat:initial initial"><strong style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;background-color:transparent;background-repeat:initial initial">System Testing (Open source)</strong></td> <td valign="top" width="231" style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;background-color:transparent;background-repeat:initial initial"><strong style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;background-color:transparent;background-repeat:initial initial">System Testing (Commercial)</strong></td> </tr><tr style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;background-color:transparent;background-repeat:initial initial"><td valign="top" width="85" style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;background-color:transparent;background-repeat:initial initial"> jUnit</td><td valign="top" width="265" style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;background-color:transparent;background-repeat:initial initial">Robotium</td><td valign="top" width="231" style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;background-color:transparent;background-repeat:initial initial"> M-euxTest</td></tr><tr style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;background-color:transparent;background-repeat:initial initial"><td valign="top" width="85" style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;background-color:transparent;background-repeat:initial initial"> Roboelectric</td><td valign="top" width="265" style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;background-color:transparent;background-repeat:initial initial">Selenium</td><td valign="top" width="231" style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;background-color:transparent;background-repeat:initial initial"> DeviceAnywhere</td></tr><tr style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;background-color:transparent;background-repeat:initial initial"><td valign="top" width="85" style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;background-color:transparent;background-repeat:initial initial"> jMock</td><td valign="top" width="265" style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;background-color:transparent;background-repeat:initial initial">MonkeyRunner</td><td valign="top" width="231" style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;background-color:transparent;background-repeat:initial initial"> Perfecto Mobile</td></tr></tbody></table> Software Testinghttp://www.blogger.com/profile/03753363363746376712noreply@blogger.com4tag:blogger.com,1999:blog-1578677178561645717.post-17493863655577044862012-11-30T07:07:00.000-08:002012-11-30T07:08:03.791-08:00Advantages of Agile Methodology<p style="margin:15px 0px;padding:0px;border:0px;outline:0px;font-size:12px;background-color:rgb(255,255,255);color:rgb(69,69,69);font-family:Arial,Verdana,Tahoma,sans-serif;line-height:18px">Agile as the name refers implies something to do very quickly. Hence Agile Testing refers to validate the client requirements as soon as possible and make it customer friendly. Agile development methodology is a conceptual framework for undertaking any software engineering projects. There are a number of agile software <span class="GRcorrect">development methods but</span> the most popular agile methods are Extreme Programming (XP) and Scrum.</p> <p style="margin:15px 0px;padding:0px;border:0px;outline:0px;font-size:12px;background-color:rgb(255,255,255);color:rgb(69,69,69);font-family:Arial,Verdana,Tahoma,sans-serif;line-height:18px">In general agile methods attempt to minimize risk and maximize productivity by developing software in short iterations and deemphasizing work on interim work artifacts and it is people oriented. Here are some of the key characteristics of the agile methodology:</p> <ul style="margin:15px 0px;padding:0px;border:0px;outline:0px;font-size:12px;background-color:rgb(255,255,255);list-style:none;color:rgb(69,69,69);font-family:Arial,Verdana,Tahoma,sans-serif;line-height:18px"><li style="margin:0px 0px 5px;padding:0px 0px 0px 25px;border:0px;outline:0px;font-size:12px;background-image:url(http://www.360logica.com/templates/ja_halite/images/bullet.gif);line-height:1.3;overflow:hidden;background-repeat:no-repeat no-repeat"> Deliver frequently.</li><li style="margin:0px 0px 5px;padding:0px 0px 0px 25px;border:0px;outline:0px;font-size:12px;background-image:url(http://www.360logica.com/templates/ja_halite/images/bullet.gif);line-height:1.3;overflow:hidden;background-repeat:no-repeat no-repeat"> More iteration.</li><li style="margin:0px 0px 5px;padding:0px 0px 0px 25px;border:0px;outline:0px;font-size:12px;background-image:url(http://www.360logica.com/templates/ja_halite/images/bullet.gif);line-height:1.3;overflow:hidden;background-repeat:no-repeat no-repeat"> Less defects.</li><li style="margin:0px 0px 5px;padding:0px 0px 0px 25px;border:0px;outline:0px;font-size:12px;background-image:url(http://www.360logica.com/templates/ja_halite/images/bullet.gif);line-height:1.3;overflow:hidden;background-repeat:no-repeat no-repeat"> Test frequently.</li><li style="margin:0px 0px 5px;padding:0px 0px 0px 25px;border:0px;outline:0px;font-size:12px;background-image:url(http://www.360logica.com/templates/ja_halite/images/bullet.gif);line-height:1.3;overflow:hidden;background-repeat:no-repeat no-repeat"> Collaborative approach.</li><li style="margin:0px 0px 5px;padding:0px 0px 0px 25px;border:0px;outline:0px;font-size:12px;background-image:url(http://www.360logica.com/templates/ja_halite/images/bullet.gif);line-height:1.3;overflow:hidden;background-repeat:no-repeat no-repeat"> Maximum ROI.</li></ul><p style="margin:15px 0px;padding:0px;border:0px;outline:0px;font-size:12px;background-color:rgb(255,255,255);color:rgb(69,69,69);font-family:Arial,Verdana,Tahoma,sans-serif;line-height:18px"><strong style="margin:0px;padding:0px;border:0px;outline:0px;font-size:12px;background-color:transparent;background-repeat:initial initial">Top reasons for adopting Agile Methodology:</strong></p> <ul style="margin:15px 0px;padding:0px;border:0px;outline:0px;font-size:12px;background-color:rgb(255,255,255);list-style:none;color:rgb(69,69,69);font-family:Arial,Verdana,Tahoma,sans-serif;line-height:18px"><li style="margin:0px 0px 5px;padding:0px 0px 0px 25px;border:0px;outline:0px;font-size:12px;background-image:url(http://www.360logica.com/templates/ja_halite/images/bullet.gif);line-height:1.3;overflow:hidden;background-repeat:no-repeat no-repeat"> <strong style="margin:0px;padding:0px;border:0px;outline:0px;font-size:12px;background-color:transparent;background-repeat:initial initial">Iterative and incremental delivery: </strong>Project delivery is divided into small functional releases or increments to manage risk and to get early feedback from customers and end users. These small releases are delivered on a schedule using iterations that typically last between one and four weeks each.</li> <li style="margin:0px 0px 5px;padding:0px 0px 0px 25px;border:0px;outline:0px;font-size:12px;background-image:url(http://www.360logica.com/templates/ja_halite/images/bullet.gif);line-height:1.3;overflow:hidden;background-repeat:no-repeat no-repeat"> <strong style="margin:0px;padding:0px;border:0px;outline:0px;font-size:12px;background-color:transparent;background-repeat:initial initial">Collaboration: </strong>All core project team members including an on-site customer are co-located in a shared, open area to facilitate face-to-communication and conduct interactions.</li> <li style="margin:0px 0px 5px;padding:0px 0px 0px 25px;border:0px;outline:0px;font-size:12px;background-image:url(http://www.360logica.com/templates/ja_halite/images/bullet.gif);line-height:1.3;overflow:hidden;background-repeat:no-repeat no-repeat"> <strong style="margin:0px;padding:0px;border:0px;outline:0px;font-size:12px;background-color:transparent;background-repeat:initial initial">Continuous Improvement: </strong>Practices that enable delivery process inspection and adaptation are integrated into agile methods. Project Reflections are meetings conducted while the project is underway to facilitate regular reflection on its successes and failures, and any of the tools and techniques applied.</li> </ul> Software Testinghttp://www.blogger.com/profile/03753363363746376712noreply@blogger.com0tag:blogger.com,1999:blog-1578677178561645717.post-74136211591136794272012-11-30T06:57:00.001-08:002012-11-30T06:57:31.588-08:00ETL Testing / Data Warehouse Testing – Tips, Techniques, Process and Challenges<br clear="all"><div> <span style="background-color:rgb(255,255,255);color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;line-height:30px">ETL testing (Extract, Transform, and Load). This article will present you with a complete idea about ETL testing and what we do to test ETL process.</span></div> <p style="padding:0px;margin:0px 0px 1.5385em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;line-height:30px;background-color:rgb(255,255,255)">It has been observed that Independent Verification and Validation is gaining huge market potential and many companies are now seeing this as <span class="GRcorrect">prospective business gain</span>. Customers have been offered <span class="GRcorrect">different range</span> of products in terms of service offerings, distributed in many areas based on technology, process and solutions. ETL or data warehouse is one of the offerings which are developing rapidly and successfully.</p> <p style="padding:0px;margin:0px 0px 1.5385em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;line-height:30px;background-color:rgb(255,255,255)"><span id="more-980" style="padding:0px;margin:0px"></span></p> <p style="padding:0px;margin:0px 0px 1.5385em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;line-height:30px;background-color:rgb(255,255,255)"><img class="alignnone wp-image-982" title="ETL testing" src="http://www.softwaretestinghelp.com/wp-content/qa/uploads/2012/05/ETL-testing.jpg" alt="ETL testing" width="393" height="244" style="padding: 0px; margin: 0px; border: none;"></p> <p style="padding:0px;margin:0px 0px 1.5385em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;line-height:30px;background-color:rgb(255,255,255)"><strong style="padding:0px;margin:0px">Why do organizations <span class="GRcorrect">need Data Warehouse</span>?</strong><br style="padding:0px;margin:0px"> Organizations with organized IT practices are looking forward to create a next level of technology transformation. They are now trying to make themselves much more operational with easy-to-<span class="GRcorrect">interoperate</span> data. Having said that data is most important part of any organization, it may be everyday data or historical data. Data is <span class="GRcorrect">backbone</span> of any report and reports are the baseline on which all the vital management decisions are taken.</p> <p style="padding:0px;margin:0px 0px 1.5385em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;line-height:30px;background-color:rgb(255,255,255)">Most of the companies are taking a step forward for constructing their data warehouse to store and monitor real time data as well as historical data. Crafting an efficient data warehouse is not an easy job. Many organizations have distributed departments with different applications running on distributed technology. ETL tool is employed in order to make a flawless integration between different data sources from different departments. ETL tool will work as an <span class="GRcorrect">integrator</span>, extracting data from different sources; transforming it in preferred format based on the business transformation rules and loading it in cohesive DB known are Data Warehouse.</p> <p style="padding:0px;margin:0px 0px 1.5385em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;line-height:30px;background-color:rgb(255,255,255)">Well planned, well defined and effective testing scope guarantees smooth conversion of the project to the production. A business gains the real buoyancy once the ETL processes are verified and validated by <span class="GRcorrect">independent group</span> of experts to make sure that <span class="GRcorrect">data warehouse</span> is concrete and robust.</p> <p style="padding:0px;margin:0px 0px 1.5385em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;line-height:30px;background-color:rgb(255,255,255)"><strong style="padding:0px;margin:0px">ETL or Data warehouse testing is categorized into four different engagements</strong> irrespective of technology or ETL tools used:</p> <ul style="padding:0px;margin:0px 0px 1.5385em 3em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;line-height:30px;background-color:rgb(255,255,255)"><li style="padding:0px;margin:0px"><strong style="padding:0px;margin:0px">New Data Warehouse Testing</strong> – New DW is built and verified from scratch. Data input is taken from customer requirements and different data sources and new data warehouse <span class="GRcorrect">is build</span> and verified with the help of ETL tools.</li> <li style="padding:0px;margin:0px"><strong style="padding:0px;margin:0px">Migration Testing</strong> – In this type of project customer will have an existing DW and ETL <span class="GRcorrect">performing</span> the job but they are looking to bag new tool in order to improve efficiency.</li> <li style="padding:0px;margin:0px"><strong style="padding:0px;margin:0px">Change Request</strong> – In this type of project new data is added from different sources to an existing DW. Also, there might be a condition where <span class="GRcorrect">customer</span> needs to change their existing business rule or they might integrate the new rule.</li> <li style="padding:0px;margin:0px"><strong style="padding:0px;margin:0px">Report Testing</strong> – Report are the end result of any Data Warehouse and the basic <span class="GRcorrect">propose</span> for which DW <span class="GRcorrect">is build</span>. <span class="GRcorrect">Report</span> must be tested by validating layout, data in the report and calculation.</li> </ul><h3 style="padding:0px;margin:1.6667em 0px 0.5556em;font-size:1.3846em;line-height:1.1111em;font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;background-color:rgb(255,255,255)"><strong style="padding:0px;margin:0px">ETL Testing Techniques:</strong></h3> <p style="padding:0px;margin:0px 0px 1.5385em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;line-height:30px;background-color:rgb(255,255,255)">1) Verify that data is transformed correctly according to various business requirements and rules.<br style="padding:0px;margin:0px"> 2) Make sure that all projected data is loaded into the data warehouse without any data loss and truncation.<br style="padding:0px;margin:0px">3) Make sure that ETL application appropriately rejects, replaces with default values and reports invalid data.<br style="padding:0px;margin:0px"> 4) Make sure that data is loaded <span class="GRcorrect">in</span> <span class="GRcorrect">data warehouse</span> within prescribed and expected time frames to confirm improved performance and scalability.</p><p style="padding:0px;margin:0px 0px 1.5385em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;line-height:30px;background-color:rgb(255,255,255)"> Apart from these 4 main ETL testing methods other testing methods like integration testing and user acceptance testing is also carried out to make sure everything is smooth and reliable.</p><h3 style="padding:0px;margin:1.6667em 0px 0.5556em;font-size:1.3846em;line-height:1.1111em;font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;background-color:rgb(255,255,255)"> <strong style="padding:0px;margin:0px">ETL Testing Process:</strong></h3><p style="padding:0px;margin:0px 0px 1.5385em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;line-height:30px;background-color:rgb(255,255,255)"> Similar to any other testing that lies under Independent Verification and Validation, ETL also go through the same phase.</p><ul style="padding:0px;margin:0px 0px 1.5385em 3em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;line-height:30px;background-color:rgb(255,255,255)"> <li style="padding:0px;margin:0px">Business and requirement understanding</li><li style="padding:0px;margin:0px">Validating</li><li style="padding:0px;margin:0px">Test Estimation</li><li style="padding:0px;margin:0px">Test planning based on the inputs from test estimation and business requirement</li> <li style="padding:0px;margin:0px">Designing test cases and test scenarios from all the available inputs</li><li style="padding:0px;margin:0px">Once all the test cases are ready and are approved, testing team <span class="GRcorrect">proceed</span> to perform pre-execution check and test data preparation for testing</li> <li style="padding:0px;margin:0px">Lastly execution is performed till exit criteria are met</li><li style="padding:0px;margin:0px">Upon successful completion summary report is prepared and closure process is done.</li></ul> <p style="padding:0px;margin:0px 0px 1.5385em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;line-height:30px;background-color:rgb(255,255,255)">It is necessary to define <span class="GRcorrect">test strategy</span> which should be mutually accepted by stakeholders before starting actual testing. A well defined test strategy will make sure that correct approach has been followed meeting the testing aspiration. ETL testing might require writing SQL statements extensively by testing team or may be tailoring the SQL provided by <span class="GRcorrect">development team</span>. In any case testing team must be aware of the results they are trying to get <span class="GRcorrect">using</span> those SQL statements.</p> <p style="padding:0px;margin:0px 0px 1.5385em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;line-height:30px;background-color:rgb(255,255,255)"><strong style="padding:0px;margin:0px"><span class="GRcorrect">Difference</span> between Database and Data Warehouse Testing</strong><br style="padding:0px;margin:0px"> There is a popular misunderstanding that database testing and <span class="GRcorrect">data warehouse</span> is similar while the fact is that both hold <span class="GRcorrect">different direction</span> in testing.</p><ul style="padding:0px;margin:0px 0px 1.5385em 3em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;line-height:30px;background-color:rgb(255,255,255)"> <li style="padding:0px;margin:0px"> Database testing is done using smaller scale of data normally with OLTP (Online transaction processing) type of databases while data warehouse testing is done with large volume with data involving OLAP (online analytical processing) databases.</li> <li style="padding:0px;margin:0px"> In database testing normally data <span class="GRcorrect">is consistently injected</span> from uniform sources while in data warehouse testing most of the data comes from different kind of data sources which are sequentially inconsistent.</li> <li style="padding:0px;margin:0px">We generally perform only CRUD (Create, read, update and delete) operation in database testing while in data warehouse testing we use read-only (Select) operation.</li><li style="padding:0px;margin:0px"> Normalized databases are used in DB testing while demoralized DB is used in data warehouse testing.</li></ul><p style="padding:0px;margin:0px 0px 1.5385em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;line-height:30px;background-color:rgb(255,255,255)"> There are <span class="GRcorrect">number</span> of universal verifications that have to be carried out for any kind of data warehouse testing. Below is the list of objects that are treated as essential for validation in ETL testing:<br style="padding:0px;margin:0px"> - Verify that data transformation from source to destination works as expected<br style="padding:0px;margin:0px">- Verify that <span class="GRcorrect">expected data</span> is added <span class="GRcorrect">in</span> <span class="GRcorrect">target system</span><br style="padding:0px;margin:0px"> - Verify that all DB fields and field data is loaded without any truncation<br style="padding:0px;margin:0px">- Verify data checksum for <span class="GRcorrect">record count match</span><br style="padding:0px;margin:0px"> - Verify that for <span class="GRcorrect">rejected</span> data proper error logs are generated with all details<br style="padding:0px;margin:0px">- Verify NULL value fields<br style="padding:0px;margin:0px">- Verify that duplicate data is not loaded<br style="padding:0px;margin:0px"> - Verify data integrity</p><h3 style="padding:0px;margin:1.6667em 0px 0.5556em;font-size:1.3846em;line-height:1.1111em;font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;background-color:rgb(255,255,255)"><strong style="padding:0px;margin:0px">ETL Testing Challenges:</strong></h3> <p style="padding:0px;margin:0px 0px 1.5385em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;line-height:30px;background-color:rgb(255,255,255)">ETL testing is quite different from conventional testing. There are many challenges we faced while performing data warehouse testing. Here is the list of few ETL testing challenges I experienced on my project:<br style="padding:0px;margin:0px"> - Incompatible and duplicate data.<br style="padding:0px;margin:0px">- Loss of data during ETL process.<br style="padding:0px;margin:0px">- Unavailability of inclusive test bed.<br style="padding:0px;margin:0px">- Testers have no privileges to execute ETL jobs by their own.<br style="padding:0px;margin:0px"> - Volume and complexity of data is very huge.<br style="padding:0px;margin:0px">- Fault in business process and procedures.<br style="padding:0px;margin:0px">- Trouble acquiring and building test data.<br style="padding:0px;margin:0px"> - Missing business flow information.</p><p style="padding:0px;margin:0px 0px 1.5385em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;line-height:30px;background-color:rgb(255,255,255)">Data is important for businesses to make the critical business decisions. ETL testing plays a significant <span class="GRcorrect">role validating</span> and ensuring that the business information is exact, consistent and reliable. Also, it minimizes <span class="GRcorrect">hazard</span> of data loss in production.</p> <p style="padding:0px;margin:0px 0px 1.5385em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;line-height:30px;background-color:rgb(255,255,255)">Tags:</p><p style="padding:0px;margin:0px 0px 1.5385em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;line-height:30px;background-color:rgb(255,255,255)"> </p><p class="MsoNormal"><span class="GRcorrect">etl</span> testing</p> <p class="MsoNormal"><span class="GRcorrect">etl</span> testing tutorial</p> <p class="MsoNormal"><span class="GRcorrect">etl</span> testing interview <span class="GRcorrect">questions</span></p> <p class="MsoNormal"><span class="GRcorrect">etl</span> testing concepts</p> <p class="MsoNormal"><span class="GRcorrect">etl</span> testing process</p> <p class="MsoNormal"><span class="GRcorrect">etl</span> testing approach</p> <p class="MsoNormal"><span class="GRcorrect">etl</span> testing methodology</p> <p class="MsoNormal"><span class="GRcorrect">etl</span> testing tools</p> <p class="MsoNormal"><span class="GRcorrect">etl</span> testing jobs</p> <p class="MsoNormal"><span class="GRcorrect">ew</span> questions and answers pdf</p> <p class="MsoNormal"><span class="GRcorrect">sql</span> interview questions</p> <p class="MsoNormal"><span class="GRcorrect">etl</span> testing concepts</p> <p class="MsoNormal"><span class="GRcorrect">etl</span> testing tutorial</p> <p class="MsoNormal"><span class="GRcorrect">etl</span> testing process</p> <p class="MsoNormal"><span class="GRcorrect">etl</span> testing tools</p> <p class="MsoNormal"><span class="GRcorrect">etl</span> testing concepts pdf</p> <p class="MsoNormal"><span class="GRcorrect">etl</span> testing pdf</p> <p class="MsoNormal"><span class="GRcorrect">etl</span> testing concepts pdf</p> <p class="MsoNormal"><span class="GRcorrect">etl</span> testing concepts <span class="GRcorrect">ppt</span></p> <p class="MsoNormal"><span class="GRcorrect">etl</span> testing interview <span class="GRcorrect">questions</span></p> <p class="MsoNormal"><span class="GRcorrect">etl</span> testing tutorial</p> <p class="MsoNormal"><span class="GRcorrect">what</span> is <span class="GRnoSuggestion GRcorrect">etl</span> testing</p> <p class="MsoNormal"><span class="GRcorrect">etl</span> testing basics</p> <p class="MsoNormal"><span class="GRcorrect">etl</span> testing process</p> <p class="MsoNormal"><span class="GRcorrect">etl</span> testing tools</p> <p class="MsoNormal"><span class="GRcorrect">data</span> warehousing testing</p> <p class="MsoNormal"><span class="GRcorrect">data</span> warehousing testing pdf</p> <p class="MsoNormal"><span class="GRcorrect">data</span> warehousing testing <span class="GRcorrect">interview</span> questions</p> <p class="MsoNormal"><span class="GRcorrect">data</span> warehousing testing jobs</p> <p class="MsoNormal"><span class="GRcorrect">data</span> warehousing testing <span class="GRcorrect">interview</span> questions and answers</p> <p class="MsoNormal"><span class="GRcorrect">data</span> warehousing testing <span class="GRcorrect">ppt</span></p> <p class="MsoNormal"><span class="GRcorrect">data</span> warehousing testing <span class="GRcorrect">training</span></p> <p class="MsoNormal"><span class="GRcorrect">data</span> warehousing testing life <span class="GRcorrect">cycle</span></p> <p class="MsoNormal"><span class="GRcorrect">data</span> warehousing testing questions</p> <p class="MsoNormal"><span class="GRcorrect">data</span> warehousing interview <span class="GRcorrect">questions</span> and answers</p> <p class="MsoNormal"><span class="GRcorrect">data</span> warehousing architect <span class="GRcorrect">interview</span> questions</p> <p class="MsoNormal"><span class="GRcorrect">data</span> warehouse testing <span class="GRcorrect">interview</span> questions pdf</p> <p class="MsoNormal"><span class="GRcorrect">data</span> warehousing concepts <span class="GRcorrect">interview</span> questions</p> <p class="MsoNormal"><span class="GRcorrect">advanced</span> data warehouse <span class="GRcorrect">interview</span> questions</p> <p class="MsoNormal"><span class="GRcorrect">oracle</span> data warehouse <span class="GRcorrect">interview</span> questions</p> <p class="MsoNormal"><span class="GRcorrect">data</span> warehouse architect <span class="GRcorrect">interview</span> questions</p> <p class="MsoNormal"><span class="GRcorrect">dwh</span> concepts interview <span class="GRcorrect">questions</span></p> <p class="MsoNormal"><span class="GRcorrect">data</span> warehousing interview <span class="GRcorrect">questions</span> and answers pdf</p> <p class="MsoNormal"><span class="GRcorrect">data</span> warehouse testing <span class="GRcorrect">interview</span> questions and answers</p> <p class="MsoNormal"><span class="GRcorrect">data</span> warehousing testing <span class="GRcorrect">interview</span> questions</p> <p class="MsoNormal"><span class="GRcorrect">advanced</span> data warehouse <span class="GRcorrect">interview</span> questions</p> <p class="MsoNormal"><span class="GRcorrect">data</span> warehousing concepts <span class="GRcorrect">interview</span> questions <span class="GRcorrect">answers</span></p> <p class="MsoNormal"><span class="GRcorrect">dwh</span> interview questions</p> <p class="MsoNormal"><span class="GRcorrect">dw</span> interview questions</p> <span style="font-size:10pt"><span class="GRcorrect">data</span> warehouse faq answers</span><p></p><p style="padding:0px;margin:0px 0px 1.5385em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;line-height:30px;background-color:rgb(255,255,255)"> <br></p> Software Testinghttp://www.blogger.com/profile/03753363363746376712noreply@blogger.com142tag:blogger.com,1999:blog-1578677178561645717.post-36967071799814047212012-11-30T06:51:00.001-08:002012-11-30T06:51:45.432-08:00How to Deliver High Value Software Features using Agile Scrum Process<h3 style="padding:0px;margin:1.6667em 0px 0.5556em;font-size:1.3846em;line-height:1.1111em;font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;background-color:rgb(255,255,255)">What is agile <span class="GRcorrect">scrum</span> (sprint) process?</h3> <p style="padding:0px;margin:0px 0px 1.5385em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;line-height:30px;background-color:rgb(255,255,255)"><strong style="padding:0px;margin:0px"><span class="GRnoSuggestion GRcorrect">Scrum</span></strong> is a software development process. In today's rapid world stakeholders want <span class="GRcorrect">immediate return</span> on their investments. They don't want to wait for longer periods to get <span class="GRcorrect">full featured product</span>. As a result, nowadays new <strong style="padding:0px;margin:0px">software development and testing framework</strong> <span class="GRcorrect">is catching</span> momentum i.e. <span class="GRnoSuggestion GRcorrect">Scrum</span> approach.</p> <p style="padding:0px;margin:0px 0px 1.5385em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;line-height:30px;background-color:rgb(255,255,255)">In <strong style="padding:0px;margin:0px"><span class="GRcorrect">scrum</span></strong>, projects are divided <span class="GRcorrect">in</span> <span class="GRcorrect">small</span> features to be developed and tested in specific time-frames called as <strong style="padding:0px;margin:0px">sprint</strong> (small cycles). Features should get developed and tested in specified small time-frames. This agile <span class="GRcorrect">scrum</span> team is handled by <strong style="padding:0px;margin:0px"><span class="GRcorrect">scrum</span> master</strong>.</p> <p style="padding:0px;margin:0px 0px 1.5385em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;line-height:30px;background-color:rgb(255,255,255)"><span id="more-577" style="padding:0px;margin:0px"></span>Scrum is an iterative, incremental framework for projects and products or application development. <span class="GRnoSuggestion GRcorrect">Scrum</span> has become more and more popular software development and testing framework among organizations. Many small to large sized IT companies have started to embrace <span class="GRcorrect">Scrum framework</span>, as this can create <strong style="padding:0px;margin:0px">excellent quality products in less time</strong> than other traditional methodologies. This framework can save companies both time and money.</p> <pre style="padding:0.7692em;margin-top:0px;margin-bottom:1.5385em;font-size:1.3em;overflow:auto;background-color:rgb(236,236,236);color:rgb(34,34,34);line-height:30px"><img class="aligncenter size-full wp-image-578" title="agile scrum sprint process" src="http://www.softwaretestinghelp.com/wp-content/qa/uploads/2010/07/agile-scrum-sprint-process.jpg" alt="" width="432" height="338" style="padding: 0px; margin: 0px; border: none;"><em style="padding:0px;margin:0px"> Source: ScrumAlliance</em></pre><h3 style="padding:0px;margin:1.6667em 0px 0.5556em;font-size:1.3846em;line-height:1.1111em;font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;background-color:rgb(255,255,255)"> Soft Skills for a Scrum Team:</h3><p style="padding:0px;margin:0px 0px 1.5385em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;line-height:30px;background-color:rgb(255,255,255)"><strong style="padding:0px;margin:0px">What Soft Skills are required to be a Successful Scrum Team?</strong></p> <p style="padding:0px;margin:0px 0px 1.5385em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;line-height:30px;background-color:rgb(255,255,255)">When we start our regular (Agile) sprints (Cycles of work), we usually find some of the challenges with our team members. These challenges are not part of technical difficulties. It usually occurs with <span class="GRcorrect">team member's mindset</span> or their soft skills. Many successful Scrum projects taught us that the success of <span class="GRcorrect">scrum</span> depends on how team members support whole heartedly towards the Sprint.</p> <p style="padding:0px;margin:0px 0px 1.5385em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;line-height:30px;background-color:rgb(255,255,255)"><strong style="padding:0px;margin:0px">Let us discuss some of the pre-requisite soft skills for a Scrum Team.</strong></p> <h3 style="padding:0px;margin:1.6667em 0px 0.5556em;font-size:1.3846em;line-height:1.1111em;font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;background-color:rgb(255,255,255)">Team Spirit</h3><p style="padding:0px;margin:0px 0px 1.5385em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;line-height:30px;background-color:rgb(255,255,255)"> Cross functional <span class="GRcorrect">Team work</span> is at the heart of Scrum. There is no "my work", "I have finished my work" and "your work". On a Scrum team we find only "Our work", "we have completed our Sprint". Individuals <span class="GRcorrect">will have helping</span> <span class="GRcorrect">tendency</span> for sharing technical knowledge. <span class="GRnoSuggestion GRcorrect">Scrum</span> Members are always available to team members rather than locked away behind closed doors. <span class="GRnoSuggestion GRcorrect">Scrum</span> Master will always motivate the teams and create a Supporting learning environment. <span class="GRcorrect">Team</span> will always be <span class="GRcorrect">sprint</span>-oriented and often discuss smooth run of the sprint. A <span class="GRcorrect">scrum</span> team's job is to self-organize around the challenges and management's job is to remove impediments to self-organization.</p> <h3 style="padding:0px;margin:1.6667em 0px 0.5556em;font-size:1.3846em;line-height:1.1111em;font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;background-color:rgb(255,255,255)">Communication</h3><p style="padding:0px;margin:0px 0px 1.5385em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;line-height:30px;background-color:rgb(255,255,255)"> Good communication must exist among team members of <span class="GRcorrect">development team</span>, testing team, business analysts and <span class="GRcorrect">stake holders</span>. There must be highly collaborative interaction between client and the delivery teams. More client involvement implies more suggestions or changes from the client. It implies more bandwidth for communication.</p> <h3 style="padding:0px;margin:1.6667em 0px 0.5556em;font-size:1.3846em;line-height:1.1111em;font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;background-color:rgb(255,255,255)">Commitment</h3><p style="padding:0px;margin:0px 0px 1.5385em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;line-height:30px;background-color:rgb(255,255,255)"> Agile Teams <span class="GRcorrect">needs</span> periodic re-energizing to renew their commitments to their purpose and to each other. <span class="GRnoSuggestion GRcorrect">Scrum</span> Masters can help by ensuring that the team embraces the concept of whole-team responsibility and whole-<span class="GRcorrect">team</span> commitment to deliver working software at the end of each sprint. With the whole-<span class="GRcorrect">team</span> commitment, the team member who has completed his tasks will help the one who has not completed so that hopefully each finishes on time.</p> <h3 style="padding:0px;margin:1.6667em 0px 0.5556em;font-size:1.3846em;line-height:1.1111em;font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;background-color:rgb(255,255,255)">Problem Solving</h3><p style="padding:0px;margin:0px 0px 1.5385em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;line-height:30px;background-color:rgb(255,255,255)"> <span class="GRnoSuggestion GRcorrect">Scrum</span> does not simply focus on developing just any type of end product. Instead, the Scrum method allows the team to focus on creating a product that <span class="GRcorrect">fulfils</span> the customer's highest value priorities which are defined by product owners.</p> <h3 style="padding:0px;margin:1.6667em 0px 0.5556em;font-size:1.3846em;line-height:1.1111em;font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;background-color:rgb(255,255,255)">Transparency</h3><p style="padding:0px;margin:0px 0px 1.5385em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;line-height:30px;background-color:rgb(255,255,255)"> Transparency among team members and management gives a real momentum to the <span class="GRcorrect">scrum</span> team. <span class="GRnoSuggestion GRcorrect">Scrum</span> Master encourages people to ask for help, surface roadblocks, and <span class="GRcorrect">give</span> public recognition for those brave enough to do so. At the same time, Scrum Master also understands the time wasted and impact on the team when individuals sit on or ignore problems.</p> <h3 style="padding:0px;margin:1.6667em 0px 0.5556em;font-size:1.3846em;line-height:1.1111em;font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;background-color:rgb(255,255,255)"><span class="GRnoSuggestion GRcorrect">Scrum</span> Result</h3> <p style="padding:0px;margin:0px 0px 1.5385em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;line-height:30px;background-color:rgb(255,255,255)">If <span class="GRcorrect">scrum team</span> follows some of <span class="GRcorrect">above</span> said soft skills, team velocity will increase significantly. In turn, customers will appreciate the results or updates – and also can react quickly to any potential problems. <strong style="padding:0px;margin:0px"><span class="GRcorrect">Team</span> can deliver high value software features in a short time period</strong> keeps everyone on top of changing business conditions.</p> <br> Software Testinghttp://www.blogger.com/profile/03753363363746376712noreply@blogger.com0tag:blogger.com,1999:blog-1578677178561645717.post-89848122582282322302012-11-30T06:46:00.001-08:002012-11-30T06:46:59.656-08:00Tips to be More Innovative in the Age of Agile Testing<strong style="padding:0px;margin:0px;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;line-height:30px;background-color:rgb(255,255,255)">What is Agile Testing?</strong><br style="padding:0px;margin:0px;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;line-height:30px;background-color:rgb(255,255,255)"> <span style="color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;line-height:30px;background-color:rgb(255,255,255)">"Agile testing involves testing from the customer perspective as early as possible, testing early and often as code becomes available and stable enough <span class="GRcorrect">from</span> module/unit level testing." – A </span><a href="http://en.wikipedia.org/wiki/Agile_testing" target="_blank" style="padding:1px 0px;margin:0px;color:rgb(119,119,119);text-decoration:initial;border-bottom-width:1px;border-bottom-style:solid;border-color:rgb(187,187,187);font-family:Verdana,sans-serif;font-size:20px;line-height:30px;background-color:rgb(255,255,255)"><span class="GRcorrect">wikipedia</span></a><span style="color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;line-height:30px;background-color:rgb(255,255,255)"> definition.</span> <div><span style="color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;line-height:30px;background-color:rgb(255,255,255)"><br></span></div><div><p style="padding:0px;margin:0px 0px 1.5385em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;line-height:30px;background-color:rgb(255,255,255)"> <strong style="padding:0px;margin:0px">The Challenges in Agile Testing</strong></p><p style="padding:0px;margin:0px 0px 1.5385em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;line-height:30px;background-color:rgb(255,255,255)"> Agile Testers face <span class="GRcorrect">lot</span> of challenges when they are working with Agile development team. A tester should be able to apply Root-Cause Analysis when finding severe bugs so that they unlikely to reoccur. While Agile has different flavors, Scrum is one process for implementing Agile. Some of the challenging <span class="GRcorrect">scrum</span> rules to be followed by every individual are</p> <ul style="padding:0px;margin:0px 0px 1.5385em 3em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;line-height:30px;background-color:rgb(255,255,255)"><li style="padding:0px;margin:0px"> Obtain Number of Hours Commitment Up Front</li> <li style="padding:0px;margin:0px"> Gather Requirements / Estimates Up Front</li><li style="padding:0px;margin:0px"> Entering the actual hours and estimated hours daily.</li><li style="padding:0px;margin:0px"> Daily Builds</li> <li style="padding:0px;margin:0px"> Keep the Daily Scrum meetings short</li><li style="padding:0px;margin:0px"> Code Inspections are Paramount</li></ul><p style="padding:0px;margin:0px 0px 1.5385em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;line-height:30px;background-color:rgb(255,255,255)"> So, in order to meet the above challenges, an agile tester needs to be innovative with the tools that they have. A great idea happens when what you have (tangible and intangible) meets the world's deepest hunger</p><p style="padding:0px;margin:0px 0px 1.5385em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;line-height:30px;background-color:rgb(255,255,255)"> </p><p style="padding:0px;margin:0px 0px 1.5385em"><strong style="padding:0px;margin:0px">How Testers Can be More Innovative in the Age of Agile Testing?</strong></p><p style="padding:0px;margin:0px 0px 1.5385em"><strong style="padding:0px;margin:0px">Here are Important Keys to Innovation:</strong></p> <p style="padding:0px;margin:0px 0px 1.5385em"><strong style="padding:0px;margin:0px">1. Creative</strong></p><p style="padding:0px;margin:0px 0px 1.5385em">A good Agile Tester needs to be extremely creative when trying to cope up with <span class="GRcorrect">speed</span> of development/release. For a tester, being creative is more important than being critical.</p> <p style="padding:0px;margin:0px 0px 1.5385em"><strong style="padding:0px;margin:0px">2. Talented</strong></p><p style="padding:0px;margin:0px 0px 1.5385em">He must be highly talented and strives for more learning and innovating new ideas. Talented Testers are never satisfied with what they have achieved and always strives to find unimaginable bugs of high value and priority.</p> <p style="padding:0px;margin:0px 0px 1.5385em"><strong style="padding:0px;margin:0px">3. Fearless</strong></p><p style="padding:0px;margin:0px 0px 1.5385em">An Agile Tester should not be afraid to look at a developer's code and if need be, hopefully in extreme cases, go in and correct it.</p> <p style="padding:0px;margin:0px 0px 1.5385em"><strong style="padding:0px;margin:0px">4. Visionary</strong></p><p style="padding:0px;margin:0px 0px 1.5385em">He must have a comprehensive vision, which includes client's expectations and delivery of <span class="GRcorrect">the good</span> product.</p> <p style="padding:0px;margin:0px 0px 1.5385em"><strong style="padding:0px;margin:0px">5. Empowered</strong></p><p style="padding:0px;margin:0px 0px 1.5385em">He must be empowered to work in Pairs. He will be <span class="GRcorrect">involving</span> in Pair Programming to bring shorter scripts, better designs and finding more bugs.</p> <p style="padding:0px;margin:0px 0px 1.5385em"><strong style="padding:0px;margin:0px">6. Passionate</strong></p><p style="padding:0px;margin:0px 0px 1.5385em">Passionate Testers always have something unique to contribute that may be in terms of their innovative ideas, the way they carry day-to-day work, their outputs and improve things around them tirelessly.</p> <p style="padding:0px;margin:0px 0px 1.5385em"><strong style="padding:0px;margin:0px">7. Multiple Disciplines</strong></p><p style="padding:0px;margin:0px 0px 1.5385em">Agile Tester must have multiple skills like, Manual, Functional, Performance testing skills and soft skills like Leadership skills, Communication skills, EI, etc. <span class="GRcorrect">so</span> that agile testing will become a cake walk.</p> <p style="padding:0px;margin:0px 0px 1.5385em">Tags:</p><p style="padding:0px;margin:0px 0px 1.5385em"></p><p class="MsoBodyText"><a name="_GoBack"></a><span class="GRcorrect">agile</span> <span class="GRcorrect">testing</span> life cycle</p> <p class="MsoBodyText"><span class="GRcorrect">agile</span> testing <span class="GRcorrect">methodology</span></p> <p class="MsoBodyText"><span class="GRcorrect">agile</span> testing <span class="GRcorrect">ppt</span></p> <p class="MsoBodyText"><span class="GRcorrect">agile</span> methodology</p> <p class="MsoBodyText"><span class="GRcorrect">agile</span> testing <span class="GRcorrect">process</span></p> <p class="MsoBodyText"><span class="GRcorrect">agile</span> model</p> <p class="MsoBodyText"><span class="GRcorrect">agile</span> testing <span class="GRcorrect">scrum</span></p> <p class="MsoBodyText"><span class="GRcorrect">scrum</span></p> <p class="MsoBodyText"><span class="GRcorrect">agile</span> testing</p> <p class="MsoBodyText"><span class="GRcorrect">agile</span> testing life <span class="GRcorrect">cycle</span></p> <p class="MsoBodyText"><span class="GRcorrect">agile</span> testing <span class="GRcorrect">scrum</span></p> <p class="MsoBodyText"><span class="GRcorrect">agile</span> testing <span class="GRcorrect">process</span> activities</p> <p class="MsoBodyText"><span class="GRcorrect">agile</span> testing <span class="GRcorrect">process</span> <span class="GRcorrect">ppt</span></p> <p class="MsoBodyText"><span class="GRcorrect">agile</span> testing <span class="GRcorrect">interview</span> questions</p> <p class="MsoBodyText"><span class="GRcorrect">software</span> testing <span class="GRcorrect">process</span> agile development</p> <p class="MsoBodyText"><span class="GRcorrect">agile</span> testing <span class="GRcorrect">process</span> <span class="GRcorrect">wikipedia</span></p> <p class="MsoBodyText"><span class="GRcorrect">agile</span> testing <span class="GRcorrect">process</span> examples</p> <p class="MsoBodyText"><span class="GRcorrect">agile</span> testing <span class="GRcorrect">scrum</span> <span class="GRcorrect">ppt</span></p> <p class="MsoBodyText"><span class="GRcorrect">what</span> is agile <span class="GRcorrect">testing</span> <span class="GRcorrect">scrum</span> and sprint</p> <p class="MsoBodyText"><span class="GRcorrect">testing</span> agile <span class="GRcorrect">scrum</span> <span class="GRcorrect">methodology</span></p> <p class="MsoBodyText"><span class="GRcorrect">agile</span> <span class="GRcorrect">scrum</span> testing <span class="GRcorrect">methodology</span></p> <p class="MsoBodyText"><span class="GRcorrect">what</span> is <span class="GRcorrect">scrum</span> <span class="GRcorrect">process</span> in testing</p> <p class="MsoBodyText"><span class="GRcorrect">agile</span> test plan</p> <p class="MsoBodyText"><span class="GRcorrect">what</span> is agile <span class="GRcorrect">methodology</span></p> <p class="MsoBodyText"><span class="GRcorrect">scrum</span> test plan</p> <p class="MsoBodyText"><span class="GRcorrect">janet</span> <span class="GRcorrect">gregory</span> agile <span class="GRcorrect">test</span> plan template</p> <p class="MsoBodyText"><span class="GRcorrect">agile</span> test plan <span class="GRcorrect">template</span></p> <p class="MsoBodyText"><span class="GRcorrect">quality</span> assurance <span class="GRcorrect">agile</span> test plan</p> <p class="MsoBodyText"><span class="GRcorrect">agile</span> test plan <span class="GRcorrect">forums</span></p> <p class="MsoBodyText"><span class="GRcorrect">agile</span> test plan <span class="GRcorrect">quality</span> methodologies</p> <p class="MsoBodyText"><span class="GRcorrect">kind</span> agile test plan</p> <p class="MsoBodyText"><span class="GRcorrect">agile</span> test plan <span class="GRcorrect">sample</span></p> <p class="MsoBodyText"><span class="GRcorrect">test</span> plan in agile <span class="GRcorrect">methodology</span></p> <p class="MsoBodyText"><span class="GRcorrect">agile</span> <span class="GRcorrect">scrum</span> testing <span class="GRcorrect">process</span></p> <p class="MsoBodyText"><span class="GRcorrect">agile</span> testing <span class="GRcorrect">process</span> diagram</p> <p class="MsoBodyText"><span class="GRcorrect">agile</span> testing <span class="GRcorrect">process</span> <span class="GRcorrect">ppt</span></p> <p class="MsoBodyText"><span class="GRcorrect">agile</span> software <span class="GRcorrect">testing</span> process</p> <p class="MsoBodyText"><span class="GRcorrect">agile</span> testing <span class="GRcorrect">challenges</span></p> <p class="MsoBodyText"><span class="GRcorrect">agile</span> testing basics</p> <p class="MsoBodyText"><span class="GRcorrect">agile</span> regression <span class="GRcorrect">testing</span></p> <p class="MsoBodyText"><span class="GRcorrect">what</span> is agile <span class="GRcorrect">testing</span> in software testing</p> <p class="MsoBodyText"><span class="GRcorrect">agile</span> testing <span class="GRcorrect">process</span> <span class="GRcorrect">ppt</span></p> <p class="MsoBodyText"><span class="GRcorrect">testing</span> challenges <span class="GRcorrect">in</span> software testing</p> <p class="MsoBodyText"><span class="GRcorrect">testing</span> in agile <span class="GRcorrect">environment</span></p> <p class="MsoBodyText"><span class="GRcorrect">what</span> is agile <span class="GRcorrect">testing</span> in software testing</p> <p class="MsoBodyText"><span class="GRcorrect">regression</span> testing <span class="GRcorrect">in</span> agile</p> <p class="MsoBodyText"><span class="GRcorrect">define</span> agile testing</p> <p class="MsoBodyText"><span class="GRcorrect">agile</span> testing <span class="GRcorrect">benefits</span></p> <p class="MsoBodyText"><span class="GRcorrect">role</span> of tester in <span class="GRcorrect">agile</span></p> <p class="MsoBodyText"><span class="GRcorrect">gile</span> test strategy</p> <p class="MsoBodyText"><span class="GRcorrect">agile</span> testing <span class="GRcorrect">methodology</span> wiki</p> <p class="MsoBodyText"><span class="GRcorrect">testing</span> agile <span class="GRcorrect">scrum</span> <span class="GRcorrect">methodology</span></p> <p class="MsoBodyText"><span class="GRcorrect">agile</span> testing <span class="GRcorrect">methodology</span> tutorial</p> <p class="MsoBodyText"><span class="GRcorrect">agile</span> testing <span class="GRcorrect">methodology</span> diagram</p> <p class="MsoBodyText"><span class="GRcorrect">performance</span> testing <span class="GRcorrect">agile</span> methodology</p> <p class="MsoBodyText"><span class="GRcorrect">agile</span> methodology in <span class="GRcorrect">software</span> testing</p> <p class="MsoBodyText"><span class="GRcorrect">agile</span> model in <span class="GRcorrect">testing</span></p> <p class="MsoBodyText"><span class="GRcorrect">what</span> is agile <span class="GRcorrect">testing</span></p> <p class="MsoBodyText"><span class="GRcorrect">what</span> is agile <span class="GRcorrect">testing</span> explain with example</p> <p class="MsoBodyText"><span class="GRcorrect">agile</span> testing <span class="GRcorrect">process</span></p> <p class="MsoBodyText"><span class="GRcorrect">agile</span> testing <span class="GRcorrect">methodology</span></p> <p class="MsoBodyText"><span class="GRcorrect">what</span> is agile <span class="GRcorrect">testing</span> model</p> <p class="MsoBodyText"><span class="GRcorrect">what</span> is agile <span class="GRcorrect">methodology</span></p> <p class="MsoBodyText"><span class="GRcorrect">what</span> is agile <span class="GRcorrect">testing</span> in software testing</p> <p class="MsoBodyText"><span class="GRcorrect">what</span> is agile <span class="GRcorrect">testing</span> with <span class="GRcorrect">example</span></p> <p class="MsoBodyText"><span lang="DA">what is agile testing <span class="GRspelling">wikipedia</span></span></p><p></p><p style="padding:0px;margin:0px 0px 1.5385em"><br></p><p style="padding:0px;margin:0px 0px 1.5385em"> <br></p><p></p></div> Software Testinghttp://www.blogger.com/profile/03753363363746376712noreply@blogger.com0tag:blogger.com,1999:blog-1578677178561645717.post-45983890023862430942012-11-30T06:35:00.000-08:002012-11-30T06:36:08.468-08:00Test Driven Development – Some practical tips<h1 class="title" style="margin:0px 0px 20px;padding:0px;border:0px;outline:0px;font-size:28px;vertical-align:baseline;color:rgb(51,51,51);line-height:34px;font-family:Arial,Helvetica,sans-serif">Test Driven Development – Some practical tips</h1> <div class="entry" style="margin:0px;padding:0px;border:0px;outline:0px;vertical-align:baseline"><p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"> In an earlier post, I had touched upon TDD very briefly, and promised some practical tips on implementing TDD in a future post. Here they are…</p><p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"> Having managed teams implementing TDD, I <span class="GRcorrect">have learnt</span> the hard way, that implementing TDD is not a cakewalk; the glamour and hype attached to it notwithstanding. So if you are contemplating on implementing TDD, try the following practical tips:</p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline">1) There will be starting-trouble, since this calls for a complete paradigm shift in the minds of the developers. Many of us have grown up hearing and practicing this: Write code, then test. TDD turns that completely topsy-turvy. It says, write a test case (it will obviously fail since it is checking for code which is still not there). Then write code which will just satisfy the test case and make it run (note that the code should do nothing more than barely making the test case run). Then write the <em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline">next</em> test case, and make it pass by writing the corresponding code. This concept requires some unlearning, so be prepared to add sufficient buffer in your deliverables for implementing this, and don't crucify your developers for taking some extra time in the beginning of your TDD roll-out. This extra time will decrease once they are comfortable with this approach – at that point, they'll reach a desirable mindset where they'll find it difficult to write code without writing test cases, but till then, patience….</p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline">2) Better to involve those experienced folks who know Unit Testing (<span class="GRcorrect">eg</span>. NUnit, JUnit). They would <span class="GRcorrect">have written test</span> cases after the code was written, and would definitely have faced issues where they've had to refactor the code in order to increase the code coverage <span class="GRcorrect">from</span> the unit test cases written. This is a constant pain, and TDD removes this by having tests initially, so code-coverage is not an issue (in case you are wondering, 'code-coverage' gives a measure of how much of the <span class="GRnoSuggestion GRcorrect">codebase</span> is covered/tested by the unit-test-cases-suite).</p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline">3) Start with a very small but determined pilot team. Starting with a big team is not really manageable, because of immediate delivery pressures.</p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline">4) It is very easy for them to slip back into the traditional way of coding, if there is a schedule pressure, so watch closely for that.</p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline">5) Go for a code coverage of about 70-80%<span class="GRcorrect">…</span>more than that could become an overkill in the initial stages… looks like the Pareto rule is kind-of applicable here too — you can achieve 80% of code coverage with 20% of effort, but the remaining 20% will take about 80% of the effort. Do I have an array of statistics to prove this? Nope<span class="GRcorrect">…</span>Just a few metrics collected and analyzed from the projects I've worked on, and a gut feeling which has evolved over time. I have seen the enthusiasm die down because of the amount of additional effort needed to cover that last stretch <span class="GRcorrect">…</span>It will take significant effort from you to rekindle the enthusiasm. So better to aim for about 70-80 % initially, and it has a better chance of working.</p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline">6) <span class="GRcorrect">Its</span> ok to have less unit tests for UI, since UI needs to get covered more by the Functionality/Usability testing. Focus on using TDD more for the sub-strata (layers below the UI).</p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline">7) In the middle layer(s), there would be integration points, so be sure not to ignore them, especially if they are part of the critical functionality/logic. Now the question is, we are doing Unit Testing (or in other words, we are <em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"></em><span class="GRcorrect"><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline">not</em>doing</span> Integration testing), so how do we cater to the integration points, since there would be some chatting between modules/classes. The solution is to use stubs. That is, create stubs which will be called (instead of the actual foreign class/module) by the unit, and return various values, and so the behavior of the unit can be tested based on the different values returned by the stub. Now the point is, writing stubs can be cumbersome. So for that, you could use some third-party API. For <span class="GRcorrect">eg</span>, there's a very good API for this very purpose, called TypeMock.</p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline">What is outlined above is but some of the pitfalls that you need to watch out for, in your journey towards TDD. Happy <em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline">Test Driving</em> !</p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline">Tags:</p><p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"> </p><p class="MsoBodyText"><span class="GRcorrect">test</span> driven testing</p> <p class="MsoBodyText"><span class="GRcorrect">test</span> driven testing <span class="GRcorrect">methodology</span></p> <p class="MsoBodyText"><span class="GRcorrect">data</span> driven tests</p> <p class="MsoBodyText"><span class="GRcorrect">keyword</span> driven tests</p> <p class="MsoBodyText"><span class="GRcorrect">driven</span> dressage <span class="GRcorrect">tests</span></p> <p class="MsoBodyText"><span class="GRcorrect">test</span> driven <span class="GRcorrect">development</span> unit testing</p> <p class="MsoBodyText"><span class="GRcorrect">test</span> complete data <span class="GRcorrect">driven</span> testing</p> <p class="MsoBodyText"><span class="GRcorrect">test</span> driven <span class="GRcorrect">development</span> agile</p> <p class="MsoBodyText"><span class="GRcorrect">advantages</span> of test <span class="GRcorrect">driven</span> development</p> <p class="MsoBodyText"><span class="GRcorrect">test</span> driven <span class="GRcorrect">development</span> methodology</p> <p class="MsoBodyText"><span class="GRcorrect">test</span> plan driven <span class="GRcorrect">method</span></p> <p class="MsoBodyText"><span class="GRcorrect">test</span> driven <span class="GRcorrect">development</span> process</p> <p class="MsoBodyText"><span class="GRcorrect">test</span> driven <span class="GRcorrect">development</span> pdf</p> <p class="MsoBodyText"><span class="GRcorrect">test</span> first <span class="GRcorrect">development</span> methodology</p> <p class="MsoBodyText"><span class="GRcorrect">test</span> driven <span class="GRcorrect">refactoring</span></p> <p class="MsoBodyText"><span class="GRcorrect">advantages</span> of test <span class="GRcorrect">driven</span> development</p> <p class="MsoBodyText"><span class="GRcorrect">test</span> driven <span class="GRcorrect">development</span> cycle</p> <p class="MsoBodyText"><span class="GRcorrect">test</span> driven <span class="GRcorrect">development</span> testing technique</p> <p class="MsoBodyText"><span class="GRcorrect">test</span> driven <span class="GRcorrect">development</span> unit testing</p> <p class="MsoBodyText"><span class="GRcorrect">test</span> driven <span class="GRcorrect">development</span> private methods</p><p></p><p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"> <br></p><p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"></p><p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><br></p><p></p><p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"> <br></p></div> Software Testinghttp://www.blogger.com/profile/03753363363746376712noreply@blogger.com0tag:blogger.com,1999:blog-1578677178561645717.post-49122073892567547162012-11-30T05:09:00.001-08:002012-11-30T05:09:50.595-08:00Enterprise Resource Planning (ERP) – The Basics<h1 class="title" style="margin:0px 0px 20px;padding:0px;border:0px;outline:0px;font-size:28px;vertical-align:baseline;color:rgb(51,51,51);line-height:34px;font-family:Arial,Helvetica,sans-serif">Enterprise Resource Planning (ERP) – The Basics</h1> <div class="entry" style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;line-height:1.5em;font-family:Helvetica,Arial,sans-serif;color:rgb(85,85,85)"><p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"> Enterprise Resource Planning (ERP) is a business management software that uses a system of integrated applications to run & manage the various businesses of an organization effectively & efficiently. <span class="GRcorrect">Its</span> a suite of integrated modules built for various functionalities of the organization like Manufacturing, CRM, Supply Chain/Procurement, Finance/Accounting, Human Capital Management, Services etc. All these business functions <span class="GRcorrect">runs</span> smoothly using the various modules provided by the ERP solution.</p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline">Some of the major advantages of using an ERP solution are:</p><ul style="margin:0px 0px 1.5em;padding:0px 0px 0px 30px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style:none"> <li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc">Achieve end-to-end view across all business lines</li><li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc"> Improve performance with <span class="GRcorrect">upto</span> date information on financial & operational activities</li><li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc"> Extend global business process using Application integration architecture</li><li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc">Reduce back office costs</li> <li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc">Efficient material management planning</li><li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc"> Aligning sales channels with corporate objectives</li><li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc">Build customer focused <span class="GRcorrect">applications</span> strategy</li> <li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc">Manage global processes in <span class="GRcorrect">localized way</span></li><li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc"> BI reports & analytics for better decision making</li></ul><p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline">There are various providers of ERP solution in <span class="GRcorrect">market</span> with each of them having their pros & cons. An organization should evaluate very carefully the features of every ERP solution against their business needs and technical capabilities. One can start by implementing <span class="GRcorrect">couple</span> of <span class="GRcorrect">most important modules</span> like CRM, Manufacturing <span class="GRcorrect">etc</span> and then go full fledged into it.</p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline">You can <span class="GRcorrect">chose</span> from the below listed major ERP applications which are available in <span class="GRcorrect">market</span> today:</p> <ul style="margin:0px 0px 1.5em;padding:0px 0px 0px 30px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style:none"><li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc"> SAP Business All-in-one</li><li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc">Oracle EBS</li><li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc"> Microsoft Dynamics AX</li><li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc">Infor10 ERP Enterprise</li><li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc"> Epicor ERP</li><li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc">Sage ERP X3</li><li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc"> Lawson M3 ERP Enterprise</li><li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc">Oracle <span class="GRcorrect">JDEdwards</span> Enterprise One</li></ul></div> Software Testinghttp://www.blogger.com/profile/03753363363746376712noreply@blogger.com1tag:blogger.com,1999:blog-1578677178561645717.post-11539983996368086582012-11-30T04:49:00.001-08:002012-11-30T04:49:25.180-08:00Product Testing Vs Application Testing<h1 class="title" style="margin:0px 0px 20px;padding:0px;border:0px;outline:0px;font-size:28px;vertical-align:baseline;color:rgb(51,51,51);line-height:34px;font-family:Arial,Helvetica,sans-serif">Product Testing Vs Application Testing</h1> <div class="entry" style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;line-height:1.5em;font-family:Helvetica,Arial,sans-serif;color:rgb(85,85,85)"><p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"> On the surface, there are few differences in terms of skills required to do product testing compared to application testing, except perhaps extra diligence and an eye for detail. However, some of the differences between product and application testing are as follows:</p> <ul style="margin:0px 0px 1.5em;padding:0px 0px 0px 30px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style:none"><li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc"> Software products need to work on a variety of environments and are expected to work on supported configurations of all supported platforms. This involves running of compatibility tests against <span class="GRcorrect">supported</span> operating systems and software that must co-exist with the product. This also involves repeating the same tests a number of times and is a fantastic argument for automation.</li> <li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc">Products must be intuitive to use and work in a similar manner to other products in its domain. Moreover, <span class="GRcorrect">products</span> are used by a large number of end-users and the way different users use it, is liable to vary. Application users are typically instructed on how to use the application and how not to. Therefore, it's generally alright if an application is shipped with some bugs in it. For products however, usability and stress testing are of utmost importance and it means that there needs to be a user advocate who tests a product with an end-user in mind.</li> <li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc">Software products also tend to have regular upgraded releases, with enhanced functions which should not break any existing product functionalities. This requires efficient regression testing.</li> <li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc">The product management team collates frequently changing customer requirements and market expectations of a product, while also contributing to the product roadmap. As a result, the scope of the product changes constantly and testing becomes complicated with daily builds involved.</li> <li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc">Product management's intervention <span class="GRcorrect">in</span> scope changes becomes more pronounced in agile environments while management thinks that by using agile the product can be taken to market faster. However, agile testing by itself is a specialized area and with <span class="GRcorrect">requirements</span> being added or modified constantly, testing becomes a complex process.</li> <li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc">In some cases, when any bugs are found in a product after a release happens, they are taken as feature additions for the next product version and made as change requirements. In the case of an application, a customer can provide change requirements as bugs and construe it as a gap in understanding the requirements.</li> <li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc">If a product is to be delivered as a plug-n-play solution to end-users, testing becomes straightforward as there are no multiple configurations and environments involved.</li> </ul><p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline">This is just a high-level overview of the differences between product testing and application testing.</p></div> <br>Tags:<br><br><span class="GRcorrect">difference</span> between application testing and product testing<br><br><span class="GRcorrect">product</span> testing <span class="GRnoSuggestion GRcorrect">vs</span> application testing<br> <br><span class="GRcorrect">difference</span> between project product testing<br><br><span class="GRcorrect">difference</span> between mobile testing mobile application testing<br><br><span class="GRcorrect">difference</span> between software application software product<br> <br><span class="GRcorrect">difference</span> between application development and product development<br><br><span class="GRcorrect">difference</span> between application testing and system testing<br><br><span class="GRcorrect">difference</span> between web testing application testing<br> <br><span class="GRcorrect">what</span> is the difference between calling a function and reusing an action<br><br><span class="GRcorrect">product</span> testing<br><br><span class="GRcorrect">product</span> testing definition<br> <br><span class="GRcorrect">product</span> testing process<br><br><span class="GRcorrect">software</span> product testing<br><br><span class="GRcorrect">application</span> testing<br><br><span class="GRcorrect">application</span> testing methodologies<br> <br><span class="GRcorrect">application</span> testing process<br><br><span class="GRcorrect">application</span> testing services<br><br><span class="GRcorrect">web</span> application testing<br><br><span class="GRcorrect">software</span> testing<br> <br><span class="GRcorrect">mobile</span> application testing<br><br><span class="GRcorrect">application</span> testing checklist<br><br><span class="GRcorrect">application</span> testing tools Software Testinghttp://www.blogger.com/profile/03753363363746376712noreply@blogger.com0tag:blogger.com,1999:blog-1578677178561645717.post-45353137435847463642012-11-30T04:40:00.001-08:002012-11-30T04:40:23.371-08:00Future of Test Automation and infrastructure<h1 class="title" style="margin:0px 0px 20px;padding:0px;border:0px;outline:0px;font-size:28px;vertical-align:baseline;color:rgb(51,51,51);line-height:34px;font-family:Arial,Helvetica,sans-serif">Future of Test Automation and infrastructure</h1> <div class="entry" style="margin:0px;padding:0px;border:0px;outline:0px;vertical-align:baseline"><p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"> <strong style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"><span style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;text-decoration:underline">Where were we and where are we today in automation?</span></strong></p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><span class="GRcorrect">Software</span> provides the core functionality of <span class="GRcorrect">most electronics</span> products. These "software-intensive systems" have a large penetration into daily life and this penetration is expected to grow even more in the coming years. In addition to the growth in size and complexity, these software systems need to be of ever increasing quality and need to be developed in ever-shorter time frames. To tackle these increasing quality requirements, testing is an important step in the development of a software-intensive system, as it checks if requirements <span class="GRcorrect">to</span> a system have not been met. To remain competitive in the development of these systems, industry needs to increase productivity by means of better testing practices.</p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline">Starting from the initial stage of testing where automation tools were not available rather the dependency was <span class="GRcorrect">highly</span> on the unit tests performed by Developers and then manual testing by QA engineer. In Automation we have evolved from Core framework to Record and playback to Custom frameworks. And in custom frameworks, one starts to build the frameworks like Modular framework, Data Driven framework, keyword Driven framework, model based framework and eventually end up with to Hybrid framework solution. However the need has grown from these tool bounded scripts to easily understandable one's, for e.g, like for non-coders like business analysts.</p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline">This need gave birth to <span class="GRcorrect">newer type</span> of framework which has evolved out of the weakness of Test Driven Development (TDD), called Behavior Driven development (BDD). BDD covers the response to the issues encountered in test-driven development:</p> <ul style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px 0px 0px 30px;border:0px;outline:0px;vertical-align:baseline;list-style:none"><li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc"> Where to start in the process</li><li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc">What to test and what not to test</li><li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc"> How much to test in one go</li><li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc">What to call the tests</li><li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc"> How to understand why a test fails</li></ul><p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"> BDD covers the 'desired behavior' which has business value for whatever entity commissioned the software unit under construction. There are many tools which are available in the market to support BDD, such as JBehave, Cucumber and Twist etc. Even after this advancement in testing, the question which still remains at large it, what is there in future for automation? To answer this we need to first understand what is in progress in <span class="GRcorrect">software industry</span> that requires immediate futuristic attention to address this question.</p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><strong style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"><span style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;text-decoration:underline">Smart UI Application Progress</span></strong></p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline">Intelligent applications are aggressively occupying the smart applications running hardware which <span class="GRcorrect">are</span> now a day's commonly visible on smart phones, PC, TV, games consoles etc. Smart applications such as drawing based, security based, motion sensor based have become new vertical in software development and testing. Due to humongous rise in demands of such devices and software, this has given rise to boom in the software industry. Consequently this has enabled and influenced us to write software for smart mobiles and portable devices.</p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><strong style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"><span style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;text-decoration:underline">Software Test automation needs to support smart UI Applications</span></strong></p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline">In order to support such smart UI applications, we definitely need to test them, and in order to test them we definitely need to perform <span class="GRcorrect">test</span> Automation to eventually support such technology. Consecutively our innovation must also work in this direction of development of such tools which support and drive.</p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><strong style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"><span style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;text-decoration:underline">What is expected?</span></strong></p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline">Hence there is <span class="GRcorrect">need</span> for <span class="GRcorrect">new level</span> of test automation products that can reduce the cost of implementation and ownership so that you can focus on testing your application instead of developing your tests. These tools should provide a pre-written test framework that can substantially reduce — or even eliminate — the need to learn and use scripting languages.</p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline">Such test frameworks, should have the capability to:</p> <ul style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px 0px 0px 30px;border:0px;outline:0px;vertical-align:baseline;list-style:none"><li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc"> Make automation accessible to testers who aren't programmers</li><li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc">Simplify script development</li><li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc"> Reduce the maintenance effort</li></ul><p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"> It could be possible that most of these frameworks can be wrapped around one or more existing commercial/freeware test tools, but not always. The primary difference among the products relates to their underlying execution "engine" or script library and whether it is mapped to action words, windows, objects or classes.</p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><strong style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"><span style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;text-decoration:underline">Vision for Future of Automation</span></strong></p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline">On following <span class="GRcorrect">few good practices</span>, the future of test Automation and test automation management can be in good state:</p> <ul style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px 0px 0px 30px;border:0px;outline:0px;vertical-align:baseline;list-style:none"><li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc"> Quality of test code should be good for production. Means, Use Private/ Protected member variables /methods. Make them public only when required</li><li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc"> Traceable and Making Debugging Less Painful</li></ul><p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"> Test automation management tools should ease the process of debugging by providing useful information and have all relevant references in one place.</p><ul style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px 0px 0px 30px;border:0px;outline:0px;vertical-align:baseline;list-style:none"> <li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc">Import only those classes which are required</li><li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc"> <span class="GRcorrect">Carefully</span> Use <span class="GRcorrect">xPath</span> <span class="GRcorrect">feature</span>, lesser use or avoid Indexes.</li><li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc"> Keep test data separate from test scripts.</li><li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc"> Valuable Reporting</li></ul><p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"> Test automation reporting should be meaningful and flexible to both test engineers and IT managers. An outstanding management tool provides metrics such as trend analysis and key performance indicators for high-level decision making. Meanwhile, it should also have <span class="GRcorrect">low-level log</span> and statistics that are useful for debugging and internal analysis.</p> <ul style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px 0px 0px 30px;border:0px;outline:0px;vertical-align:baseline;list-style:none"><li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc"> Instant Recognition of Changes in Testing Results</li></ul><p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"> It is essential now to pick up changes in automated test results almost immediately, which requires the management tool to shift information and improve test efficiency.</p><ul style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px 0px 0px 30px;border:0px;outline:0px;vertical-align:baseline;list-style:none"> <li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc"> Compliance with Testing Systems</li></ul><p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"> Easy integration with other systems will help manage different tasks on a single platform.</p><p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"> <br></p><p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline">Tags:</p><p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"> </p><p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><br> </span></font></p><p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">future</span> of automation testing</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">tools</span> of automation testing</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">why</span> automation testing is needed</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">what</span> is meant by <span class="GRcorrect">automation</span> testing</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">does</span> automation replace manual testing</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">automated</span> testing <span class="GRcorrect">wikipedia</span></span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">automated</span> software testing</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">latest</span> trends in test automation</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">test</span> automation introduction</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">latest</span> trends in test automation</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">latest</span> trends process automation</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">challenges</span> in test automation</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">benefits</span> of automation testing</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">why</span> we use automation testing</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">tools</span> of automation testing</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">does</span> automation replace manual testing</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">advantage</span> of automation testing over manual</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">test</span> automation process</span></font></p> <p></p></div> Software Testinghttp://www.blogger.com/profile/03753363363746376712noreply@blogger.com1tag:blogger.com,1999:blog-1578677178561645717.post-74041787037654874882012-11-30T04:37:00.001-08:002012-11-30T04:37:38.920-08:00Mobile Testing<h1 class="title" style="margin:0px 0px 20px;padding:0px;border:0px;outline:0px;font-size:28px;vertical-align:baseline;color:rgb(51,51,51);line-height:34px;font-family:Arial,Helvetica,sans-serif">Mobile Testing</h1><div class="entry" style="margin:0px;padding:0px;border:0px;outline:0px;vertical-align:baseline"> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline">Exponential growth of Smartphones has opened newer avenues for enterprises to integrate them into mainstream computing. Enterprises across all industry verticals are embracing mobility at a rapid pace.</p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline">According to Gartner's report on Market Insight 2012, Bring Your Own Device (BYOD), the rapid ascent of enterprise application stores, and the high expectations customers have of continual mobile app usability and performance improvements are just three of <span class="GRcorrect">many factors</span> driving mobility growth.</p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline">Enterprise applications that were initially available as web applications are now being ported to mobile devices. Enterprises are now deploying mobile applications in empowering workforces in areas like Sales, Supply Chain, Field Support and Shop Floor.</p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline">Mobile testing is quickly becoming a necessity as more and more businesses are embracing mobility. Mobile apps reflects the face of the enterprise, bad quality mobile apps can severely affect the reputation of the overall company. Even smaller issues can negatively impact the brand. For example, according to research cited by Aberdeen senior research analyst Jim Rapoza, 7% of users abandon applications after just one second of delay in performance. 11% abandon at two seconds, 18% at three, 25% at four and 50% at five seconds.</p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline">In Mobile application testing, there are unique challenges that are encountered like device and OS fragmentation, browser compatibility, UI compatibility, differences in the graphics and screen density of various devices. There are various forms of bugs that affect mobile apps testing including minor flaws related to incoming calls, power cycles, low signal strength, form <span class="GRcorrect">factors</span> variations, bandwidth issues, network speeds, recording user actions and input errors.</p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline">The complexity of testing mobile devices is that there is code on mobile devices, especially in business apps, code runs on several servers and in <span class="GRnoSuggestion GRcorrect">backend</span> data centers. The system must be active to test the code on mobile devices. Setting up multiple infrastructures to test on mobile devices is an expensive proposition that customers would not prefer. The technique is to isolate the different tiers of applications and stimulate a whole data center running. The Test Engineer can <span class="GRcorrect">virtualize</span> and stimulate, allowing him to concentrate only on the mobile device and forget about all the <span class="GRcorrect">backend</span> stuff.</p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline;text-align:center"><img class="aligncenter size-full wp-image-1328" title="t1" src="http://blog.aspiresys.com/wp-content/uploads/2012/11/t1.jpg" alt="" width="737" height="790" style="margin: 0px auto 15px; padding: 0px; border: 0px; outline: 0px; font-size: 14px; vertical-align: baseline; display: block;"></p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><img class="aligncenter size-full wp-image-1330" title="t2" src="http://blog.aspiresys.com/wp-content/uploads/2012/11/t21.jpg" alt="" width="732" height="480" style="margin: 0px auto 15px; padding: 0px; border: 0px; outline: 0px; font-size: 14px; vertical-align: baseline; text-align: center; display: block;"></p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><strong style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline">Automation tools available for testing:</strong></p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline">Mainly mobile testing is done manually on actual devices. Some of the following tools are available in to test the functionality as well as usability of <span class="GRcorrect">application</span>.</p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline">- <span class="GRnoSuggestion GRcorrect">Robotium</span> for Android</p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline">- <span class="GRnoSuggestion GRcorrect">Testquest</span>, try, and <span class="GRcorrect">digia</span> for Symbian</p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline">- <span class="GRnoSuggestion GRcorrect">FoneMonkey</span> for <span class="GRcorrect">IPhones</span></p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline">- Memory sweep for <span class="GRcorrect">IPhone</span></p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline">- Other tools: eggplant, VNC Robot, Hopper and TestQuest</p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><strong style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline">Performance/load and stress testing tools</strong></p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline">- Recent announcement by <span class="GRcorrect">MicroFocus</span> about SilkPerformer 9.0 (2012) supports Mobile Web & Native <span class="GRcorrect">apps</span> testing on <span class="GRcorrect">iOS</span>, Android & BB platforms</p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline">- HP LoadRunner supports mobile web & native <span class="GRcorrect">apps</span> testing on <span class="GRcorrect">iOS</span>, Android, BB & WM platforms</p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline">- <span class="GRnoSuggestion GRcorrect">NeoLoad</span> supports mobile web & native mobile apps</p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline">- JMeter supports mobile web app testing on simulators</p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline">- IBM Rational Performance Tester (RPT) supports mobile web app testing as well</p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><br></p><p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"> Tags:</p><p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"></p><p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">mobile</span> testing</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">mobile</span> testing tutorial</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">mobile</span> testing tools</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">mobile</span> testing interview questions</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">mobile</span> testing jobs</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">mobile</span> testing <span class="GRcorrect">ppt</span></span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">mobile</span> testing wiki</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">mobile</span> app testing</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">mobile</span> software testing</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">mobile</span> automation testing tools</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">mobile</span> testing tutorial</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">mobile</span> phone testing tools</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">mobile</span> application testing</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">mobile</span> testing interview questions</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">mobile</span> testing tools tutorial</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">mobile</span> app testing tools</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">mobile</span> testing tools free download</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">mobile</span> testing tutorial pdf</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">mobile</span> testing interview questions</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">mobile</span> testing tools</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">java</span> mobile application testing tutorial</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">java</span> mobile application testing example</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">mobile</span> application development tutorial</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px">mobile testing pdf</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px">mobile testing techniques</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px">mobile application testing techniques and tools</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px">software testing techniques</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px">mobile testing methodologies</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">mobile</span> testing tutorial</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">mobile</span> testing tools</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">mobile</span> testing interview questions</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px">mobile testing interview questions and answers pdf</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">mobile</span> testing tools</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">mobile</span> testing tutorial</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px">mobile testing interview questions with answers</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px">mobile apps testing interview questions</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px">mobile application testing interview questions</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px">mobile application testing interview questions and answers</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px">mobile app testing interview questions</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px">test cases mobile application testing</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px">iphone testing interview questions</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px">mobile application testing tutorial</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px">interview questions handset testing</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px">mobile application testing tools</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px">mobile application testing ppt</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px">mobile application test cases sample</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px">windows mobile test cases</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px">automation tool test cases</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px">android test cases</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">mobile</span> application testing</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px">test cases for mobile</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px">test cases for mobile phone</span></font></p> <p></p></div> Software Testinghttp://www.blogger.com/profile/03753363363746376712noreply@blogger.com4tag:blogger.com,1999:blog-1578677178561645717.post-14023356730347510482012-11-30T04:35:00.000-08:002012-11-30T04:36:02.013-08:00Automated Regression Testing Challenges in Agile Environment<h1 style="padding:0px;margin:0px;font-size:2.8em;line-height:1.4286em;font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;letter-spacing:-1px;color:rgb(169,0,0);background-color:rgb(255,255,255)"><p style="padding:0px;margin:0px 0px 1.5385em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;font-weight:normal;line-height:30px"> Agile Projects present their own challenges to the Automation team; Unclear project scope, Multiple iterations, Minimal documentation, early and frequent Automation needs and active stakeholder involvement all demand <span class="GRcorrect">lot</span> of challenges from the Automation Team<span class="GRcorrect">.</span><strong style="padding:0px;margin:0px">Some of these challenges are:</strong></p> <p style="padding:0px;margin:0px 0px 1.5385em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;font-weight:normal;line-height:30px"><strong style="padding:0px;margin:0px">Challenge 1: Requirement Phase</strong><br style="padding:0px;margin:0px"> Test Automation developer <span class="GRcorrect">captures</span> requirements in the form of "user stories", which are brief descriptions of customer-relevant functionality.</p><p style="padding:0px;margin:0px 0px 1.5385em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;font-weight:normal;line-height:30px"> Each requirement has to be prioritized as follows:</p><p style="padding:0px;margin:0px 0px 1.5385em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;font-weight:normal;line-height:30px"><strong style="padding:0px;margin:0px">High:</strong> These are mission critical requirements that absolutely have to be done in the first release<br style="padding:0px;margin:0px"> <strong style="padding:0px;margin:0px">Medium:</strong> These are requirements that are important but can be worked around until implemented.<br style="padding:0px;margin:0px"><strong style="padding:0px;margin:0px">Low:</strong> These are requirements that are nice-to-have but not critical to the operation of the software.</p> <p style="padding:0px;margin:0px 0px 1.5385em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;font-weight:normal;line-height:30px">Once priories are established, the release "iterations" are planned. Normally, each Agile release iteration takes between 1 to 3 months to deliver. Customers/software folks take <span class="GRcorrect">liberty</span> to make too many changes to the requirements. Sometimes, these changes are so volatile that the iterations are bumped off. These changes are greater challenges in implementing Agile Automation testing process.</p> <p style="padding:0px;margin:0px 0px 1.5385em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;font-weight:normal;line-height:30px"><strong style="padding:0px;margin:0px">Challenge 2: Selecting the Right Tools</strong></p> <p style="padding:0px;margin:0px 0px 1.5385em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;font-weight:normal;line-height:30px"><span class="GRcorrect">Traditional</span>, test-last tools with record-and-playback-features force teams to wait until after the software is done. <span class="GRcorrect">More over</span>, traditional test automation tools don't work <span class="GRcorrect">for</span> an Agile context because they solve traditional problems, and those are different from the challenges facing Agile Automation teams. Automation in the early stages of an agile project is usually very tough, but as the system grows and evolves, some aspects settle and it becomes appropriate to deploy automation. So the choice of testing tools becomes critical for reaping the efficiency and quality benefits of agile.</p> <p style="padding:0px;margin:0px 0px 1.5385em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;font-weight:normal;line-height:30px"><strong style="padding:0px;margin:0px">Challenge 3: Script Development Phase</strong></p> <p style="padding:0px;margin:0px 0px 1.5385em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;font-weight:normal;line-height:30px">The Automation testers, developers, business analysts and project stakeholders all contribute to kick-off meetings where "user-stories" are selected to <span class="GRcorrect">next sprint</span>. Once the "user-stories" are selected for the sprint, they are used as the basis for a set of tests.</p> <p style="padding:0px;margin:0px 0px 1.5385em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;font-weight:normal;line-height:30px">As functionality grows with each iteration, regression testing must be performed to ensure that existing functionality has not been impacted by the introduction of new functionality in each iteration cycle. The scale of the regression testing grows with each sprint and ensures that this remains a manageable task the test team use the test automation for the regression suite.</p> <p style="padding:0px;margin:0px 0px 1.5385em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;font-weight:normal;line-height:30px"><strong style="padding:0px;margin:0px">Challenge 4: Resource Management</strong></p> <p style="padding:0px;margin:0px 0px 1.5385em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;font-weight:normal;line-height:30px">The Agile approach requires a mixture of testing skills, that is, test resource will be required to define unclear scenarios and test cases, conduct manual testing alongside developers, write automated regression tests and execute the automated regression packages. As the project progresses, specialist skills will also be required to cover further test areas that might include integration and performance testing. There should be an appropriate mix of domain specialist who plan and gather requirements. The challenging part in the Resource management is to find out test resources with multiple skills and<br style="padding:0px;margin:0px"> <span class="GRcorrect">allocate</span> them.</p><p style="padding:0px;margin:0px 0px 1.5385em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;font-weight:normal;line-height:30px"><strong style="padding:0px;margin:0px">Challenge 5: Communication</strong></p> <p style="padding:0px;margin:0px 0px 1.5385em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;font-weight:normal;line-height:30px">Good communication must exist among Automation testing team, developers, business analysts and <span class="GRcorrect">stake holders</span>. There must be highly collaborative interaction between client and the delivery teams. More client involvement implies more suggestions or changes from the client. It implies more bandwidth for communication. The key challenge is that the process should be able to capture and effectively implement all the changes and data integrity needs to be retained. In traditional testing, developers and testers are like oil and water, but in <span class="GRcorrect">agile environment</span>, the challenging task is that they both must work together to achieve the target.</p> <p style="padding:0px;margin:0px 0px 1.5385em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;font-weight:normal;line-height:30px"><strong style="padding:0px;margin:0px">Challenge 6: Daily Scrum Meeting</strong></p> <p style="padding:0px;margin:0px 0px 1.5385em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;font-weight:normal;line-height:30px"><span class="GRcorrect">Daily Scrum Meeting</span> is one of the key activities in Agile Process. Teams do meet for 15 minutes stand up sessions. What is the effectiveness of these meetings? How far these meetings help Automation practice Developers?</p> <p style="padding:0px;margin:0px 0px 1.5385em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;font-weight:normal;line-height:30px"><strong style="padding:0px;margin:0px">Challenge 7: Release Phase</strong></p> <p style="padding:0px;margin:0px 0px 1.5385em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;font-weight:normal;line-height:30px">The aim of Agile project is to deliver a basic working product as quickly as possible and then to go through a process of continual improvement. This means that there is no single release phase <span class="GRcorrect">for</span> a product. The challenging part lies in integration testing and acceptance testing of the product.</p> <p style="padding:0px;margin:0px 0px 1.5385em;color:rgb(34,34,34);font-family:Verdana,sans-serif;font-size:20px;font-weight:normal;line-height:30px">If we can meet these challenges in a well optimized manner, then Automated Regression Testing in Agile environment is an excellent opportunity for QA to take leadership of the agile processes. It is better placed to bridge the gap between users and developers, understand both what is required, how it can be achieved and how it can be assured prior to deployment. Automation practice should have a vested interest in both the how and the result, as well as continuing to assure that the whole evolving system meets business objectives and is fit for purpose.</p> </h1> Software Testinghttp://www.blogger.com/profile/03753363363746376712noreply@blogger.com0tag:blogger.com,1999:blog-1578677178561645717.post-21072000719955568442012-11-30T03:10:00.001-08:002012-11-30T03:10:46.045-08:00Transitioning from Waterfall to Agile Testing – ‘Challenges & Approach’<h1 class="title" style="margin:0px 0px 20px;padding:0px;border:0px;outline:0px;font-size:28px;vertical-align:baseline;color:rgb(51,51,51);line-height:34px;font-family:Arial,Helvetica,sans-serif">Transitioning from Waterfall to Agile Testing – 'Challenges & Approach'</h1> <div class="entry" style="margin:0px;padding:0px;border:0px;outline:0px;vertical-align:baseline"><p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"> More and more software projects in the mainstream are embracing Agile, these days. It's important to understand how this paradigm shift impacts testing teams. And, what are the challenges testing teams encounter and how do they overcome them?</p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline">This blog post is an attempt to answer some of the questions above by taking inferences from a recent customer engagement of Aspire, where <span class="GRcorrect">Client's team</span> and Aspire's offshore team <span class="GRnoSuggestion GRcorrect">collaboratively</span> plans the move to Agile.</p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><strong style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline">Driving the transformation to Agile Testing</strong></p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline">Our customer is a leader in enterprise fraud management solutions in <span class="GRcorrect">US</span>. This customer has been engaged with us for more than 6 years now. Aspire is involved in Manual Testing and Test Automation of their suite of products. Because of a heightened need for shorter testing cycles and higher visibility, customer decided to move ahead with Agile.</p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><strong style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline">Primary Differences in working style- Waterfall Model vs. Agile</strong></p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline">In the waterfall model, requirements along with product documentation were entrusted to the team. There was enough time to understand requirements, perform exploratory testing, write test cases, and automate the QA. On the Test Automation front, the <span class="GRcorrect">builds</span> were stable, with the UI and functionality intact, making it easier for preparing good test scripts.</p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline">All these <span class="GRcorrect">practises</span> that were working earlier were not applicable for <span class="GRcorrect">agile approach</span>. So the team decided to pursue each problem one by one and analyze the strategy for agile testing and define new methodologies.</p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline">The typical activities that were carried out include:</p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><strong style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline">Requirements Understanding and Scheduling:</strong></p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline">Less Documentation/Regular Communication Meetings</em>: Meetings with the Product Owners, Scrum Masters and development team to understand the requirements one by one and validated our understanding by questioning defined Use Cases. The requirements were approached from the customer perspective.</p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline">Refining the requirements from the customer perspective: </em>The requirements were refined to the smallest possible unit. This enabled the team to commit the unit requirement into <span class="GRcorrect">specific Sprint</span>. Then the team proceeded onto writing test scenario with test cases as soon as the sprint started.</p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline">Estimate the effort required to complete the estimation: </em>Based on the refined requirements, <span class="GRcorrect">team</span> was able to precisely estimate the effort required to complete the design, development, QA and documentation. This helped everyone in the team to know when the preceding task (<span class="GRcorrect">say</span> <span class="GRcorrect">development</span>) would be completed and the work product would be available for succeeding tasks (say QA). This helps to track the schedule and negate any slippage.</p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><strong style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline">Test Automation:</strong></p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline">Transition to Test Automation was not as easy as it was in manual testing. Earlier, the team had a complete set of test cases and cushion of stable builds for categories like smoke and regression. This helped to create <span class="GRcorrect">module</span> based scripts with good <span class="GRcorrect">reusability</span>.</p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline">Development</em><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline"> & Test automation in Different Sprint:</em> Initially Test Automation was followed up <span class="GRcorrect">by</span> development activities and manual testing with a gap of one sprint. The team automated test cases of previous sprint, so that the team can minimize test script maintenance activities. Since this was not in tune with agile, we followed below approach.</p> <ul style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px 0px 0px 30px;border:0px;outline:0px;vertical-align:baseline;list-style:none"><li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc"> Developing feature, writing test cases and creating test scripts went in parallel for a particular requirement.</li><li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc"> Developer/Product Owner reviews the test cases based on scoped requirements</li><li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc">Test automation engineer starts writing stub test scripts and common functions based on <span class="GRcorrect">reviewed</span> test scripts</li> <li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc"><em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline">Transparent & Collaborative Approach:</em> Since each member <span class="GRcorrect">in</span> the team was aware of the team member's work and this helped to inform the changes better and avoid any rework in the sprints. The integrated work-approach within the team played a crucial role here.</li> </ul><p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><strong style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline">Regression testing:</strong></p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline">Delivering working products faster requires shorter end of the release activities. So we need to minimize the end of release activities (specifically regression testing). To accommodate this, we empowered our QA Infrastructure to perform regression quickly, as and when needed, without pushing it to the end of the release.</p> <ul style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px 0px 0px 30px;border:0px;outline:0px;vertical-align:baseline;list-style:none"><li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc"> At the end of each sprint, the test cases (which are mostly automated) were classified into categories like sanity, smoke, regression etc.</li><li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc"> The Smoke test cases in particular were executed as nightly tests which helped to uncover any major issues instantly.</li><li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc"> Importantly, these test suites had to be properly maintained to have confidence in the scripts. So the testing team worked with developers to maintain these tests where they will review the scripts and will also execute the tests wherever they feel something has changed/affected.</li> <li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc">This helped to extensively bring down the regression testing effort required at the end of each release</li> </ul><p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><strong style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline">Certifying alpha / beta kits</strong></p> <ul style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px 0px 0px 30px;border:0px;outline:0px;vertical-align:baseline;list-style:none"><li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc"> In the earlier waterfall model, resources spent dedicated time to certify alpha and beta kits.</li><li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc">With the current approach in regression testing and test automation, qualifications of kit were integrated and were implied part of sprint deliverables.</li> <li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc">Delivery of fully working product in each sprint</li></ul><p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"> <strong style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline">Team Work</strong></p><p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"> All these need consensus within <span class="GRcorrect">team</span> that "Quality of product is every ones responsibility". The emphasis has been on review of test cases and test scripts, involving ourselves in requirement grooming, giving feedback on usability and most importantly approaching testing with quality in mind.</p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><strong style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline">Conclusion:</strong></p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline">Agile helped us to improve ourselves and scale up in new areas. In the team, people who were used to performing manual testing alone, started developing automation scripts and reviewing scripts developed by others.</p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline">The team aggressively interacted and worked closely with developers and product owners.</p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline">And thus, they were able to deliver product quickly (~50% less time than waterfall model approach) and with good quality. Most importantly they are learning each day in agile and <em style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline">"Transforming Product Development"</em>.</p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline">Tags:</p><p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"> </p><p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> testing life cycle</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> testing methodology</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> testing <span class="GRcorrect">ppt</span></span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> methodology</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> testing process</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> model</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> testing <span class="GRcorrect">scrum</span></span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">scrum</span></span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> testing</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> testing life cycle</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> testing <span class="GRcorrect">scrum</span></span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> testing process activities</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> testing process <span class="GRcorrect">ppt</span></span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> testing interview questions</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">software</span> testing process agile development</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> testing process <span class="GRcorrect">wikipedia</span></span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> testing process examples</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> testing <span class="GRcorrect">scrum</span> <span class="GRnoSuggestion GRcorrect">ppt</span></span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">what</span> is agile testing <span class="GRcorrect">scrum</span> and sprint</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">testing</span> agile <span class="GRcorrect">scrum</span> methodology</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> <span class="GRcorrect">scrum</span> testing methodology</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">what</span> is <span class="GRcorrect">scrum</span> process in testing</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> test plan</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">what</span> is agile methodology</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">scrum</span> test plan</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">janet</span> <span class="GRcorrect">gregory</span> agile test plan template</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> test plan template</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">quality</span> assurance agile test plan</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> test plan forums</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> test <span class="GRcorrect">plan</span> quality methodologies</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">kind</span> agile test plan</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> test plan sample</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">test</span> plan in agile methodology</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> <span class="GRcorrect">scrum</span> testing process</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> testing process diagram</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> testing process <span class="GRcorrect">ppt</span></span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> software testing process</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> testing challenges</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> testing basics</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> regression testing</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">what</span> is agile testing in software testing</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> testing process <span class="GRcorrect">ppt</span></span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">testing</span> challenges in software testing</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">testing</span> in <span class="GRcorrect">agile environment</span></span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">what</span> is agile testing in software testing</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">regression</span> testing in agile</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">define</span> agile testing</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> testing benefits</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">role</span> of tester in agile</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">gile</span> test strategy</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> testing methodology wiki</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">testing</span> agile <span class="GRcorrect">scrum</span> methodology</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> testing methodology tutorial</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> testing methodology diagram</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">performance</span> testing agile methodology</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> methodology in software testing</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> model in testing</span></font></p> <p></p><p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><br></p></div> Software Testinghttp://www.blogger.com/profile/03753363363746376712noreply@blogger.com0tag:blogger.com,1999:blog-1578677178561645717.post-66677724574278606792012-11-30T03:08:00.001-08:002012-11-30T03:08:46.628-08:00Agile Automation<h1 class="title" style="margin:0px 0px 20px;padding:0px;border:0px;outline:0px;font-size:28px;vertical-align:baseline;color:rgb(51,51,51);line-height:34px;font-family:Arial,Helvetica,sans-serif">Agile Automation</h1><div class="entry" style="margin:0px;padding:0px;border:0px;outline:0px;vertical-align:baseline"> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline">According to the <a href="http://www.nl.capgemini.com/expertise/publicaties/world-quality-report-2011-2012/" style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;color:rgb(0,0,0);text-decoration:initial">World Quality Report 2010/2011</a> <span class="GRcorrect">by</span> Capgemini and HP over 60% of companies have either already adopted agile methods or are planning to do so in the near future. Agile Testing has been gaining popularity over the last few years due to several reasons such as the faster product development lifecycles and quicker Go to market cycles (GTM.</p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline">Some of the factors that affect <span class="GRcorrect">progress</span> and outcome of sprints are:</p> <ul style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px 0px 0px 30px;border:0px;outline:0px;vertical-align:baseline;list-style:none"><li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc"> Reduced Coverage: Compressed time frames in each sprint, forces the Test Engineers to test only the areas that have changed in the sprint. A complete regression cycle is not being conducted on the rest of the application leaving it susceptible to major flaws</li> <li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc">Traditional tools that were designed to work in a 'test last' environment, struggle to work in agile environment which is designed for 'test first, test continuously' model. New agile specific tools from Version One or Rally Software, can be used</li> <li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc">Agile Testing allows requirements to creep in any time during any phase of the project and it will be accommodated in the already allotted functionalities to be validated</li> </ul><p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline">To address these issues, a suite of automated testing solutions can be formulated that enable smarter sprints that help to meet deadlines and timely qualitative releases.</p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline">And some of the best practices that can yield great results for such short GTMs and provide quick ROI are:</p> <ul style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px 0px 0px 30px;border:0px;outline:0px;vertical-align:baseline;list-style:none"><li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc"> Refactoring/Regression-Performing Bug fixes, refactoring old code and running extensive regression testing, every few weeks to focus on stability, takes care of missed bugs during <span class="GRcorrect">ongoing testing process</span></li> <li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc">Testing from a Customer Point of View: Sharing good stories with customer relevant material, with the development team as well as the testing team</li> <li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc">Test ideas can be compiled <span class="GRcorrect">in</span> a presentation shared with the developers and developers can take <span class="GRcorrect">live</span> feedback helping developers start thinking about whether their software will pass such tests</li> <li style="margin:0px;padding:0px;border:0px;outline:0px;font-size:14px;vertical-align:baseline;list-style-type:disc">Frequently run tests or procedures, or those that take the most time, if automated, can generate a big ROI</li> </ul><p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline">Adopting these core points can hugely impact the overall testing process.</p> <p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><br></p><p style="color:rgb(85,85,85);font-family:Helvetica,Arial,sans-serif;font-size:14px;line-height:1.5em;margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"> <span style="font-size:14px;line-height:1.5em">Tags:</span></p><p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"></p><p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"> <font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> testing life cycle</span></font></p><p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"> <font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> testing methodology</span></font></p><p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"> <font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> testing <span class="GRcorrect">ppt</span></span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> methodology</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> testing process</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> model</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> testing <span class="GRcorrect">scrum</span></span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">scrum</span></span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> testing</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> testing life cycle</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> testing <span class="GRcorrect">scrum</span></span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> testing process activities</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> testing process <span class="GRcorrect">ppt</span></span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> testing interview questions</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">software</span> testing process agile development</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> testing process <span class="GRcorrect">wikipedia</span></span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> testing process examples</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> testing <span class="GRcorrect">scrum</span> <span class="GRnoSuggestion GRcorrect">ppt</span></span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">what</span> is agile testing <span class="GRcorrect">scrum</span> and sprint</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">testing</span> agile <span class="GRcorrect">scrum</span> methodology</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> <span class="GRcorrect">scrum</span> testing methodology</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">what</span> is <span class="GRcorrect">scrum</span> process in testing</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> test plan</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">what</span> is agile methodology</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">scrum</span> test plan</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">janet</span> <span class="GRcorrect">gregory</span> agile test plan template</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> test plan template</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">quality</span> assurance agile test plan</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> test plan forums</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> test <span class="GRcorrect">plan</span> quality methodologies</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">kind</span> agile test plan</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> test plan sample</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">test</span> plan in agile methodology</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> <span class="GRcorrect">scrum</span> testing process</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> testing process diagram</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> testing process <span class="GRcorrect">ppt</span></span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> software testing process</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> testing challenges</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> testing basics</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> regression testing</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">what</span> is agile testing in software testing</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> testing process <span class="GRcorrect">ppt</span></span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">testing</span> challenges in software testing</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">testing</span> in <span class="GRcorrect">agile environment</span></span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">what</span> is agile testing in software testing</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">regression</span> testing in agile</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">define</span> agile testing</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">agile</span> testing benefits</span></font></p> <p style="margin:0px 0px 1.5em;padding:0px;border:0px;outline:0px;vertical-align:baseline"><font color="#555555" face="Helvetica, Arial, sans-serif"><span style="font-size:14.44444465637207px;line-height:20.981481552124023px"><span class="GRcorrect">role</span> of tester in agile</span></font></p> <p></p></div> Software Testinghttp://www.blogger.com/profile/03753363363746376712noreply@blogger.com0