tag:blogger.com,1999:blog-10207447869560208302011-02-09T19:39:53.033-08:00Software Testing StuffAn eXcellent web log and online resource center of Software TestingPhttp://www.blogger.com/profile/11295088633938021751noreply@blogger.comBlogger174125tag:blogger.com,1999:blog-1020744786956020830.post-43259296313038906802010-11-02T05:43:00.000-07:002010-11-02T02:08:57.063-07:00Software Testing Openings in Gurgaon<b>Date: </b>02-Nov-10 <br />There few urgent openings for software test professionals having experience from 6 months to 1 year.<br /><b>Location:</b> Gurgaon <br /><b>If you are interested, please send your cv at jobs_india@yahoo.com with the subject line as “Testing | Years of Experience”. Kindly mention the below details:</b><br /><ul><li>Current CTC: </li><li>Expected CTC: </li><li>Notice Period: </li></ul><b></b>Below is the job description:<br /><ul><li>Experience in testing of web based applications</li><li>Experience in Manual Functional and System Testing</li><li> Experience in test case design and execution</li><li> Experience in regression testing, re-testing, integration testing, rapid testing </li><li>Bug Reporting & Tracking</li><li>Good understanding of software development life cycle models</li><li>Good communication skills</li><li>Knowledge of automation tools will be an added advantage</li></ul><b>If you are interested, please send your cv at jobs_india@yahoo.com with the subject line as “Testing | Years of Experience”. </b><br />=========================================================== <br /><b>Date: </b>May 06, 2008<br />There is an opening for Test Lead. Below are the job details:<br /><b>Experience: </b>3 - 6 Years <br /><b>Desired Qualification:</b> UG - B.Tech/B.E. - Any Specialization; BCA - Computers<br />Candidate should have experince in Test Planning and Test Execution. <br />Interested candidates can send their profiles directly to <b>narender@eminence.co.in</b><br />=========================================================== <br />=========================================================== <br /><b>Date:</b> May 03, 2008<br />There is an opening for Sr. Tester in United Health Group. <br /><b>Skill Set:</b> Automation QTP<br />If interested kindly mail your resume at <b>Sharad@recruitingpundits.co.in</b> ASAP. Kindly mention the following details also: - <br /><ul><li>Skill Sets: </li><li>Current CTC: </li><li>Expected CTC: </li><li>Notice Period: </li></ul>=========================================================== <br /><b>Also See:</b><br /><ul><li><a href="http://www.softwaretestingstuff.com/2007/10/current-openings-in-delhi.html"><b>Openings in Delhi</b></a><b> </b></li><li><a href="http://www.softwaretestingstuff.com/2007/10/openings-in-noida.html"><b>Openings in Noida</b></a><b> </b></li><li><a href="http://www.softwaretestingstuff.com/2007/10/openings-in-us-singapore.html"><b>Openings in US / Singapore</b></a> </li></ul><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1020744786956020830-4325929631303890680?l=www.softwaretestingstuff.com' alt='' /></div>
<p><a href="http://feedads.g.doubleclick.net/~a/0ga7U7oOjkCOcF95gBqHxvMGBuU/0/da"><img src="http://feedads.g.doubleclick.net/~a/0ga7U7oOjkCOcF95gBqHxvMGBuU/0/di" border="0" ismap="true"></img></a><br/>
<a href="http://feedads.g.doubleclick.net/~a/0ga7U7oOjkCOcF95gBqHxvMGBuU/1/da"><img src="http://feedads.g.doubleclick.net/~a/0ga7U7oOjkCOcF95gBqHxvMGBuU/1/di" border="0" ismap="true"></img></a></p><img src="http://feeds.feedburner.com/~r/software_testing_stuff/~4/RmhwJ_wfioQ" height="1" width="1"/>Phttp://www.blogger.com/profile/11295088633938021751noreply@blogger.com0http://www.softwaretestingstuff.com/2007/10/openings-in-gurgaon.htmltag:blogger.com,1999:blog-1020744786956020830.post-71846687410483352012010-10-05T01:37:00.001-07:002010-10-05T01:37:52.013-07:00HP Quality Center - Defect/Bug Tracking<p><strong>Introduction:</strong></p> <ul> <li>HP quality center is web-based test management tool</li> <li>QC is used to manage the application testing process</li> <li>QC is used to define releases, specifying requirements, planning tests, executing tests, tracking defects, alerting on changes, and analyzing results</li> <li>QC also shows you how to customize your project</li> <li>Defect: Anything that is extra or missing or wrong in application is termed as defect</li> <li>QC helps you to add defects to application when found and track the defect repair progression.</li> <li>QC provides a central defect tracking system that can be used by testing and development teams to resolve defects</li> <strong>QC testing process includes 5 phases:</strong> <li>Specifying release</li> <li>Specifying requirements</li> <li>Planning Tests</li> <li>Running Tests</li> <li>Tracking Defects</li> <strong>Defect Modules:</strong> <li>QC Defect module provides complete system for logging, tracking, managing, and analyzing application defects</li> <li>QC Defect tracking tools are organized into: Defects grid, Grid filter, Description, Attachments, History</li> <strong>Defect Logging: Steps to Log a defect</strong> <li>In Defect module, click New Defect</li> <li>New defect dialog box contains data fields and multiple tabbed pages. This multiple tabbed pages are custom-defined by QC administrator for your project</li> <li>You can also add attachments to provide more information about the defect. QC supports five types of attachments</li> <li>Click Submit to save the defect to your project database</li> <strong>Defect Organizing - Grid filter provides two ways to organize defect grid:</strong> <li>Use entry boxes under each field heading in grid filter to select the criteria for filtering the data in the defects grid</li> <li>Use the Filter dialog box to set a filter condition</li> <li>To clear filter criteria, click the Clear Filter/Sort button</li> <strong>Defect Status:</strong> <li>New: Default status when defect is reported</li> <li>Open: Indicates defect is assigned to review</li> <li>Reopen: Indicates testing team reopened the defect which was closed</li> <li>Fixed: Indicates defect is verified</li> <li>Closed: Defect is closed and waiting fro approval by tester</li> <li>Rejected: Defect is rejected , rationale fore rejecting defect to be provided</li> <strong>Defect association with other entities - Defects can be associated with the following entities:</strong> <li>Requirement</li> <li>Test</li> <li>Test set</li> <li>Test instance</li> <li>Test run</li> <li>Test steps</li> <li>Other Defect</li> <strong>This linkage of defects with entities enables to</strong> <li>Trace your defects from perspective of QC entities</li> <li>Search defects that are related to specific QC entities</li> <li>Link multiple entities of same type to the same defect</li> <strong>Defect Requirement:</strong> <li>Associating defects with test requirements will help to ensure consistency throughout the testing process</li> <li>The defect-requirement association enables us to utilize the status of defects to determine whether requirements have been met</li> <li>A requirement can be associated with more than one defect</li> <li>Either a existing defect can be associated with the requirement or new defect can be added to requirement</li> <strong>Defect Test:</strong> <li>Association of defect with test helps to ensure defect traceability throughout the testing process. A defect may be indirectly linked to a test through other entities, such as a test instance, a test run, or a test step</li> <li>Tests from Test plan module can be associated with defects that have been logged in the Defects module</li> <strong>Defect Matching:</strong> <li>Matching defects enables you to eliminate similar and duplicate defects in your project</li> <li>Each time you add a new defect, Quality Center stores lists of keywords from the Summary and Description fields</li> <li>When you search for similar defects, keywords in these fields are matched against other defects</li> <li>Note that keywords must be more than two characters and letter case does not affect your results</li> <strong>Updating the defects:</strong> <li>A defect can be regularly updated to record all the information about an issue.</li> <li>A defect can be regularly updated to record decisions made as different individuals review the defect.</li> <li>While updating the defect ,click Details to update specific data fields.</li> <li>Click Attachments to attach files to defect.</li> <li>Click Linked entities and then click the Defects tab to link a defect to another defect.</li> <li>Click Others tab to link a defect to other entities such as a test or test set.</li> <li>Click History to view the changes made to defect.</li> <strong>Favorite view:</strong> A favorite view is a view of a Quality Center window with the settings you applied to it. Steps to create favorite view in defects grid: <li>Defect module should be displayed</li> <li>Define a filter to view defects, Click the Set Filter/Sort button. The Filter dialog box opens.</li> <li>Click the Filter Condition box, Click the browse button. The Select Filter Condition dialog box opens. Click OK to close the Select Filter Condition dialog box. Click OK to apply your chosen filter.</li> <li>Add a favorite view. In the Favorites menu, choose Add to Favorites. The Add Favorite dialog box opens.</li> <img title="HP Quality Center - Defect/Bug Tracking" style="border-right: 0px; border-top: 0px; display: block; float: none; margin-left: auto; border-left: 0px; margin-right: auto; border-bottom: 0px" height="308" alt="HP Quality Center - Defect/Bug Tracking" src="http://lh5.ggpht.com/_ansP04Rcsso/TKrj3SdtZRI/AAAAAAAAATE/hsMFwQls0oU/image%5B5%5D.png?imgmax=800" width="544" border="0" /></ul> <div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1020744786956020830-7184668741048335201?l=www.softwaretestingstuff.com' alt='' /></div>
<p><a href="http://feedads.g.doubleclick.net/~a/1nzdvOry6KJRm0Ab2uRBoOEF87s/0/da"><img src="http://feedads.g.doubleclick.net/~a/1nzdvOry6KJRm0Ab2uRBoOEF87s/0/di" border="0" ismap="true"></img></a><br/>
<a href="http://feedads.g.doubleclick.net/~a/1nzdvOry6KJRm0Ab2uRBoOEF87s/1/da"><img src="http://feedads.g.doubleclick.net/~a/1nzdvOry6KJRm0Ab2uRBoOEF87s/1/di" border="0" ismap="true"></img></a></p><img src="http://feeds.feedburner.com/~r/software_testing_stuff/~4/G_Cw5_dYrxc" height="1" width="1"/>Phttp://www.blogger.com/profile/11295088633938021751noreply@blogger.com0http://www.softwaretestingstuff.com/2010/10/hp-quality-center-defectbug-tracking.htmltag:blogger.com,1999:blog-1020744786956020830.post-25657789257467723562010-10-01T04:02:00.001-07:002010-10-01T04:02:54.858-07:00Common Problems in Bug Tracking<p>Working with different stake holders in a project, teams would be facing difficulty in keeping transparency on bugs because of following common problems:</p> <ul> <li><strong>Lack of process for bug logging:</strong> Typical scenario like testing & development teams are not well educated on severities & priorities to be used and their importance. </li> <li>No clear communication to testing team on required fields as part of bug logging. Testers may skip to mention required data like reproducible steps or may skip to attached screen shots. </li> <li>Lack of a standard bug tracking / logging template. If all team members will follow their own template to describe defects, it may lead to discrepancy at a later stage. </li> <li>Team will not have a dedicated SPOC communicate defects to all the stake holders </li> <li>Team will follow their own communication channel to communicate defects using phone/email. Sometimes they won’t even log defect after communicating issue to Dev and getting fix on the fly. </li> <li>Team will not maintain appropriate statuses for defects. Even after they retest and close some times defect still shows as ‘Ready for Test’. </li> <li><b>Improper Defect Triage/Communication Process</b>: Triage process allows all stake holders to gather at one place (Physically or virtually) to discuss on all open defects and decide on action items. Without this call/meeting in regular intervals it will be difficult to have a common understanding on issues/defects or reasons for blocking of test execution. </li> <li>Test team some time will not have control on Test environments and they would not know when the fix is deployed in to test environment. Sometimes Dev team adhocly performs certain actions on test environment and fixes the issue. Not having complete control on Test Environment would cause so many issues in ensuring quality of defect retest. </li> In today’s market conditions, we have so many Freeware tools available for Test/Defect management tools. Some projects also afford to have cost assigned to Defect Management tools and buy required amount of licenses. Even after having a tool in place, if the process is not defined about how to utilize the tool then we will have many challenges to be faced in handling Defects. </ul> <ul>The below are the common blind spots identified in the poor or No process scenarios. <li>No Training on tool(s) to the team</li> <li>No clear guidelines on the process to the team</li> <li>No availability of tool till the execution starts</li> <li>No planning about how many licenses required for the team</li> <li>No Communication process defined</li> <li>No Triage process defined</li> <p> All the above will lead to poor reporting of the Defect status and eventually Test Execution status.</p> </ul> <div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1020744786956020830-2565778925746772356?l=www.softwaretestingstuff.com' alt='' /></div>
<p><a href="http://feedads.g.doubleclick.net/~a/1jzSqFOaot1Uk61uJGi6JwES5MY/0/da"><img src="http://feedads.g.doubleclick.net/~a/1jzSqFOaot1Uk61uJGi6JwES5MY/0/di" border="0" ismap="true"></img></a><br/>
<a href="http://feedads.g.doubleclick.net/~a/1jzSqFOaot1Uk61uJGi6JwES5MY/1/da"><img src="http://feedads.g.doubleclick.net/~a/1jzSqFOaot1Uk61uJGi6JwES5MY/1/di" border="0" ismap="true"></img></a></p><img src="http://feeds.feedburner.com/~r/software_testing_stuff/~4/soA19tLZ0tI" height="1" width="1"/>Phttp://www.blogger.com/profile/11295088633938021751noreply@blogger.com0http://www.softwaretestingstuff.com/2010/10/common-problems-in-bug-tracking.htmltag:blogger.com,1999:blog-1020744786956020830.post-77879921279905777672010-09-29T01:17:00.000-07:002010-09-29T01:19:55.713-07:00Bug or Incident or Defect Communication & TriageTest Manager/Lead has to take the responsibility of communicating the defects to the respective Dev teams and all other stake holders. The process should be defined in such a way as depending on the severity of the defect the SLA for turnaround times should exist.<br /><br />The bug tracking & management tools should trigger an e-mail to the assigned team when the defect is assigned. If no tool is used Test leads will be sending e-mail communication to the Dev teams.<br /><br />While communicating bugs, always remember:<br /><ul><li>Do not share the actual Defect sheets through emails. Create share location and share the location details. This will avoid different people working on different versions of sheets.</li><li>Make sure Dev team also have write access to the share point and allow them to add comments and change the status of the defect</li></ul>Depending on the time lines and the number of defects raised, the schedule for Triage has to be defined. Ideal way is to have this meeting every end of the day. Discuss all the defects and decide the actions.<br /><br />For an effective bug triage, always remember:<br /><ul><li>Set up the conference call/Meeting and invite all the intended recipients.</li><li>Share the list of defects and their details to the Triage participants well in advance of meeting.</li><li>Make sure one representation is available from all groups.</li><li>Prepare an MOM for the Triage and log all the actions</li><li>Discuss on Actions pending from previous meetings.</li><li>Discuss defects and create new actions and identify the responsible person for each action.</li><li>Share the MOM with all the stake holders.</li></ul><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1020744786956020830-7787992127990577767?l=www.softwaretestingstuff.com' alt='' /></div>
<p><a href="http://feedads.g.doubleclick.net/~a/hkPe3zNXwgaIw_8Tx0kQEsG41ko/0/da"><img src="http://feedads.g.doubleclick.net/~a/hkPe3zNXwgaIw_8Tx0kQEsG41ko/0/di" border="0" ismap="true"></img></a><br/>
<a href="http://feedads.g.doubleclick.net/~a/hkPe3zNXwgaIw_8Tx0kQEsG41ko/1/da"><img src="http://feedads.g.doubleclick.net/~a/hkPe3zNXwgaIw_8Tx0kQEsG41ko/1/di" border="0" ismap="true"></img></a></p><img src="http://feeds.feedburner.com/~r/software_testing_stuff/~4/o6UT4dZN2qw" height="1" width="1"/>Phttp://www.blogger.com/profile/11295088633938021751noreply@blogger.com0http://www.softwaretestingstuff.com/2010/09/bug-or-incident-or-defect-communication.htmltag:blogger.com,1999:blog-1020744786956020830.post-87706114800335358762010-09-28T02:33:00.000-07:002010-09-28T07:21:33.435-07:00Unit Testing - Best Practices & TechniquesUnit testing is a software development process in which the smallest testable parts of an application, called units, are individually and independently scrutinized for proper operation. The primary goal of unit testing is to take the smallest piece of testable software in the application, isolate it from the remainder of the code, and determine whether it behaves exactly as expected. Each unit is tested separately before integrating them into modules to test the interfaces between modules.By means of effective Unit testing large percentage of defects are identified. Unit testing is performed by developers.<br /><br />Each module that is developed by designers need to be tested individually to verify proper operation so that any faulty module can be fixed immediately rather than let it exist and then cause some major issue in the integration phase. Once all of the units in a program have been found to be working efficiently and without any bugs, larger components of the program can be evaluated by means of integration testing. Though Unit testing may be time consuming, tedious and requires thoroughness on the part of the development team, but in the long run it can avoid major pitfalls in the software.<br /><br /><b>Benefits of unit testing:</b><br /><ul><li>The modular approach during Unit testing eliminates the dependency on other modules during testing. </li><li>We can test parts of a project with out waiting for the other parts to be available.</li><li>Designers can identify and fix problem immediately, as the modules are best known to them. This helps in fixing multiple problems simultaneously.</li><li>Cost of fixing a defect identified during the early stages is less compared to that during later stage.</li><li>Debugging is simplified. </li><li>Structural coverage of code is higher.</li><li>Unit testing is more cost effective compared to the other stages of testing</li></ul><b>Misconceptions about Unit Testing:</b><br /><ul><li><b>Integration Tests will Catch all the Bugs Anyway:</b> This is one of the common misconceptions of designers. Complexity of the issue rises while it passes through various testing cycles and then when the bug is raised during the later stages, the resolution time will be high as the scope of the bug widens. It is better to weed off the crop before it poisons the whole farm.</li><li><b><span style="color: black; font-family: "Arial","sans-serif"; font-size: 10pt;">Programmers Dilemma</span><span style="font-family: "Arial","sans-serif"; font-size: 10pt;">: </span></b><span style="font-family: "Arial","sans-serif"; font-size: 10pt;">Most designers believe Unit testing is not actually required as it is time consuming. They feel they are too good programmers and their software doesn’t need Unit tests. But i</span><span style="font-family: "Arial","sans-serif"; font-size: 10pt;">n the real world, everyone makes mistakes. Real software systems are much more complex. Software behavior various in different environment and with different scenarios. Coding is not a one pass process. Enhancements to the code can be made only when we know the existing module is functioning as expected.</span></li><li><b><span style="font-family: "Arial","sans-serif"; font-size: 10pt;">It Consumes Too Much Time: </span></b><span style="font-family: "Arial","sans-serif"; font-size: 10pt;">Developers are often in a hurry to complete their code and integrate it. Unit Testing is most often considered a useless activity, as they feel anyways the code will be tested by QA. </span><span style="font-family: "Arial","sans-serif"; font-size: 10pt;">There is no point in having a system which works but not exactly as it is supposed to function and is to be full of bugs. Practically, such an approach to development will often result in software which will not even run. The net result is that a lot of time will be spent tracking down relatively simple bugs which are wholly contained within particular units. Individually, such bugs may be trivial, but collectively they result in an excessive period of time integrating the software to produce a system which is unlikely to be reliable. This can also lead to failure to meet the required deadlines. </span></li></ul><b><span style="font-family: "Arial","sans-serif"; font-size: 10pt;"></span></b><span style="font-family: "Arial","sans-serif"; font-size: 10pt;"><b>Unit Testing Best Practices:</b></span><br /><ul><li><span style="font-family: "Arial","sans-serif"; font-size: 10pt;">Ensure each Unit Test case is independent of each other. As the software is prone to changes during the Unit Testing due to enhancements/changes to the requirements. Hence any given behavior should be specified in one and only one test. Otherwise if you later change that behavior, you’ll have to change multiple tests.</span></li><li><span style="font-family: "Arial","sans-serif"; font-size: 10pt;">Test only one code at a time. It is always recommended to test each of the modules independently and not while all are chained together. Otherwise you will have lots of overlap between tests and changes to one unit may effect all other modules and cause the software to fail.</span></li><li><span style="font-family: "Arial","sans-serif"; font-size: 10pt;">Name your unit tests clearly and consistently. Ensure that your test cases are easily readable so that anyone picking up Unit test cases can execute them without any issues. Ensure the test case nomenclature is consistent throughout.</span></li><li><span style="font-family: "Arial","sans-serif"; font-size: 10pt;">Before changing a module interface or implementation, make sure that the module has test cases and that it passes its tests before changing the implementation. This way you can know that your changes didn't break anything.</span></li><li><span style="font-family: "Arial","sans-serif"; font-size: 10pt;">Always ensure the bug identified during Unit Testing is fixed before moving it to the next phase.</span></li></ul><span style="font-family: "Arial","sans-serif"; font-size: 10pt;"><b>Unit Testing Techniques:</b> Structural, Functional & Error based Techniques</span><br /><span style="font-family: "Arial","sans-serif"; font-size: 10pt;"> </span><br /><b><span style="font-family: "Arial","sans-serif"; font-size: 10pt;">Structural </span></b><span style="font-family: "Arial","sans-serif"; font-size: 10pt;"><b>Techniques:</b> It is a White box testing technique that uses an internal perspective of the system to design test cases based on internal structure. It requires programming skills to identify all paths through the software. The tester chooses test case inputs to exercise paths through the code and determines the appropriate outputs. Major Structural techniques are:</span><br /><ul><li><span style="font-family: "Arial","sans-serif"; font-size: 10pt;"><b>Statement Testing:</b> A test strategy in which each statement of a program is executed at least once.</span> </li><li><b>Branch Testing: </b>Testing in which all branches in the program source code are tested at least once.</li><li><b>Path Testing: </b>Testing in which all paths in the program source code are tested at least once.</li><li><b>Condition Testing:</b> Condition testing allows the programmer to determine the path through a program by selectively executing code based on the comparison of a value <span style="font-family: "Arial","sans-serif"; font-size: 10pt;"> </span></li><li><span style="font-family: "Arial","sans-serif"; font-size: 10pt;"><b>Expression Testing:</b> Testing in which the application is tested for different values of Regular Expression.</span></li></ul><span style="font-family: "Arial","sans-serif"; font-size: 10pt;"><b>Functional testing techniques:</b> These are Black box testing techniques which tests the functionality of the application. Some functionality testing techniques are:</span><br /><ul><li><span style="font-family: "Arial","sans-serif"; font-size: 10pt;"><b>Input domain testing:</b> This testing technique concentrates on size and type of every input object in terms of boundary value analysis and Equivalence class.</span> <b> </b></li><li><b>Boundary Value: </b>Boundary value analysis is a software testing design technique in which tests are designed to include representatives of boundary values.<span style="font-family: "Arial","sans-serif"; font-size: 10pt;"> <b> </b></span></li><li><span style="font-family: "Arial","sans-serif"; font-size: 10pt;"><b>Syntax checking:</b> This is a technique which is used to check the Syntax of the application.</span><span style="font-family: "Arial","sans-serif"; font-size: 10pt;"> </span></li><li><span style="font-family: "Arial","sans-serif"; font-size: 10pt;"><b>Equivalence Partitioning:</b> This is a software testing technique that divides the input data of a software unit into partition of data from which test cases can be derived</span></li></ul><span style="font-family: "Arial","sans-serif"; font-size: 10pt;"><b>Error based Techniques:</b> The best person to know the defects in his code is the person who has designed it.<br />Few of the Error based techniques are:</span><br /><ul><li><span style="font-family: "Arial","sans-serif"; font-size: 10pt;"><b>Fault seeding</b> techniques can be used so that known defects can be put into the code and tested until they are all found.</span></li><li><span style="font-family: "Arial","sans-serif"; font-size: 10pt;"><b>Mutation Testing:</b> This is done by mutating certain statements in your source code and checking if your test code is able to find the errors. Mutation testing is very expensive to run, especially on very large applications.</span></li><li><span style="font-family: "Arial","sans-serif"; font-size: 10pt;"><b>Historical Test data:</b> This technique calculates the priority of each test case using historical information from the previous executions of the test case. </span></li></ul><span style="font-family: "Arial","sans-serif"; font-size: 10pt;">Careful approach to Unit testing helps detecting many bugs at a stage of the software development where they can be corrected economically. It is a tedious process when bugs are detected and corrected at later stages of software development as fixing the bugs is difficult, time consuming and costly. Efficiency and quality are best served by testing software as early in the life cycle. Whenever any changes are made to the software we need to ensure regression testing is performed. Testing strategies like thorough unit testing, good management of the testing process, and appropriate use of tools helps in maximizing the effectiveness of testing effort. Effective unit testing is all part of developing a very high quality software product which can benefit the organization on a whole.</span><span style="font-family: "Arial","sans-serif"; font-size: 10pt;"> </span><span style="font-family: "Arial","sans-serif"; font-size: 10pt;"></span><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1020744786956020830-8770611480033535876?l=www.softwaretestingstuff.com' alt='' /></div>
<p><a href="http://feedads.g.doubleclick.net/~a/iu1j8CuWaiYSRfCOUfUOcjHd2nw/0/da"><img src="http://feedads.g.doubleclick.net/~a/iu1j8CuWaiYSRfCOUfUOcjHd2nw/0/di" border="0" ismap="true"></img></a><br/>
<a href="http://feedads.g.doubleclick.net/~a/iu1j8CuWaiYSRfCOUfUOcjHd2nw/1/da"><img src="http://feedads.g.doubleclick.net/~a/iu1j8CuWaiYSRfCOUfUOcjHd2nw/1/di" border="0" ismap="true"></img></a></p><img src="http://feeds.feedburner.com/~r/software_testing_stuff/~4/1yhUIZly4GM" height="1" width="1"/>Phttp://www.blogger.com/profile/11295088633938021751noreply@blogger.com0http://www.softwaretestingstuff.com/2010/09/unit-testing-best-practices-techniques.htmltag:blogger.com,1999:blog-1020744786956020830.post-27417448137006753492010-07-23T23:54:00.000-07:002010-07-23T23:55:09.119-07:00How to do Cookies TestingBelow is a list of major scenarios for cookies testing of a website. Multiple test cases can be generated from <br />these scenarios by performing various combinations.<br /><ol><li>Check if the application is writing cookies properly or not.</li><li>Test to make sure that no personal or sensitive data is stored in the cookie. If it is there in cookies, it should be in encrypted format.</li><li>If the application under test is a public website, there should not be overuse of cookies. It may result in loss of website traffic if browser is prompting for cookies more often.</li><li>Close all browsers, delete all previously written cookies and disable the cookies from your browser settings. Navigate or use that part of web site which use cookies. It should display appropriate messages like "For smooth functioning of this site please enable cookies on your browser."</li><li>Set browser options to prompt whenever cookie is being stored / saved in your system. Navigate or use that part of web site which use cookies. It will prompt and ask if you want to accept or reject the cookie. Application under test should display an appropriate message if you reject the cookies. Also, check that if pages are getting crashed or data is getting corrupted.</li><li>Close all browsers windows and manually delete all cookies. Navigate various web pages and check and see if these web pages show unexpected behavior.</li><li>Edit few cookies manually in notepad or some other editor. Make modifications like alter the cookie content, name of the cookie, change expiry date etc. Now, test the site functionality. Corrupted cookies should not allow to read the data inside it.</li><li>Cookies written by one web site should not be accessible by other website.</li><li>If you are testing an online shopping portal, Check if reaching to your final order summary page deletes the cookie of previous page of shopping cart properly and no invalid action or purchase got executed from same logged in user.</li><li>Check if the application under test is writing the cookies properly on different browsers as intended and site works properly using these cookies. This test can be done on browsers like different versions of internet explorer, Mozilla Firefox, Netscape, Opera etc.</li><li>If the application under test is using cookies to maintain the logging state for users. Check if some id is being displayed in the address bar. Now, change the id & press enter. It should display an access denied message and and you should not be able to see other user's account.</li></ol><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1020744786956020830-2741744813700675349?l=www.softwaretestingstuff.com' alt='' /></div>
<p><a href="http://feedads.g.doubleclick.net/~a/yDeLO5jn8cMCUIp9PUqR3E32idM/0/da"><img src="http://feedads.g.doubleclick.net/~a/yDeLO5jn8cMCUIp9PUqR3E32idM/0/di" border="0" ismap="true"></img></a><br/>
<a href="http://feedads.g.doubleclick.net/~a/yDeLO5jn8cMCUIp9PUqR3E32idM/1/da"><img src="http://feedads.g.doubleclick.net/~a/yDeLO5jn8cMCUIp9PUqR3E32idM/1/di" border="0" ismap="true"></img></a></p><img src="http://feeds.feedburner.com/~r/software_testing_stuff/~4/DaTKOts2OQk" height="1" width="1"/>Phttp://www.blogger.com/profile/11295088633938021751noreply@blogger.com0http://www.softwaretestingstuff.com/2010/07/how-to-do-cookies-testing.htmltag:blogger.com,1999:blog-1020744786956020830.post-53674653062266904682009-12-02T01:26:00.001-08:002009-12-09T05:21:49.304-08:00How to do System TestingTesting the software system or software application as a whole is referred to as System Testing of the software. System testing of the application is done on complete application software to evaluate software's overall compliance with the business / functional / end-user requirements. The system testing comes under black box software testing. So, the knowledge of internal design or structure or code is not required for this type of software testing. <br /><a name='more'></a><br />In system testing a software test professional aims to detect defects or bugs both within the interfaces and also within the software as a whole. However, the during integration testing of the application or software, the software test professional aims to detect the bugs / defects between the individual units that are integrated together.<br /><br />During system testing, the focus is on the software design, behavior and even the believed expectations of the customer. So, we can also refer the system testing phase of software testing as investigatory testing phase of the software development life cycle.<br /><br /><b>At what stage of SDLC the System Testing comes into picture:</b><br /><br />After the integration of all components of the software being developed, the whole software system is rigorously tested to ensure that it meets the specified business, functional & non-functional requirements. System Testing is build on the unit testing and integration testing levels. Generally, a separate and dedicated team is responsible for system testing. And, system testing is performed on stagging server.<br /><br /><b>Why system testing is required:</b><br /><ul><li>It is the first level of software testing where the software / application is tested as a whole. </li><li>It is done to verify and validate the technical, business, functional and non-functional requirements of the software. It also includes the verification & validation of software application architecture. </li><li>System testing is done on stagging environment that closely resembles the production environment where the final software will be deployed. </li></ul><b>Entry Criteria for System Testing:</b> <br /><ul><li>Unit Testing must be completed </li><li>Integration Testing must be completed </li><li>Complete software system should be developed </li><li>A software testing environment that closely resembling the production environment must be available (stagging environment). </li></ul><b>System Testing in seven steps: </b><br /><ol><li>Creation of System Test Plan </li><li>Creation of system test cases </li><li>Selection / creation of test data for system testing </li><li>Software Test Automation of execution of automated test cases (if required) </li><li>Execution of test cases </li><li>Bug fixing and regression testing </li><li>Repeat the software test cycle (if required on multiple environments) <b> </b></li></ol><b>Contents of a system test plan:</b> The contents of a software system test plan may vary from organization to organization or project to project. It depends how we have created the software test strategy, project plan and master test plan of the project. However, the basic contents of a software system test plan should be:<br /><br />- Scope <br />- Goals & Objective <br />- Area of focus (Critical areas) <br />- Deliverables <br />- System testing strategy <br />- Schedule <br />- Entry and exit criteria <br />- Suspension & resumption criteria for software testing<br />- Test Environment <br />- Assumptions <br />- Staffing and Training Plan <br />- Roles and Responsibilities <br />- Glossary<br /><br /><b>How to write system test cases: </b>The system test cases are written in a similar way as we write functional test cases. However, while creating system test cases following two points needs to be kept in mind:<br /><br />- System test cases must cover the use cases and scenarios <br />- They must validate the all types of requirements - technical, UI, functional, non-functional, performance etc.<br /><br />As per Wikipedia, there are total of 24 types of testings that needs to be considered during system testing. These are:<br /><br />GUI software testing, Usability testing, Performance testing, Compatibility testing, Error handling testing, Load testing, Volume testing, Stress testing, User help testing, Security testing, Scalability testing, Capacity testing, Sanity testing, Smoke testing, Exploratory testing, Ad hoc testing, Regression testing, Reliability testing, Recovery testing, Installation testing, Idem potency testing, Maintenance testing, Recovery testing and failover testing, Accessibility testing<br /><br /><b>The format of system test cases contains:</b><br /><ul><li>Test Case ID - a unique number </li><li>Test Suite Name </li><li>Tester - name of tester who execute of write test cases </li><li>Requirement - Requirement Id or brief description of the functionality / requirement </li><li>How to Test - Steps to follow for execution of the test case </li><li>Test Data - Input Data </li><li>Expected Result </li><li>Actual Result </li><li>Pass / Fail </li><li>Test Iteration </li></ul><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1020744786956020830-5367465306226690468?l=www.softwaretestingstuff.com' alt='' /></div>
<p><a href="http://feedads.g.doubleclick.net/~a/3ewmATAE9y0SLtKhMjyQ91e7Sbk/0/da"><img src="http://feedads.g.doubleclick.net/~a/3ewmATAE9y0SLtKhMjyQ91e7Sbk/0/di" border="0" ismap="true"></img></a><br/>
<a href="http://feedads.g.doubleclick.net/~a/3ewmATAE9y0SLtKhMjyQ91e7Sbk/1/da"><img src="http://feedads.g.doubleclick.net/~a/3ewmATAE9y0SLtKhMjyQ91e7Sbk/1/di" border="0" ismap="true"></img></a></p><img src="http://feeds.feedburner.com/~r/software_testing_stuff/~4/v9PFXEZ7HTM" height="1" width="1"/>Phttp://www.blogger.com/profile/11295088633938021751noreply@blogger.com4http://www.softwaretestingstuff.com/2009/12/how-to-do-system-testing.htmltag:blogger.com,1999:blog-1020744786956020830.post-12435287434166052872009-12-01T04:04:00.000-08:002009-12-09T05:34:45.169-08:00Difference between Smoke & Sanity Software Testing<b>Smoke Testing: </b>Software Testing done to ensure that whether the build can be accepted for through software testing or not. Basically, it is done to check the stability of the build received for software testing.<br /><br /><a name='more'></a><b>Sanity testing:</b> After receiving a build with minor changes in the code or functionality, a subset of regression test cases are executed that to check whether it rectified the software bugs or issues and no other software bug is introduced by the changes. Sometimes, when multiple cycles of regression testing are executed, sanity testing of the software can be done at later cycles after through regression test cycles. If we are moving a build from staging / testing server to production server, sanity testing of the software application can be done to check that whether the build is sane enough to move to further at production server or not.<br /><br /><b>Difference between Smoke & Sanity Software Testing:</b><br /><ul><li>Smoke testing is a wide approach where all areas of the software application are tested without getting into too deep. However, a sanity software testing is a narrow regression testing with a focus on one or a small set of areas of functionality of the software application.</li><li>The test cases for smoke testing of the software can be either manual or automated. However, a sanity test is generally without test scripts or test cases.</li><li>Smoke testing is done to ensure whether the main functions of the software application are working or not. During smoke testing of the software, we do not go into finer details. However, sanity testing is a cursory software testing type. It is done whenever a quick round of software testing can prove that the software application is functioning according to business / functional requirements.</li><li>Smoke testing of the software application is done to check whether the build can be accepted for through software testing. Sanity testing of the software is to ensure whether the requirements are met or not.<br /></li></ul><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1020744786956020830-1243528743416605287?l=www.softwaretestingstuff.com' alt='' /></div>
<p><a href="http://feedads.g.doubleclick.net/~a/hMODD81ZkMlpULKoyAI_WKManbw/0/da"><img src="http://feedads.g.doubleclick.net/~a/hMODD81ZkMlpULKoyAI_WKManbw/0/di" border="0" ismap="true"></img></a><br/>
<a href="http://feedads.g.doubleclick.net/~a/hMODD81ZkMlpULKoyAI_WKManbw/1/da"><img src="http://feedads.g.doubleclick.net/~a/hMODD81ZkMlpULKoyAI_WKManbw/1/di" border="0" ismap="true"></img></a></p><img src="http://feeds.feedburner.com/~r/software_testing_stuff/~4/Iv6MwT8FT-I" height="1" width="1"/>Phttp://www.blogger.com/profile/11295088633938021751noreply@blogger.com1http://www.softwaretestingstuff.com/2009/12/difference-between-smoke-sanity-testing.htmltag:blogger.com,1999:blog-1020744786956020830.post-51519573994260007332009-10-30T10:55:00.001-07:002009-12-09T05:38:43.500-08:00Software Test Management and Planning<ul><li><a href="http://www.softwaretestingstuff.com/2007/11/software-testing-estimation-process.html" rel="nofollow" title="Software Testing Estimation Process">Software Testing Estimation Process</a> – It covers some important factors which needs to be taken care while doing estimation. </li><li><a href="http://www.softwaretestingstuff.com/2008/12/organizing-test-team.html" rel="nofollow" title="Organizing the Test Team">Organizing the Software Test Team</a> – One of the important tasks for the Software Test Manager.<br /></li><li><a href="http://www.softwaretestingstuff.com/2009/04/test-readiness-review-checklist.html" rel="nofollow" title="Test Readiness Review Checklist">Software Test Readiness Review Checklist</a> – A sample checklist for Software Test Leads & Managers to evaluate the readiness of the application released for software testing. </li></ul><br /><a name='more'></a> <br /><br /><ul><li><a href="http://www.softwaretestingstuff.com/2008/12/identify-testing-types-and-exit.html" rel="nofollow" title="Identify Testing Types and Exit Criteria">Identify Software Testing Types and Exit Criteria</a> – Identifying various types of software testing's required for the application and Exit Criteria, both are very critical for the success of testing effort. </li><li><a href="http://www.softwaretestingstuff.com/2008/12/software-test-planning.html" rel="nofollow" title="Software Test Planning">Software Test Planning</a> – The quality of the testing effort is directly proportional to the quality of the test planning. </li><li><a href="http://www.softwaretestingstuff.com/2008/11/testing-bible-software-test-plan.html" rel="nofollow" title="Testing Bible - Software Test Plan Document">Software Testing Bible - Software Test Plan Document</a> – The document usually created after software test planning or parallel with the Test Planning effort. </li><li><a href="http://www.softwaretestingstuff.com/2007/12/test-specification.html" rel="nofollow" title="Test Specification">Software Test Specification</a> - a detailed summary of what all scenarios shall be tested and how they will be tested. It is basically, a part of software test planning process. </li><li><a href="http://www.softwaretestingstuff.com/2008/11/test-strategy-all-aspects.html" rel="nofollow" title="Test Strategy">Software Test Strategy</a> – Important activity to be done before starting the software test planning. </li><li><a href="http://www.softwaretestingstuff.com/2008/12/when-software-is-ready-to-ship-or.html">When software is ready to ship or release</a> – It is really difficult to decide whether the software is ready for release or not. Only, an experienced software test manager or software test lead can make decision of it. </li><li><a href="http://www.softwaretestingstuff.com/2008/05/responsibilities-of-test-manager-lead.html" rel="nofollow" title="Responsibilities of a Test Manager / Lead">Responsibilities of a Software Test Manager / Lead</a> – Here is a list of roles and responsibilities of a Software Test Manager or Test Lead. It will help aspiring Software Test Managers and leads. </li></ul><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1020744786956020830-5151957399426000733?l=www.softwaretestingstuff.com' alt='' /></div>
<p><a href="http://feedads.g.doubleclick.net/~a/e-1lUI0Se-zN77HlAEmNxE8b9Us/0/da"><img src="http://feedads.g.doubleclick.net/~a/e-1lUI0Se-zN77HlAEmNxE8b9Us/0/di" border="0" ismap="true"></img></a><br/>
<a href="http://feedads.g.doubleclick.net/~a/e-1lUI0Se-zN77HlAEmNxE8b9Us/1/da"><img src="http://feedads.g.doubleclick.net/~a/e-1lUI0Se-zN77HlAEmNxE8b9Us/1/di" border="0" ismap="true"></img></a></p><img src="http://feeds.feedburner.com/~r/software_testing_stuff/~4/d1vO34fPI-A" height="1" width="1"/>Phttp://www.blogger.com/profile/11295088633938021751noreply@blogger.com1http://www.softwaretestingstuff.com/2009/10/test-management-and-planning.htmltag:blogger.com,1999:blog-1020744786956020830.post-9685864437282904502009-10-30T02:39:00.001-07:002009-12-09T06:39:28.715-08:00Software Testing Types, Methods and StrategiesIn my various posts in this web log, I wrote about common and important Software Testing Types, Methods and Strategies. Below are these topics. Although this is not a complete list, but soon it will increase in size as well as in quality.<br /><br />Here is the list:<br /><br /><a name='more'></a><br /><ul><li><a href="http://www.softwaretestingstuff.com/2009/06/localization-testing.html" title="Localization Testing">Localization Software Testing</a></li><li><a href="http://www.softwaretestingstuff.com/2009/05/agile-testing.html" title="Agile Testing">Agile Software Testing</a></li><li><a href="http://www.softwaretestingstuff.com/2008/06/build-verification-testing.html" title="Build Verification Testing">Build Verification Software Testing</a></li><li><a href="http://www.softwaretestingstuff.com/2008/06/usability-testing.html" title="Usability Testing">Usability Software Testing</a></li><li><a href="http://www.softwaretestingstuff.com/2008/05/penetration-testing-software.html" title="Penetration Testing">Penetration Testing</a></li><li><a href="http://www.softwaretestingstuff.com/2008/05/installation-testing.html" title="Installation Testing">Installation Software Testing</a></li><li><a href="http://www.softwaretestingstuff.com/2008/04/network-protocol-testing.html" title="Network Protocol Testing">Network Protocol Testing</a></li><li><a href="http://www.softwaretestingstuff.com/2008/04/what-is-security-testing.html" title="Security Testing">Security Testing</a></li><li><a href="http://www.softwaretestingstuff.com/2007/10/regression-testing.html" title="Regression Testing">Regression Testing</a></li><li><a href="http://www.softwaretestingstuff.com/2007/10/rapid-testing.html" title="Rapid Testing">Rapid Software Testing</a></li><li><a href="http://www.softwaretestingstuff.com/2007/10/task-based-software-testing.html" title="Task-Based Software Testing">Task-Based Software Testing</a></li><li><a href="http://www.softwaretestingstuff.com/2007/10/thread-based-integration-testing.html" title="Thread Based Integration Testing">Thread Based Integration Software Testing</a></li><li><a href="http://www.softwaretestingstuff.com/2007/10/top-down-testing-vs-bottom-up-testing.html" title="Top down Testing and Bottom up Testing">Top down Software Testing and Bottom up Testing</a></li><li><a href="http://www.softwaretestingstuff.com/2007/10/pairwise-testing.html" title="Pairwise Testing">Pairwise Software Testing</a></li><li><a href="http://www.softwaretestingstuff.com/2007/09/user-acceptance-testing.html" title="User Acceptance Testing">User Acceptance Software Testing</a></li><li><a href="http://www.softwaretestingstuff.com/2008/11/spiral-testing-approach.html">Spiral Software Testing Approach</a><br /></li><li><a href="http://www.softwaretestingstuff.com/2007/10/black-box-testing.html" title="Black Box Testing">Black Box Software Testing</a></li><li><a href="http://www.softwaretestingstuff.com/2007/09/white-box-testing.html" title="White Box Testing">White Box Software Testing</a></li><li><a href="http://www.softwaretestingstuff.com/2009/12/difference-between-smoke-sanity-testing.html">Smoke & Sanity Software Testing</a></li><li><a href="http://www.softwaretestingstuff.com/2009/12/how-to-do-system-testing.html">System Testing</a> <br /></li></ul><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1020744786956020830-968586443728290450?l=www.softwaretestingstuff.com' alt='' /></div>
<p><a href="http://feedads.g.doubleclick.net/~a/ToisiIBZlTFVgPlEop9sJimoAMg/0/da"><img src="http://feedads.g.doubleclick.net/~a/ToisiIBZlTFVgPlEop9sJimoAMg/0/di" border="0" ismap="true"></img></a><br/>
<a href="http://feedads.g.doubleclick.net/~a/ToisiIBZlTFVgPlEop9sJimoAMg/1/da"><img src="http://feedads.g.doubleclick.net/~a/ToisiIBZlTFVgPlEop9sJimoAMg/1/di" border="0" ismap="true"></img></a></p><img src="http://feeds.feedburner.com/~r/software_testing_stuff/~4/ANHlzKOSLbY" height="1" width="1"/>Phttp://www.blogger.com/profile/11295088633938021751noreply@blogger.com1http://www.softwaretestingstuff.com/2009/10/testing-types-methods-and-strategies.htmltag:blogger.com,1999:blog-1020744786956020830.post-2533613825602912382009-10-21T22:50:00.001-07:002009-12-09T06:44:21.190-08:00License Errors in HP Mercury's LoadRunner<b>License – Expired:</b> Your LoadRunner license has expired. Please contact customer support to renew it. You have a time-limited license for your LoadRunner application. Some or all of your license features have expired. <br /><a name='more'></a><br /><b>Troubleshooting:</b><br /><ul><li>Check your license information of LoadRunner to verify whether your license has expired.</li><li>Contact customer support of LoadRunner to renew your license</li></ul><b>License – Renewal:</b> Your LoadRunner licenses are no longer valid. Contact customer support to renew your licenses of LoadRunner.<br /><br /><b>Troubleshooting:</b> Contact customer support to renew your LoadRunner license.<br /><br /><b>License - Time limit Expired:</b> LoadRunner out of licenses. You have a time-limited LoadRunner license. Some or all of your license features have expired.<br /><br /><b>Troubleshooting:</b> <br /><ul><li>Check your LoadRunner license to verify which features have expired. </li><li>Contact customer support to renew your LoadRunner license.</li></ul><b>License - Vuser Type Not Licensed:</b> You do not have a LoadRunner license for this Vuser type. Please contact customer support to renew your LoadRunner license.<br /><br /><b>Troubleshooting:</b><br /><ul><li>Check your LoadRunner license information to verify whether the LoadRunner license currently installed includes the Vuser types that you are trying to use.</li><li>Contact customer support to obtain a LoadRunner license for this Vuser type, or to inform them that you have a problem trying to run a LoadRunner licensed Vuser type.</li></ul><b>License - WAN Emulation:</b> You need a LoadRunner license to use the WAN Emulation feature. Please contact customer support for LoadRunner licensing information.<br /><br /><b>Troubleshooting: </b>Contact customer support for WAN Emulation LoadRunner licensing information.<br /><br /><b>Also See: <a href="http://www.softwaretestingstuff.com/2009/10/important-loadrunner-tutorials.html"><span style="color: blue;">Important LoadRunner Tutorials</span></a></b><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1020744786956020830-253361382560291238?l=www.softwaretestingstuff.com' alt='' /></div>
<p><a href="http://feedads.g.doubleclick.net/~a/caEQBckAEXTWST9UqxpLkzngv0g/0/da"><img src="http://feedads.g.doubleclick.net/~a/caEQBckAEXTWST9UqxpLkzngv0g/0/di" border="0" ismap="true"></img></a><br/>
<a href="http://feedads.g.doubleclick.net/~a/caEQBckAEXTWST9UqxpLkzngv0g/1/da"><img src="http://feedads.g.doubleclick.net/~a/caEQBckAEXTWST9UqxpLkzngv0g/1/di" border="0" ismap="true"></img></a></p><img src="http://feeds.feedburner.com/~r/software_testing_stuff/~4/OWpapXdogk4" height="1" width="1"/>Phttp://www.blogger.com/profile/11295088633938021751noreply@blogger.com0http://www.softwaretestingstuff.com/2009/10/license-errors-in-loadrunner.htmltag:blogger.com,1999:blog-1020744786956020830.post-75290157492853933382009-10-08T05:55:00.001-07:002009-12-09T06:48:37.289-08:00Replay Tips for Citrix protocol in HP Mercury's LoadRunnerToday, I’m going add one more tutorial in the <a href="http://www.softwaretestingstuff.com/2009/10/important-loadrunner-tutorials.html">LoadRunner</a> section. Below are some useful tips to replay a HP Mercury's LoadRunner script for Citrix protocol while doing <b>performance testing</b>:<br /><br /><a name='more'></a><br /><ul><li><b>Set initialization quota:</b> To prevent overloading by multiple Vusers in LoadRunner while connecting, set an initialization quota of 4 to 10 Vusers (depending on the capacity of the server) or apply ramp up initialization using the <b>LoadRunner </b>Scheduler. </li><li><b>Enable think time:</b> While doing <b>performance testing</b> using <b>LoadRunner</b>; for best results, do not disable think time in the Run Time settings. Think time is especially relevant before the ctrx_sync_on_window and ctrx_sync_on_bitmap functions, which require time to stabilize. </li><li><b>Set consistency between machines:</b> If you intend to replay the <b>LoadRunner Vuser </b>script on another machine, make sure that the following items are consistent between the record and replay machines: Window Size (resolution), Window Colors, System Font and the other Default Options settings for the Citrix client. In <b>LoadRunner</b>, these settings affect the hash value of bitmaps, and inconsistencies may cause replay to fail. To view the Citrix Client settings, select an item from the Citrix program group and choose Application Set Settings or Custom Connection Settings from the right-click menu. Select the Default Options tab. </li><li><b>Increase the numbers of Vusers per machine:</b> Machines running Citrix <b>Vusers </b>may be limited in the number of <b>Vusers </b>that can run, due to the graphic resources available to that machine. In <b>LoadRunner</b>, to increase the number of <b>Vusers </b>per machine, open a Terminal Server session on the machine. You relate to this Terminal Server as a new injector machine. To refer to the virtual injector machine from the <b>LoadRunner Controller</b>, use the following format: machine_name:1, machine_name:2, ... using either the machine name or its IP address. Note that sessions on a Terminal server use, by default, a 256-color set. If you intend to use a terminal session for load testing, make sure to record on machines with a 256-color set. </li><li><b>Changing window names:</b> In some Citrix sessions, the active window name changes while you are recording. If you try to replay the script as is, the <b>LoadRunner's</b> <b>Vuser </b>uses the original window name and the replay may fail. Using the recording options, you can specify a naming convention for the windows in which <b>LoadRunner's VuGen</b> uses a common prefix or common suffix to identify the window. </li></ul><br /><ul>For example, if the original window's name is "Application 1" where the name changes during application's run to "Application 1", you can instruct <b>LoadRunner's VuGen</b> to use the common prefix only, "Application".Alternatively, you can modify the window names in the actual script after recording. In the Script view (View > Script view), locate the window name and replace the end of the window name with the wildcard notation, *. For example, ctrx_sync_on_window ("Application*", ACTIVATE, ...);.</ul><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1020744786956020830-7529015749285393338?l=www.softwaretestingstuff.com' alt='' /></div>
<p><a href="http://feedads.g.doubleclick.net/~a/HKZYBGBD-wd4uO70XSug7Can4MM/0/da"><img src="http://feedads.g.doubleclick.net/~a/HKZYBGBD-wd4uO70XSug7Can4MM/0/di" border="0" ismap="true"></img></a><br/>
<a href="http://feedads.g.doubleclick.net/~a/HKZYBGBD-wd4uO70XSug7Can4MM/1/da"><img src="http://feedads.g.doubleclick.net/~a/HKZYBGBD-wd4uO70XSug7Can4MM/1/di" border="0" ismap="true"></img></a></p><img src="http://feeds.feedburner.com/~r/software_testing_stuff/~4/rHDOTKDfPvk" height="1" width="1"/>Phttp://www.blogger.com/profile/11295088633938021751noreply@blogger.com0http://www.softwaretestingstuff.com/2009/10/replay-tips-for-citrix-protocol-in.htmltag:blogger.com,1999:blog-1020744786956020830.post-34157037748625302312009-10-06T05:38:00.001-07:002009-12-09T06:53:32.173-08:00How to correlate a Winsock script in LoadRunnerFor <b>LoadRunner </b>7.51 and later, users can correlate the dynamic value for a Winsock script from <b>VuGen</b>'s Tree View. Below is further information on how it can be accomplished.<br /><br /><a name='more'></a><b>In LoadRunner, to use the Tree View for correlation:</b><br /><ol><li>Open the script in VuGen. </li><li>Choose <b>View > Tree View</b>. </li><li>The Tree View will open with the following structure: <br /><br /><br /><ul><li>Function call in the <b>LoadRunner </b>script listed on the left panel. </li><li>Snapshot of the page in the right panel which can be viewed in either <i>Text </i>View<i> or Binary </i>View </li></ul><br /><b>To correlate in LoadRunner: </b><br /></li></ol><ol><li>Select the <b>lrs_recieve</b> function on the left panel of the Tree View. The contents of the received buffer are displayed in the right panel<b>.</b> </li><li>Select either Text View or Binary View. If you work in Text View, you need to clear the <b>Read-only</b> check box in the upper right corner<b>.</b> </li><li>Search for the dynamic value that you want to capture. </li><li>Highlight that value, right-click, and select <b>Create Parameter</b>. There are two ways to create a parameter: <br /><br /><br /><ul><li>If the offset of the dynamic value is fixed, highlighting that value will set the correct values for <b>Data Range </b>in the <b>Create Parameter</b> window. This creates the function <b>lrs_save_param</b>. </li><li>If the offset values are not fixed (when the send buffer is parameterized and the response of the server changes in length), look for fixed left and right boundaries to capture the value. Then check <b>Extract Parameter data using boundaries</b> and set the left and right boundaries correctly. This creates function <b>lrs_save_search_string</b>.<br /></li></ul><br /><br /></li><li><b>VuGen </b>will pop-up with an option for applying the correlation to all occurrences of the value in the script. <br /><br /><br /><ul><li>If you select <b>Yes</b>, <b>VuGen </b>will automatically search for this value in all the <b>lrs_send</b> buffers and replace the values with the parameter name. </li><li>If you select <b>No</b>, the correlation will be applied to the current location only.<br /></li></ul><br /><br /></li></ol><b>Also See:</b> Other <b><a href="http://www.softwaretestingstuff.com/2009/10/important-loadrunner-tutorials.html"><span style="color: blue;">LoadRunner Tutorials</span></a></b><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1020744786956020830-3415703774862530231?l=www.softwaretestingstuff.com' alt='' /></div>
<p><a href="http://feedads.g.doubleclick.net/~a/ZT3hfaXJ5A5FXlbX4SoOL1zpsAQ/0/da"><img src="http://feedads.g.doubleclick.net/~a/ZT3hfaXJ5A5FXlbX4SoOL1zpsAQ/0/di" border="0" ismap="true"></img></a><br/>
<a href="http://feedads.g.doubleclick.net/~a/ZT3hfaXJ5A5FXlbX4SoOL1zpsAQ/1/da"><img src="http://feedads.g.doubleclick.net/~a/ZT3hfaXJ5A5FXlbX4SoOL1zpsAQ/1/di" border="0" ismap="true"></img></a></p><img src="http://feeds.feedburner.com/~r/software_testing_stuff/~4/7DVE0XKr-Lg" height="1" width="1"/>Phttp://www.blogger.com/profile/11295088633938021751noreply@blogger.com2http://www.softwaretestingstuff.com/2009/10/how-to-correlate-winsock-script-in.htmltag:blogger.com,1999:blog-1020744786956020830.post-65302561663749557082009-10-05T09:17:00.001-07:002009-10-24T20:15:29.773-07:00Important LoadRunner Tutorials<p>Below are some the links of eXcellent loadrunner tutorials:</p> <ol> <li><a href="http://www.softwaretestingstuff.com/2009/10/recording-tips-in-load-runner.html">Recording Tips in Load Runner</a></li> <span class="fullpost"> <li><a href="http://www.softwaretestingstuff.com/2009/10/recording-problems-in-loadrunner.html">Recording Problems in LoadRunner</a></li> <li><a href="http://www.softwaretestingstuff.com/2009/08/hp-diagnostics-and-loadrunner.html">HP Diagnostics and LoadRunner Integration</a></li> <li><a href="http://www.softwaretestingstuff.com/2009/08/loadrunner-automation-api.html">LoadRunner Automation API</a></li> <li><a href="http://www.softwaretestingstuff.com/2009/08/lr-analysis-api.html">Analysis API in LoadRunner</a></li> <li><a href="http://www.softwaretestingstuff.com/2009/08/vusers.html">Vusers in LoadRunner</a></li> <li><a href="http://www.softwaretestingstuff.com/2009/03/c-vuser-functions-in-loadrunner.html">C Vuser Functions in LoadRunner</a></li> <li><a href="http://www.softwaretestingstuff.com/2009/03/loadrunner-vugen-environment-options.html">LoadRunner VuGen Environment Options</a></li> <li><a href="http://www.softwaretestingstuff.com/2008/11/silent-test-runner.html">Silent Test Runner</a></li> <li><a href="http://www.softwaretestingstuff.com/2008/11/measuring-transactions.html">Measuring Transactions</a></li> <li><a href="http://www.softwaretestingstuff.com/2008/11/inserting-and-running-tests-in.html">Inserting and Running Tests in LoadRunner or Business Process Monitor</a></li> <li><a href="http://www.softwaretestingstuff.com/2008/11/mercury-performance-testing-and.html">Mercury Performance Testing and Business Availability Center Products</a></li> <li><a href="http://www.softwaretestingstuff.com/2008/11/mercury-loadrunner-and-citrix.html">Mercury LoadRunner and Citrix</a></li> <li><a href="http://www.softwaretestingstuff.com/2008/11/citrix-ica-client-integration-with.html">Citrix ICA Client Integration with LoadRunner</a></li> <li><a href="http://www.softwaretestingstuff.com/2008/11/citrix-load-testing-challenges.html">Citrix Load Testing Challenges</a></li><li><a href="http://www.softwaretestingstuff.com/2009/10/how-to-correlate-winsock-script-in.html">How to correlate a Winsock script in LoadRunner</a></li><li><a href="http://www.softwaretestingstuff.com/2009/10/replay-tips-for-citrix-protocol-in.html">Replay tips for Citrix protocol in LoadRunner</a></li><li><a href="http://www.softwaretestingstuff.com/2009/10/license-errors-in-loadrunner.html">License Errors in LoadRunner</a><br /></li> <li><a href="http://www.softwaretestingstuff.com/2007/10/load-runner-interview-questions.html">Load Runner - Interview Questions</a></li> </span></ol><span style="font-weight: bold;">Note: For further stuff on LoadRunner, please visit our other website: </span><a style="font-weight: bold;" href="http://www.loadrunnerstuff.com/">LoadRunnerStuff.com</a><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1020744786956020830-6530256166374955708?l=www.softwaretestingstuff.com' alt='' /></div>
<p><a href="http://feedads.g.doubleclick.net/~a/vqZ5tp6ZFvnpHEX_vHlgL8i_H2E/0/da"><img src="http://feedads.g.doubleclick.net/~a/vqZ5tp6ZFvnpHEX_vHlgL8i_H2E/0/di" border="0" ismap="true"></img></a><br/>
<a href="http://feedads.g.doubleclick.net/~a/vqZ5tp6ZFvnpHEX_vHlgL8i_H2E/1/da"><img src="http://feedads.g.doubleclick.net/~a/vqZ5tp6ZFvnpHEX_vHlgL8i_H2E/1/di" border="0" ismap="true"></img></a></p><img src="http://feeds.feedburner.com/~r/software_testing_stuff/~4/mtsU4vi-2Lw" height="1" width="1"/>Phttp://www.blogger.com/profile/11295088633938021751noreply@blogger.com0http://www.softwaretestingstuff.com/2009/10/important-loadrunner-tutorials.htmltag:blogger.com,1999:blog-1020744786956020830.post-77411250204514623762009-10-05T08:56:00.001-07:002009-10-05T10:35:23.268-07:00Recording Tips in Load Runner<p>In continuation to my previous post “<a href="http://www.softwaretestingstuff.com/2009/10/recording-problems-in-loadrunner.html">Recording Problems in Load Runner</a>”, here, I’m going to give you some good and useful tips for doing recording in Load Runner.</p> <span class="fullpost"> <ol> <li><strong>Use the mouse and not the keyboard:</strong> In LoadRunner, it is preferable to click on an object with the mouse rather then using the keyboard. During recording, use only GUI objects that are within the browser's pane. Do not use any browser icons, controls, the Stop button, or menu items, such as View > Refresh. You may, however, use the Refresh, Home, Back and Forward buttons and the address bar. </li><li><strong>Do not record over an existing script :</strong> It is best to record into a newly created script—not an existing one. </li> <li><strong>Avoid context menus:</strong> Avoid using context menus during recording. Context menus are menus which pop up when clicking an item in a graphical user interface, such as right-click menus. </li> <li><strong>Avoid working in a browser while recording:</strong> During recording, do not work in any browser window other than the browser windows opened by VuGen. </li> <li><strong>Wait for downloads:</strong> Wait for all downloads to complete before doing any action, such as clicking on a button or filling in a text field. </li> <li><strong>Wait for pages to load:</strong> During recording, it is best to wait for the page to load completely before doing the next step. If you did not wait for all of the pages to load, record the script again. </li> <li><strong>Navigate to start page:</strong> If the last page in an action does not contain the links and buttons that were available at the start of the iteration, then the next iteration will fail. For example, if the first page has a text link Book A Flight, make sure to navigate to the appropriate page at the end of your recording, so that the same link will be visible at the end of the business process. </li> <li><strong>Use a higher event configuration level:</strong> Record the business process again the High Event Configuration level. </li> <li><strong>Disable socket level recording:</strong> In certain cases, the capturing of the socket level messages disrupts the application. For most recordings, socket level data is not required. To prevent the recording of socket level data, disable the option in the recording options. For more information, see the section about recording with Click and Script. </li> <li><strong>Enable the record rendering-related property values:</strong> If the client-side scripts of the application use a lot of styling activities, enable the Record rendering-related property values option before recording the script. For example, enable this option to record additional DOM objects such as offsetTop. Note that enabling this option may decrease the replay speed. To enable record rendering-related property values in <strong>Load Runner</strong>: </li> <p>Open the Recording Options. Select Tools > Recording Options and select the GUI Properties:Advanced node</p><p> <span style="font-weight: bold;">Also See:</span> Other <a href="http://www.softwaretestingstuff.com/2009/10/important-loadrunner-tutorials.html"><span style="font-weight: bold; color: rgb(0, 0, 153);">LoadRunner Tutorials</span></a><br /></p> </ol> </span><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1020744786956020830-7741125020451462376?l=www.softwaretestingstuff.com' alt='' /></div>
<p><a href="http://feedads.g.doubleclick.net/~a/cgxb9Wh-jW2LU2_pzS4aeKp6CrA/0/da"><img src="http://feedads.g.doubleclick.net/~a/cgxb9Wh-jW2LU2_pzS4aeKp6CrA/0/di" border="0" ismap="true"></img></a><br/>
<a href="http://feedads.g.doubleclick.net/~a/cgxb9Wh-jW2LU2_pzS4aeKp6CrA/1/da"><img src="http://feedads.g.doubleclick.net/~a/cgxb9Wh-jW2LU2_pzS4aeKp6CrA/1/di" border="0" ismap="true"></img></a></p><img src="http://feeds.feedburner.com/~r/software_testing_stuff/~4/KcyrYs8v4HQ" height="1" width="1"/>Phttp://www.blogger.com/profile/11295088633938021751noreply@blogger.com0http://www.softwaretestingstuff.com/2009/10/recording-tips-in-load-runner.htmltag:blogger.com,1999:blog-1020744786956020830.post-12452547540416540292009-10-05T04:49:00.001-07:002009-10-08T07:31:48.694-07:00Recording Problems in LoadRunner<p>Here, I’m going to describe some common recording problems / issues of Load Runner and how to resolve them. Normally, these problems are faced by everyone. I would request you all that leave your comments for the problems you face and how you tackle them.</p> <ol><li><strong>Firefox is not supported:</strong> Only Internet Explorer is supported for Web (Click and Script). To record browser activity on Firefox, use the Web (HTTP/HTML) protocol. </li> <span class="fullpost"> <li><strong>Application behaves differently while being recorded:</strong> If your application behaves differently during recording, than it does without recording, you should determine if the recording problem is unique to Web (Click and Script). The effect may be that a Web page will not load, part of the content is missing, a popup window does not open, and so forth. Create a new Web (HTTP/HTML) script and repeat the recording. In the event that the recording is OK in Web (HTTP/HTML), we recommend that you disable socket level recording. The problem may be the result of an event listener. Use trial and error to disable event listeners in the Web Event Configuration Recording Options, and then re-record your session as a Web (Click and Script) user. To disable an event listener: <ul><li>Open the Recording Options. Select Tools > Recording Options and select the GUI Properties:Web Event Configuration node. </li><li>Click Custom Settings and expand the Web Objects node. Select an object. </li><li>Select Disabled from the list in the Record column for the relevant Web object. If the recording still does not work, enable the listener you previously disabled, and try disabling another one. Repeat these steps until your recording succeeds. </li></ul></li><li><strong>Dynamic menu navigation was not recorded:</strong> A dynamic menu is a menu that dynamically changes depending on where you select it. If the dynamic menu navigation was not recorded, record again using "high" event configuration mode. To set the configuration level to high: <ul><li>Open the Recording Options. Select Tools > Recording Options and select the GUI Properties:Web Event Configuration node. </li><li>Move the slider to High. </li></ul></li><li><strong>Certain user actions were not recorded:</strong> Check if there is a Java applet running inside the browser. If not, record the script with the Web (HTTP/HTML) protocol. </li></ol><span style="font-weight: bold;">Also See:</span> Other <a href="http://www.softwaretestingstuff.com/2009/10/recording-problems-in-loadrunner.html"><span style="font-weight: bold; color: rgb(0, 0, 153);">LoadRunner Tutorials</a></span></span><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1020744786956020830-1245254754041654029?l=www.softwaretestingstuff.com' alt='' /></div>
<p><a href="http://feedads.g.doubleclick.net/~a/ZkE1kDU8byfglmQXPtoD-UUPSnQ/0/da"><img src="http://feedads.g.doubleclick.net/~a/ZkE1kDU8byfglmQXPtoD-UUPSnQ/0/di" border="0" ismap="true"></img></a><br/>
<a href="http://feedads.g.doubleclick.net/~a/ZkE1kDU8byfglmQXPtoD-UUPSnQ/1/da"><img src="http://feedads.g.doubleclick.net/~a/ZkE1kDU8byfglmQXPtoD-UUPSnQ/1/di" border="0" ismap="true"></img></a></p><img src="http://feeds.feedburner.com/~r/software_testing_stuff/~4/v32LBxE0Rck" height="1" width="1"/>Phttp://www.blogger.com/profile/11295088633938021751noreply@blogger.com0http://www.softwaretestingstuff.com/2009/10/recording-problems-in-loadrunner.htmltag:blogger.com,1999:blog-1020744786956020830.post-38695315441820671422009-10-02T03:15:00.000-07:002009-10-05T06:55:04.286-07:00Latest QTP Training Material and TutorialsHere are the links of some good QTP tutorials. Beginners can use these tutorials as a training material. Read these and give your feedback for improvement.<span class="fullpost"><br /><ol><li><a href="http://www.softwaretestingstuff.com/2009/08/keyword-driven-methodology.html">Keyword Driven Methodology</a></li><li><a href="http://www.softwaretestingstuff.com/2009/04/enhancements-in-quicktest-professional.html">Enhancements in QuickTest Professional 10</a></li><li><a href="http://www.softwaretestingstuff.com/2009/08/object-repository-types-in-qtp.html">Object Repository Types in QTP</a></li><li><a href="http://www.softwaretestingstuff.com/2009/08/testing-business-components-using-qtp.html">Testing Business Components using QTP and Quality Center</a> </li><li><a href="http://www.softwaretestingstuff.com/2009/08/running-part-of-test-script-in-qtp.html">Running Part of Test Script in QTP</a></li><li><a href="http://www.softwaretestingstuff.com/2009/08/debugging-action-or-function-in-qtp.html">Debugging an Action or a Function in QTP</a></li><li><a href="http://www.softwaretestingstuff.com/2009/08/handling-run-errors-in-qtp.html">Handling Run Errors in QTP</a></li><li><a href="http://www.softwaretestingstuff.com/2009/08/debugging-components-and-function.html">Debugging Components and Function Libraries in QTP</a></li><li><a href="http://www.softwaretestingstuff.com/2009/08/oracle-add-in-for-qtp.html">Oracle Add-in for QTP</a></li><li><a href="http://www.softwaretestingstuff.com/2009/08/working-with-java-add-in-in-qtp.html">Working with the Java Add-in in QTP</a></li><li><a href="http://www.softwaretestingstuff.com/2009/07/delphi-add-in-in-qtp-10.html">Delphi Add-in in QTP 10</a></li><li><a href="http://www.softwaretestingstuff.com/2009/04/fine-tuning-bitmap-comparison.html">Fine-Tuning the Bitmap Comparison</a></li><li><a href="http://www.softwaretestingstuff.com/2009/04/jumping-to-step-in-quicktest-1000.html">Jumping to a Step in QuickTest 10.00</a></li><li><a href="http://www.softwaretestingstuff.com/2009/04/installing-custom-comparer-and.html">Installing Custom Comparer and Registering to <span class="post-labels" id="labels-7705138012111980849">QTP</span></a></li><li><a href="http://www.softwaretestingstuff.com/2009/04/considerations-for-developing-custom.html">Considerations for Developing Custom Comparers</a></li><li><a href="http://www.softwaretestingstuff.com/2009/04/developing-bitmap-checkpoint-comparison.html">Developing Bitmap Checkpoint Comparison Algorithm</a></li><li><a href="http://www.softwaretestingstuff.com/2009/04/comparing-shared-object-repositories.html">Comparing Shared Object Repositories</a></li><li><a href="http://www.softwaretestingstuff.com/2009/04/asset-comparison-tool-and-asset-viewer.html">Asset Comparison Tool and Asset Viewer</a></li><li><a href="http://www.softwaretestingstuff.com/2009/04/resources-and-dependencies-model.html">Resources and Dependencies Model </a></li><li><a href="http://www.softwaretestingstuff.com/2009/04/test-analysis-using-qtp-1000.html">Test Analysis using QTP 10.00</a></li><li><a href="http://www.softwaretestingstuff.com/2009/04/manage-and-share-testing-assets-in.html">Manage and Share Testing Assets in Quality Center and QTP 10</a></li><li><a href="http://www.softwaretestingstuff.com/2008/12/considerations-for-testing-activex.html">Testing ActiveX Controls using QuickTest Professional</a></li><li><a href="http://www.softwaretestingstuff.com/2008/12/hp-quicktest-professional-test-object.html">HP QuickTest Professional Test Object Schema</a></li><li><a href="http://www.softwaretestingstuff.com/2008/12/implement-web-add-in-extensibility-in.html">Implement Web Add-in Extensibility in QTP</a></li><li><a href="http://www.softwaretestingstuff.com/2008/11/objects-and-actions-in-qtp.html">Objects and Actions in QTP</a></li><li><a href="http://www.softwaretestingstuff.com/2008/11/datatable-in-qtp.html">DataTable in QTP</a></li><li><a href="http://www.softwaretestingstuff.com/2008/11/naming-conventions-in-qtp.html">Naming Conventions in QTP</a></li><li><a href="http://www.softwaretestingstuff.com/2008/11/settings-in-qtp.html">Settings in QTP</a></li><li><a href="http://www.softwaretestingstuff.com/2008/11/quicktest-tests-for-use-with-loadrunner.html">QuickTest Tests for Use with LoadRunner or Business Process Monitor</a> </li><li><a href="http://www.softwaretestingstuff.com/2008/11/mercury-performance-testing-and.html">Mercury Performance Testing and Business Availability Center Products </a></li><li><a href="http://www.softwaretestingstuff.com/2008/11/bpt-methodology-in-qtp-and-quality.html">BPT Methodology in QTP and Quality Center </a><br /></li><li><a href="http://www.softwaretestingstuff.com/2008/11/business-process-testing.html">Business Process Testing</a></li><li><a href="http://www.softwaretestingstuff.com/2008/12/qtp-cste-iseb-istqb-question-papers.html">QTP, CSTE, ISEB, ISTQB, CSQA Question / Certification Papers</a></li><li><a href="http://www.softwaretestingstuff.com/2007/10/qtp-interview-questions.html">QTP Interview Questions - Part 1</a></li><li><a href="http://www.softwaretestingstuff.com/2008/05/qtp-interview-questions-part-2.html">QTP Interview Questions - Part 2</a></li></ol></span><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1020744786956020830-3869531544182067142?l=www.softwaretestingstuff.com' alt='' /></div>
<p><a href="http://feedads.g.doubleclick.net/~a/XDgFvOLS_y-2LFGRtuwIp7n6E8M/0/da"><img src="http://feedads.g.doubleclick.net/~a/XDgFvOLS_y-2LFGRtuwIp7n6E8M/0/di" border="0" ismap="true"></img></a><br/>
<a href="http://feedads.g.doubleclick.net/~a/XDgFvOLS_y-2LFGRtuwIp7n6E8M/1/da"><img src="http://feedads.g.doubleclick.net/~a/XDgFvOLS_y-2LFGRtuwIp7n6E8M/1/di" border="0" ismap="true"></img></a></p><img src="http://feeds.feedburner.com/~r/software_testing_stuff/~4/HWUBgW9Oia4" height="1" width="1"/>Phttp://www.blogger.com/profile/11295088633938021751noreply@blogger.com0http://www.softwaretestingstuff.com/2009/10/latest-qtp-training-material-and.htmltag:blogger.com,1999:blog-1020744786956020830.post-3786145295418851132009-08-30T05:26:00.001-07:002009-10-05T08:07:16.406-07:00Selenium - Overview<p>Selenium is a portable software testing framework for web applications. The tests can be written as HTML tables or coded in a number of popular programming languages and can be run directly in most modern web browsers. Selenium can be deployed on Windows, Linux, and Macintosh. Selenium is used for UAT (User Acceptance Test). </p> <p> </p><span class="fullpost"> <p>Selenium consists of </p> <p> </p> <p>- Selenium Core <br />- Selenium RC <br />- Selenium Grid <br />- Selenium on Rails <br />- Selenium IDE </p> <p> </p> <p><strong>Selenium IDE: </strong></p> <p>Selenium IDE is a complete Integrated Development Environment (IDE) for Selenium tests (previously known as Selenium Recorder). Firefox extension that allows recording and editing of tests. It allows easier development of tests. It can output Ruby for it’s Ruby based (Application Programming Interface) API. </p> <p> </p> <p><strong>Selenium IDE Features: </strong></p> <p><strong></strong></p> <p>- Record and playback <br />- Intelligent field selection will use IDs, names, or XPath as needed <br />- Auto complete for all common Selenium commands <br />- Walk through test cases and test suites. <br />- Debug and set breakpoints <br />- Save tests as HTML, Ruby scripts, or other formats <br />- Support for Selenium user-extensions.js file <br />- Option to automatically assert the title of every page <br />- Rollup common commands </p> <p> </p> <p><strong>Selenium IDE License: </strong></p> <p>Selenium was developed by a team of programmers and testers at Thought Works. Selenium is open source software, released under the Apache 2.0 license and can be downloaded and used without charge. The Selenium Grid provides a hub allowing the running of multiple Selenium tests concurrently  on any number of local or remote systems, thus minimizing test execution time. </p></span> <div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1020744786956020830-378614529541885113?l=www.softwaretestingstuff.com' alt='' /></div>
<p><a href="http://feedads.g.doubleclick.net/~a/NUq4vK87rk6DNzxfpQNqd74NIg4/0/da"><img src="http://feedads.g.doubleclick.net/~a/NUq4vK87rk6DNzxfpQNqd74NIg4/0/di" border="0" ismap="true"></img></a><br/>
<a href="http://feedads.g.doubleclick.net/~a/NUq4vK87rk6DNzxfpQNqd74NIg4/1/da"><img src="http://feedads.g.doubleclick.net/~a/NUq4vK87rk6DNzxfpQNqd74NIg4/1/di" border="0" ismap="true"></img></a></p><img src="http://feeds.feedburner.com/~r/software_testing_stuff/~4/Fdw8x_L7NTI" height="1" width="1"/>Phttp://www.blogger.com/profile/11295088633938021751noreply@blogger.com0http://www.softwaretestingstuff.com/2009/08/selenium-overview.htmltag:blogger.com,1999:blog-1020744786956020830.post-32567760866344422492009-08-30T05:09:00.001-07:002009-11-01T08:50:31.639-08:00Selenium Interview Questions - 1<p><strong>Q1. What is Selenium? </strong></p> <p><strong>Ans.</strong> Selenium is a set of tools that supports rapid development of test automation scripts for web </p> <p>based applications. Selenium testing tools provides a rich set of testing functions specifically </p> <p>designed to fulfil needs of testing of a web based application. </p> <p> </p> <p><strong>Q2. What are the main components of Selenium testing tools?</strong> <br /><strong>Ans.</strong> Selenium IDE, Selenium RC and Selenium Grid</p> <p> </p><span class="fullpost"> <p><strong>Q3. What is Selenium IDE? <br />Ans.</strong> Selenium IDE is for building Selenium test cases. It operates as a Mozilla Firefox add on and </p> <p>provides an easy to use interface for developing and running individual test cases or entire test </p> <p>suites. Selenium-IDE has a recording feature, which will keep account of user actions as they are </p> <p>performed and store them as a reusable script to play back. </p> <p> </p> <p><strong>Q4. What is the use of context menu in Selenium IDE?</strong> <br /><strong>Ans.</strong> It allows the user to pick from a list of assertions and verifications for the selected location. </p> <p> </p> <p><strong>Q5. Can tests recorded using Selenium IDE be run in other browsers? <br />Ans.</strong> Yes. Although Selenium IDE is a Firefox add on, however, tests created in it can also be run in </p> <p>other browsers by using Selenium RC (Selenium Remote Control) and specifying the name of the test </p> <p>suite in command line.</p> <p> </p> <p><strong>Q6. What are the advantage and features of Selenium IDE?</strong> </p> <p><strong>Ans.</strong> 1. Intelligent field selection will use IDs, names, or XPath as needed <br />2. It is a record & playback tool and the script format can be written in various languages including </p> <p>C#, Java, PERL, Python, PHP, HTML <br />3. Auto complete for all common Selenium commands <br />4. Debug and set breakpoints <br />5. Option to automatically assert the title of every page <br />6. Support for Selenium user-extensions.js file</p> <p> </p> <p><strong>Q7. What are the disadvantage of Selenium IDE tool? <br />Ans.</strong> 1. Selenium IDE tool can only be used in Mozilla Firefox browser. <br />2. It is not playing multiple windows when we record it.</p> <p> </p> <p><strong>Q8. What is Selenium RC (Remote Control)? <br />Ans.</strong> Selenium RC allows the test automation expert to use a programming language for maximum </p> <p>flexibility and extensibility in developing test logic. For example, if the application under test returns </p> <p>a result set and the automated test program needs to run tests on each element in the result set, the </p> <p>iteration / loop support of programming language’s can be used to iterate through the result set, </p> <p>calling Selenium commands to run tests on each item. </p> <p> </p> <p>Selenium RC provides an API and library for each of its supported languages. This ability to use </p> <p>Selenium RC with a high level programming language to develop test cases also allows the automated </p> <p>testing to be integrated with the project’s automated build environment.</p> <p> </p> <p><strong>Q9. What is Selenium Grid? </strong></p> <p><strong>Ans.</strong> Selenium Grid in the selenium testing suit allows the Selenium RC solution to scale for test suites </p> <p>that must be run in multiple environments. Selenium Grid can be used to run multiple instances of </p> <p>Selenium RC on various operating system and browser configurations. </p> <p> </p> <p><strong>Q10. How Selenium Grid works? </strong></p> <p><strong>Ans.</strong> Selenium Grid sent the tests to the hub. Then tests are redirected to an available Selenium RC, </p> <p>which launch the browser and run the test. Thus, it allows for running tests in parallel with the entire </p> <p>test suite.</p> <p> </p> <p><strong>Q 11. What you say about the flexibility of Selenium test suite? <br />Ans.</strong> Selenium testing suite is highly flexible. There are multiple ways to add functionality to Selenium </p> <p>framework to customize test automation. As compared to other test automation tools, it is </p> <p>Selenium’s strongest characteristic. Selenium Remote Control support for multiple programming and </p> <p>scripting languages allows the test automation engineer to build any logic they need into their </p> <p>automated testing and to use a preferred programming or scripting language of one’s choice. </p> <p>Also, the Selenium testing suite is an open source project where code can be modified and </p> <p>enhancements can be submitted for contribution.</p> <p> </p> <p><strong>Q12. What test can Selenium do? <br />Ans.</strong> Selenium is basically used for the functional testing of web based applications. It can be used for </p> <p>testing in the continuous integration environment. It is also useful for agile testing</p> <p> </p> <p><strong>Q13. What is the cost of Selenium test suite? <br />Ans.</strong> Selenium test suite a set of open source software tool, it is free of cost.</p> <p> </p> <p><strong>Q14. What browsers are supported by Selenium Remote Control? <br />Ans. </strong>The test automation expert can use Firefox, IE 7/8, Safari and Opera browsers to run tests in </p> <p>Selenium Remote Control.</p> <p> </p> <p><strong>Q15. What programming languages can you use in Selenium RC? <br />Ans.</strong> C#, Java, Perl, PHP, Python, Ruby</p> <p> </p> <p><strong>Q16. What are the advantages and disadvantages of using Selenium as testing tool? <br />Ans.</strong> <strong>Advantages:</strong> Free, Simple and powerful DOM (document object model) level testing, can be used </p> <p>for continuous integration; great fit with Agile projects. </p> <p> </p> <p><strong>Disadvantages:</strong> Tricky setup; dreary errors diagnosis; can not test client server applications.</p> <p> </p> <p><strong>Q17. What is difference between QTP and Selenium? <br />Ans.</strong> Only web applications can be testing using Selenium testing suite. However, QTP can be used for </p> <p>testing client server applications. Selenium supports following web browsers: Internet Explorer, </p> <p>Firefox, Safari, Opera or Konqueror on Windows, Mac OS X and Linux. However, QTP is limited to </p> <p>Internet Explorer on Windows.</p> <p> <br />QTP uses scripting language implemented on top of VB Script. However, Selenium test suite has the </p> <p>flexibility to use many languages like Java, .Net, Perl, PHP, Python, and Ruby.</p> <p> </p> <p><strong>Q18. What is difference between Borland Silk test and Selenium? <br />Ans.</strong> Selenium is completely free test automation tool, while Silk Test is not. Only web applications </p> <p>can be testing using Selenium testing suite. However, Silk Test can be used for testing client server </p> <p>applications. Selenium supports following web browsers: Internet Explorer, Firefox, Safari, Opera or </p> <p>Konqueror on Windows, Mac OS X and Linux. However, Silk Test is limited to Internet Explorer and </p> <p>Firefox.</p> <p> <br />Silk Test uses 4Test scripting language. However, Selenium test suite has the flexibility to use many </p> <p>languages like Java, .Net, Perl, PHP, Python, and Ruby.</p></span> <div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1020744786956020830-3256776086634442249?l=www.softwaretestingstuff.com' alt='' /></div>
<p><a href="http://feedads.g.doubleclick.net/~a/1oUNVQ4JEO6Z-lCuGXGqnW9SGto/0/da"><img src="http://feedads.g.doubleclick.net/~a/1oUNVQ4JEO6Z-lCuGXGqnW9SGto/0/di" border="0" ismap="true"></img></a><br/>
<a href="http://feedads.g.doubleclick.net/~a/1oUNVQ4JEO6Z-lCuGXGqnW9SGto/1/da"><img src="http://feedads.g.doubleclick.net/~a/1oUNVQ4JEO6Z-lCuGXGqnW9SGto/1/di" border="0" ismap="true"></img></a></p><img src="http://feeds.feedburner.com/~r/software_testing_stuff/~4/jSQ4aY4Twlc" height="1" width="1"/>Phttp://www.blogger.com/profile/11295088633938021751noreply@blogger.com1http://www.softwaretestingstuff.com/2009/08/selenium-interview-questions-1.htmltag:blogger.com,1999:blog-1020744786956020830.post-36848444531289686042009-08-29T08:06:00.001-07:002009-10-05T06:55:17.371-07:00Object Repository Types in QTP<p>Test objects can be stored in two types of object repositories—a <strong>shared object repository</strong> and a <strong>local object repository</strong>. A shared object repository stores test objects in a file that can be accessed by multiple components (via their application areas) in read-only mode. A local object repository stores objects in a file that is associated with one specific component, so that only that component can access the stored objects.</p> <p> </p> <span class="fullpost"> <p>When you plan and create components, you must consider how you want to store the objects in your components. You can store the objects for each component in its corresponding local object repository, or you can store the objects in your components in one or more shared object repositories. By storing objects in shared object repositories and associating these repositories with your components’ application areas, you enable multiple components to use the objects. For each component, you can use a combination of objects from your local and shared object repositories, according to your needs. You can also transfer local objects to a shared object repository, if required. This reduces maintenance and enhances the reusability of your components because it enables you to maintain the objects in a single, shared location instead of multiple locations.</p> <p> </p> <p>If you are new to using QTP, you may want to use local object repositories. In this way, you can record and run components without creating, choosing, or modifying shared object repositories because all objects are automatically saved in a local object repository that can be accessed by its corresponding component. If you modify an object in the local object repository, your changes do not have any effect on any other component.</p> <p> </p> <p>If you are familiar with testing, it is probably most efficient to save objects in a shared object repository. In this way, you can use the same shared object repository for multiple components—if the components include the same objects. Test object information that applies to many components is kept in one central location. When the objects in your application change, you can update them in one location for all the components that use this shared object repository.</p> <p> </p> <p>If an object with the same name and description is located in both the local object repository and in a shared object repository associated with the same component, the component uses the local object definition. If an object with the same name and description is located in more than one shared object repository associated with the same component, the object definition is used from the first occurrence of the object, according to the order in which the shared object repositories are associated with the component.</p> <p> </p> <p>Local objects are saved locally with the component, and can be accessed only from that component. When using a shared object repository, you can use the same object repository for multiple components. You can also use multiple object repositories for each component.</p> <p> </p> <p>When you open and work with an existing component, it always uses the object repositories that are specified in the application area with which the component is associated. Shared object repositories are read-only when accessed from components; you edit them using the Object Repository Manager.</p> </span> <div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1020744786956020830-3684844453128968604?l=www.softwaretestingstuff.com' alt='' /></div>
<p><a href="http://feedads.g.doubleclick.net/~a/3UYv2INYcVJXhkBBtF9oa8wB7o4/0/da"><img src="http://feedads.g.doubleclick.net/~a/3UYv2INYcVJXhkBBtF9oa8wB7o4/0/di" border="0" ismap="true"></img></a><br/>
<a href="http://feedads.g.doubleclick.net/~a/3UYv2INYcVJXhkBBtF9oa8wB7o4/1/da"><img src="http://feedads.g.doubleclick.net/~a/3UYv2INYcVJXhkBBtF9oa8wB7o4/1/di" border="0" ismap="true"></img></a></p><img src="http://feeds.feedburner.com/~r/software_testing_stuff/~4/xrCIhkmGBqk" height="1" width="1"/>Phttp://www.blogger.com/profile/11295088633938021751noreply@blogger.com0http://www.softwaretestingstuff.com/2009/08/object-repository-types-in-qtp.htmltag:blogger.com,1999:blog-1020744786956020830.post-14440795850196976212009-08-29T08:01:00.001-07:002009-10-05T06:55:17.372-07:00Testing Business Components using QTP and Quality Center<p>Generally, business components are created and modified in Quality Centre by Subject Matter Experts. However, you can use the Business Component Keyword View to create, view, modify, and debug a business component in QTP, if required.</p> <p> </p> <p>In the Keyword View, business components are divided into steps in a modular, keyword-driven, table format. Each step is a row that comprises individual parts that you can easily modify. You create and modify steps by selecting items and operations and entering additional information, as required.</p> <p> </p><span class="fullpost"> <p>Each step in a business component is automatically documented as you complete it. This enables you to view a description of the step in understandable sentences. In addition, if you added a function library to the application area associated with the business component, when you define a step by selecting a user-defined operation (function), the documentation that you added in the function library will be displayed for the step.</p> <p> </p> <p>Before you create or open a business component, you connect QTP to a Quality Centre project, which is where business components and application area resources and settings are stored. Connecting to your Quality Centre project enables QTP to create or open the business component. This also enables the business component to access all of the resources defined in the application area on which the component is based.</p> <p> </p> <p><strong>Important Note: </strong>Make sure you have the required Quality Centre permissions before working with business components and application areas.</p> <p> </p> <p>If the application area you select does not yet contain all of the required resources and settings, you can still add steps using the <strong>ManualStep</strong> function or the <strong>Comment</strong> option. This enables you to type in manual steps as you would in Quality Centre or in another application, such as Microsoft Excel or Microsoft Word. You can also use comments to add information about a step or to separate sections of your business component. Each manual step and comment appears as a separate row in the Keyword View.</p> <p> </p> <p>If you want to delete a component, you can do so only in Quality Centre, regardless of whether it was created in QTP or in Quality Centre.</p> <p> </p> <p>Also, if needed, you can convert a business component to a scripted component.</p></span> <div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1020744786956020830-1444079585019697621?l=www.softwaretestingstuff.com' alt='' /></div>
<p><a href="http://feedads.g.doubleclick.net/~a/rzkjGBTR8XX9gTEQ59LevkQHLEo/0/da"><img src="http://feedads.g.doubleclick.net/~a/rzkjGBTR8XX9gTEQ59LevkQHLEo/0/di" border="0" ismap="true"></img></a><br/>
<a href="http://feedads.g.doubleclick.net/~a/rzkjGBTR8XX9gTEQ59LevkQHLEo/1/da"><img src="http://feedads.g.doubleclick.net/~a/rzkjGBTR8XX9gTEQ59LevkQHLEo/1/di" border="0" ismap="true"></img></a></p><img src="http://feeds.feedburner.com/~r/software_testing_stuff/~4/djJzQlAxzdM" height="1" width="1"/>Phttp://www.blogger.com/profile/11295088633938021751noreply@blogger.com0http://www.softwaretestingstuff.com/2009/08/testing-business-components-using-qtp.htmltag:blogger.com,1999:blog-1020744786956020830.post-67706449600184730922009-08-08T00:36:00.001-07:002009-08-08T00:39:49.455-07:00Running Part of Test Script in QTP<p>You can use the Run from Step option to run a selected part of your test. This enables you to check a specific section of your application or to confirm that a certain part of your test runs smoothly.</p> <p> </p> <p>In the Expert View, you can use the Run from Step option to run your test from the selected step until the end of the action. Using Run from Step in this mode ignores any iterations. However, if the action contains nested actions, QTP runs the nested actions for the defined number of iterations of the nested action.</p> <p> </p><span class="fullpost"> <p>In the Keyword View, you can use the Run from Step option to run your test from the selected step until the end of the test (if the selected step is not part of a reusable action, because a reusable action needs to be called from a test, in order for the test to know from where to continue). Using Run from Step in this mode includes all iterations. The first iteration will run from the step you selected until the end of the test; all other iterations will run from the beginning of the test.</p> <p> </p> <p>You can use the Run Current Action option to run a single action in your test. Using Run Current Action ignores any iterations. However, if the action contains nested actions, QTP runs the nested actions for the defined number of iterations.</p> <p> </p> <p>Please note, if you only want to run one iteration of your test, select Run one iteration only from the Run pane in the Test Settings dialog box.</p> <p> </p> <p>If you want to run your test until a specific point within the test (and not to the end of the action or test), you can insert a breakpoint. The test will then run from the selected step or action until the breakpoint.</p> <p> </p> <p>To run an entire action, or run a test or action from a selected step:</p> <p> </p> <ol> <li>Make sure your application is in a state matching the action or step you want to run. </li> <li>Select the action or step where you want to start running the test. Make sure that the step or action you choose is not dependent on previous steps, such as a retrieved value or a parameter defined in a previous step. </li> <li>Select Automation > Run from Step or Run Current Action, or right-click and select Run from Step. The Run dialog box opens. </li> <li>In the Run dialog box, choose where to save the run session results, and define any input parameters you want to use. </li> <li>Click OK. The Run dialog box closes and the run session starts </li> </ol> <ol> <p align="justify">By default, when the run session ends, the Test Results window opens. The Test Results summary displays a note indicating that the test was run using the Run from Step or Run Current Action option.</p> </ol> <p>If you cleared the View results when run session ends check box in the Run pane of the Options dialog box, the Test Results window does not open at the end of the run session.</p></span> <div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1020744786956020830-6770644960018473092?l=www.softwaretestingstuff.com' alt='' /></div>
<p><a href="http://feedads.g.doubleclick.net/~a/lcATg65k6Yz2n_LPU_uCiMZUqjA/0/da"><img src="http://feedads.g.doubleclick.net/~a/lcATg65k6Yz2n_LPU_uCiMZUqjA/0/di" border="0" ismap="true"></img></a><br/>
<a href="http://feedads.g.doubleclick.net/~a/lcATg65k6Yz2n_LPU_uCiMZUqjA/1/da"><img src="http://feedads.g.doubleclick.net/~a/lcATg65k6Yz2n_LPU_uCiMZUqjA/1/di" border="0" ismap="true"></img></a></p><img src="http://feeds.feedburner.com/~r/software_testing_stuff/~4/KUBeBQ3TQSg" height="1" width="1"/>Phttp://www.blogger.com/profile/11295088633938021751noreply@blogger.com0http://www.softwaretestingstuff.com/2009/08/running-part-of-test-script-in-qtp.htmltag:blogger.com,1999:blog-1020744786956020830.post-619481435615492052009-08-08T00:33:00.001-07:002009-08-08T00:39:49.455-07:00Debugging an Action or a Function in QTP<p>Suppose you create an action or a function that defines variables that will be used in other parts of your test or function library. You can add breakpoints to the action or function to see how the value of the variables changes as the test or function library runs. To see how the test or function library handles the new value, you can also change the value of one of the variables during a breakpoint.</p> <p> </p> <p>This can be done by following below simple steps:</p> <p> </p> <span class="fullpost"> <p><strong>Step 1: Create a New Action or Function: </strong>Open a test and insert a new action, or open a new function library and create a new function called SetVariables.</p> <p> </p> <p>If you are working in the Expert View, then follow Step 4 directly. If you are working in a function library, continue with Step 2 and Step 3.</p> <p> </p> <p><strong>Step 2: (For Function Libraries Only) Associate the Function Library with a Test:</strong> Make sure the function library is in focus. Select File > Associate Library ‘<Function Library Name>’ with ‘<Test Name>’. QuickTest associates the function library with your test.</p> <p> </p> <p><strong>Step 3: (For Function Libraries Only) Add a Call to the Function in Your Test: </strong>Add a call to the function by inserting a new step and typing the following in the Expert View: SetVariables.</p> <p> </p> <p><strong>Step 4: Add Breakpoints: </strong>Add breakpoints at the appropriate lines.</p> <p> </p> <p><strong>Step 5: Begin Running the Test:</strong> Run the test. The test or function library stops at the first breakpoint, before executing that step (line of script).</p> <p> </p> <p><strong>Step 6: Check the Value of the Variables in the Debug Viewer Pane:</strong></p> <p><strong></strong></p> <p><strong>Step 7: Check the Value of the Variables at the Next Breakpoint: </strong>Click the Run button to continue running the test. The test stops at the next breakpoint.</p> <p> </p> <p><strong>Step 8: Modify the Value of a Variable Using the Variables Tab</strong></p> <p><strong></strong></p> <p><strong>Step 9: Modify the Value of a Variable Using the Command Tab</strong></p> <p><strong></strong></p> <p><strong>Step 10: Repeat a Command from the Command History</strong></p></span> <div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1020744786956020830-61948143561549205?l=www.softwaretestingstuff.com' alt='' /></div>
<p><a href="http://feedads.g.doubleclick.net/~a/ifhUKirKh2BIYOVRCx-XwsNDuYo/0/da"><img src="http://feedads.g.doubleclick.net/~a/ifhUKirKh2BIYOVRCx-XwsNDuYo/0/di" border="0" ismap="true"></img></a><br/>
<a href="http://feedads.g.doubleclick.net/~a/ifhUKirKh2BIYOVRCx-XwsNDuYo/1/da"><img src="http://feedads.g.doubleclick.net/~a/ifhUKirKh2BIYOVRCx-XwsNDuYo/1/di" border="0" ismap="true"></img></a></p><img src="http://feeds.feedburner.com/~r/software_testing_stuff/~4/cU8v37NWHrM" height="1" width="1"/>Phttp://www.blogger.com/profile/11295088633938021751noreply@blogger.com0http://www.softwaretestingstuff.com/2009/08/debugging-action-or-function-in-qtp.htmltag:blogger.com,1999:blog-1020744786956020830.post-11500634240595813692009-08-08T00:30:00.001-07:002009-08-08T00:39:49.455-07:00Handling Run Errors in QTP<p>There are two types of Run Error message boxes that can be displayed during a run session in QTP. One is displayed if the problem is a pure VBScript syntax error. When a syntax run error message box is displayed, click OK in the message box and address the error in your step.</p> <p> </p> <p>The other message box can be displayed in a number of situations. It offers information about the error and a number of buttons for dealing with errors encountered:</p> <p> </p><span class="fullpost"> <p><strong>Stop:</strong> Stops the run session. The run results are displayed if QTP is configured to show run results after the run.</p> <p> <br /><strong>Retry: </strong>QTP attempts to perform the step again. If the step succeeds, the run continues.</p> <p> </p> <p><strong>Skip: </strong>QTP skips the step that caused the error, and continues the run from the next step.</p> <p> </p> <p><strong>Debug: </strong>QTP<strong> </strong>suspends the run, enabling you to debug the test and any associated function library that contains a function called by the test. You can perform any of the debugging operations described in this section. After debugging, you can continue the run session from the step where the test or function library stopped, or you can use the step commands to control the remainder of the run session.</p> <p> </p> <p><strong>Help:</strong> Opens the QTP troubleshooting Help for the displayed error message. After you review the Help topic, you can select another button in the error message box.</p> <p> </p> <p>The message box also recommends that you consider using Maintenance Mode if you think the error is due to intentional changes in your application and requires that you update multiple steps in your test or objects in your repository.</p></span> <div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1020744786956020830-1150063424059581369?l=www.softwaretestingstuff.com' alt='' /></div>
<p><a href="http://feedads.g.doubleclick.net/~a/zA1F7DJ9NRmvvTnrIneVrER8cPc/0/da"><img src="http://feedads.g.doubleclick.net/~a/zA1F7DJ9NRmvvTnrIneVrER8cPc/0/di" border="0" ismap="true"></img></a><br/>
<a href="http://feedads.g.doubleclick.net/~a/zA1F7DJ9NRmvvTnrIneVrER8cPc/1/da"><img src="http://feedads.g.doubleclick.net/~a/zA1F7DJ9NRmvvTnrIneVrER8cPc/1/di" border="0" ismap="true"></img></a></p><img src="http://feeds.feedburner.com/~r/software_testing_stuff/~4/_fAN36Bn9Ug" height="1" width="1"/>Phttp://www.blogger.com/profile/11295088633938021751noreply@blogger.com0http://www.softwaretestingstuff.com/2009/08/handling-run-errors-in-qtp.htmltag:blogger.com,1999:blog-1020744786956020830.post-41833927664427892712009-08-08T00:28:00.001-07:002009-10-05T10:40:20.374-07:00HP Diagnostics and LoadRunner Integration<p>The HP Diagnostics integration with LoadRunner allows you to monitor and analyze the performance of Java 2 Enterprise Edition (J2EE), .NET-connected, SAP, Oracle, and other complex environments.<strong><br /></strong></p><p><strong>Specifying the Diagnostics Server Details: </strong>The first time you use LoadRunner to capture J2EE or .NET diagnostics data, you need to identify the machine on which the Diagnostics Server in Commander mode is running, and the port that it is using for communication with LoadRunner. You must update this information if you want to integrate with a different Diagnostics Server in Commander mode, or if you change the port it is using. To update the LoadRunner configuration settings for HP Diagnostics:</p><p>1. Select Start > Programs > HP LoadRunner > LoadRunner to open the LoadRunner launcher window.</p><p>2. From the LoadRunner launcher window menu, select Configuration > Diagnostics for J2EE/.NET Setup to open the Diagnostics for J2EE/.NET Setup dialog box. Enter the details for the Diagnostics Server in Commander mode.</p><p>3. Click Test to verify that you entered the correct information for the Diagnostics Server in Commander mode and that there is connectivity between the Diagnostics Server in Commander mode and LoadRunner. Click OK to complete the configuration process.</p><p><strong>Configure LoadRunner Scenarios to use HP Diagnostics</strong></p><span class="fullpost"> <p>1. Before configuring your scenario for Diagnostics, ensure that the application server that you are monitoring has been started.</p> <p>2. In the Controller, open the relevant load test scenario (FIle > Open) or create a new scenario (File > New).</p> <p>3. Select Diagnostics > Configuration to open the Diagnostics Distribution dialog box.</p> <p>4. Set the percentage of Vusers to participate in the HP Diagnostics (J2EE/.NET Diagnostics) monitoring. The maximum percentage of Vusers for which HP Diagnostics (J2EE/.NET Diagnostics) data can be collected is 100%, unless you have enabled other types of diagnostics. In this case, the percentage of Vuser participation in HP Diagnostics (J2EE/.NET Diagnostics) cannot exceed the maximum of any of the other types of diagnostics that you enabled.</p> <p>5. In the Online & Offline Diagnostics section of the Diagnostics Distribution dialog box, next to J2EE/.NET Diagnostics, click Configure. The J2EE/.NET Diagnostics Configuration dialog box opens.</p> <p>6. Select Enable J2EE/.NET Diagnostics</p> <p>7. In the Select probes list, select the probes to be included in your load test scenario.</p> <p>8. If the Diagnostics Server (or a Diagnostics Server in Mediator mode in a distributed environment) is located behind a firewall, select There is a firewall between the mediator and the Controller, and enter the name of the MI listener server in the MI listener server box. If there is a firewall between the LoadRunner Controller and the Diagnostics Server involved in a load test, you must configure the Controller and the Diagnostics Server to use the MI Listener to enable the transfer of the offline analysis file.</p> <p>9. To capture a percentage of server requests which occur outside the context of any Vuser transaction select Monitor server requests.</p> <p>10. To investigate any issues that you have with the connections between the Diagnostics components, click the Troubleshoot Diagnostics for J2EE/.NET connectivity link. This will open the HP Diagnostics System Health Monitor in a new browser window.</p> <p>During a LoadRunner load test scenario, you can view HP Diagnostics data for the whole scenario or you can drill down to HP Diagnostics data from a particular transaction. After you have run your scenario, you can use HP LoadRunner Analysis to analyze offline Diagnostics data generated during the scenario.</p><p><span style="font-weight: bold;">Also See:</span> Other <a href="http://www.softwaretestingstuff.com/2009/10/important-loadrunner-tutorials.html"><span style="font-weight: bold; color: rgb(0, 0, 153);">LoadRunner Tutorials</span></a><br /></p></span><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1020744786956020830-4183392766442789271?l=www.softwaretestingstuff.com' alt='' /></div>
<p><a href="http://feedads.g.doubleclick.net/~a/q2JRP3z44UGG561_ZgqnF-USDCo/0/da"><img src="http://feedads.g.doubleclick.net/~a/q2JRP3z44UGG561_ZgqnF-USDCo/0/di" border="0" ismap="true"></img></a><br/>
<a href="http://feedads.g.doubleclick.net/~a/q2JRP3z44UGG561_ZgqnF-USDCo/1/da"><img src="http://feedads.g.doubleclick.net/~a/q2JRP3z44UGG561_ZgqnF-USDCo/1/di" border="0" ismap="true"></img></a></p><img src="http://feeds.feedburner.com/~r/software_testing_stuff/~4/EwHvz-vN8To" height="1" width="1"/>Phttp://www.blogger.com/profile/11295088633938021751noreply@blogger.com1http://www.softwaretestingstuff.com/2009/08/hp-diagnostics-and-loadrunner.html