Posts

Performance Testing using HP LoadRunner

hploadrunner-300x243 Performance Testing using HP LoadRunner

HP LoadRunner

Join us at VanQ this Thursday to discuss Performance Testing using HP LoadRunner. Our own technical manager, Larry Ng, will be sharing his hands-on experience using real-life examples.

If you haven’t made it to a VanQ event yet, this is your chance. VanQ hosts a free event each month in Vancouver to discuss software testing best practices. We regularly sponsor the event as it brings in excellent speakers and a strong network of local software testing professionals.

The event starts at 6:45PM on Thursday, April 28, but come early to meet local testing experts.

To RVSP, please visit VanQ’s website.

Hope to see you there!

Quick Test Professional 11 Review

QTP-11-177x300 Quick Test Professional 11 ReviewQuick Test Professional (QTP) is an automated functional Graphical User Interface (GUI) testing tool created by the HP subsidiary Mercury Interactive that allows the automation of user actions on a web, client based, or desktop application. QTP can be integrated with Quality Center and the automated test cases suite can be executed directly from Quality Center.

Quick Test Professional 10 came with exciting new features like Local System Monitoring while Running Your Tests, Versioning, QTP 10 integration with QC, and Call Actions Dynamically during the Test Run. People from the test automation community were expecting new features in QTP 11 like the long awaited support for Firefox, functional library load at run time, and identification of objects using XPATH property.

Finally QTP 11 is out with following exciting new features!

Regular Expression Evaluator:
The use of regular expressions in the dynamic object properties has been simplified using new Regular Expression Evaluator. For applications which require a lot of regular expressions in automation, upgrading to QTP 11 will definitely help in simplifying things and solving complex puzzles.

Visual Relation Identifier:
After upgrading to QTP 11, automation engineers that were working on QTP 10 or previous versions will see a new property in the Object Repository Visual Relation Identifier. This feature helps to identify objects based on the relationship with other objects in the application under test.
Earlier we had to write logic to find objects in the application. This was then used during execution of automated test cases as most of these types of objects have an index value associated with them. Now using the visual relation identifier we can identify objects based on their relationships with other objects. The scenario above is just one example of how this feature can be helpful in identifying other complex objects in the application.

Enhanced Result Viewer:
QTP_11-Results-Viewer1 Quick Test Professional 11 Review

The Result Viewer has a completely new look as compared to Result Viewer in QTP 10. The new Result Viewer displays summary data and pie charts for current and previous runs with quick links to open results for the previous runs. The Run Time Data Table also has enhanced look which is now displayed under the executive summary section.

Load Function Libraries at Run Time:
Like the ‘LoadAndRunAction’ feature which was added in QTP 10 (which we used lot in long END-to-END automation scenarios), QTP 11 has taken the next step in this direction which makes scripts more dynamic. This new functionality allows run time loading of the functional library using the ‘LoadFunctionLibrary’ statement.

Firefox support:
QTP 11 now supports Firefox 3.6; however, you have to install a patch before you can automate on Firefox. In our experience, Firefox 3.6 support by QTP 11 works pretty well.

Automatic Parameterization:
Now we can instruct QTP to automatically parameterize input data by enabling this feature during recording. If you do a lot of parameterization in test scripts, this will save time.

Silverlight Support:
Automation support for Silverlight is available in QTP 11. The Silverlight add-in is displayed in the add-in manager after upgrading QTP from previous versions. One good thing is that the Silverlight add-in is provided by HP, not like the flex add-in that is provided by Adobe. So we can expect better support for Silverlight applications by QTP.

Extensibility Accelerator:
Using the Extensibility Accelerator we can design automation support for custom developed web-controls which are not supported by object recognition mechanism of QTP.

XPath and CSS:
Like Selenium, now QTP can also recognize objects using the XPath and CSS properties of the objects in the application.

Integration with Service Test:
Service Test scripts can now be called in QTP scripts. This helps in automation of scenarios which include SOA service steps along with GUI functional steps in one script.

Conclusion:

As per our experience, the upgrade from QTP 10 to QTP 11 is a painless transition. With the features mentioned above, like support for Firefox, Visual Relation Identifier, Regular Expression Evaluator, and the enhanced Result Viewer, it’s worth upgrading your existing automation suite. QTP 11 can now be adopted for automation of Silverlight application. If you’re already using QTP 10, then the upgrade to QTP 11 is free of charge and definitely worth the effort.

If you’d like help setting automated software testing with QTP 11, please give us a call or send us an email at info@optimusinfo.com.

Software Testing at Facebook

facebook_bugs-300x225 Software Testing at FacebookFacebook is famous for its rapid development and frequent releases. That agile software development cycle requires diligent software testing and bug tracking. Steven Grimm, a Test Engineering Tech Lead at Facebook, has shared his experience using a combination of manual and automated tools while developing at Facebook.

In order to manage the steady stream of updates, Facebook has implemented a hybrid system of automated and manual tests. This system is built of several tools (mentioned below) that interface with their bug tracking software. By integrating testing with their bug tracking software, they are able to efficiently identify which tests are failing and which engineers can resolve the issues. The suite will also run tests on edited code and include the test results when a patch is submitted for review.

Software testing tools used at Facebook:

  • For PHP they use PHPUnit and have developed over 2200 test cases. They are run both manually by developers and automatically by the back-end system.
  • For browser-based testing they use the Watir Framework. They use Watir to both double check that backend rules have been followed and to semi-automate tests that include manual form entry.
  • For JavaScript testing they have started using JSSPec but it’s still in the early stages.
  • For backend testing they use a combination of open source and internally built C++ frameworks. Backend tests are built right into the build process and report error automatically.

Facebook is very proud of their frequent release cycle, they take a delay in pushing a release to production very seriously; however, the engineer in charge of the release may hold back if there are issues.

Facebook’s other major concern is protecting user’s privacy, so they have redundant tests at both the back-end and front-end. Even with this redundant testing, Facebook has still run into problems protecting user’s privacy. We can learn a lot from Facebook’s rapid development/testing cycle, so thank you to Steven Grimm for sharing his experiences.