AcdntlPoet 2700019V2G Visits (126)
Improved Kanban Board and Taskboard views in Rational Team Concert 5.0.1- Chris Goldthorpe and William Vorhees host this how-to for teams who use a combination of scrum and Kanban methods, showing how it's now easier to visually manage and optimize the flow of work with our new Kanban board and Taskboard views.
Soumya Y Shanthimohan 270004GAQS Visits (120)
First, make sure to have gone through the prerequisites for SAP testing. Refer the below link -
As you see in the link, you can have a maximum of only 50 virtual users on an agent for a SAP GUI test.
Beyond that, failures such as "connection errors", "SAP GUI Component not found" and "Invalid arguments" will start occurring during playback.
This is a result of how SAP has implemented the test automation API in SAP GUI.
Depending upon the script's complexity and the number of GUI components that are part of the script's scenario, it is likely that a script can be played back for only a lesser number of users. These limitations arise out of the SAP automation framework and not Rational Performance Tester (RPT) tool itself. The limitation holds good for other testing tools as well.
Since the limitation is on the on number of users per engine Java process, I tried setting up multiple agent engines in the same physical machine. This involved creation of multiple host aliases in the agent machine and then adding those hosts as locations to be used in user groups (Vertically Scaling an agent machine).
I personally saw that high capacity machine with multiple Agents did not resolve the issue.
Below are some recommendations while load testing a SAP GUI
Randy.Simmons 270002WWMT Visits (152)
My name is Randy Simmons and I am a Rational Collaborative Lifecycle Management (CLM) Support Engineer specializing in the Requirements and Quality Management Tool. I was tasked to create a Video Series to give internal IBMer’s and external customers a basic understanding and troubleshooting options to use when Java related problems occur using the CLM suite of Tools.
This “Non-Programmer's Guide to Troubleshooting Java in CLM” video series covers the topics below. It will make you more aware of the Java Tools available for download at IBM DeveloperWorks. It give you some background about how Java and JVMs work, what data Rational Support is looking for, and the understanding of how you would go about troubleshooting Java or Performance related issues.
Click through the titles to watch the four videos, or click play on the embedded playlist at the end:
1. Introduction to Java for CLM: This video is a recording from an education session "Non-Programmer's Guide to Troubleshooting Java in CLM". This video provides an introduction to Java for IBM Rational Collaboration Lifecycle Management V5.0 users.
2. Garbage Collection in Java for CLM: This video provides an overview of Java Garbage Collection for IBM Rational Collaboration Lifecycle Management V5.0 users.
3. IBM Diagnostic and Monitoring tools for Java with CLM: This video provides an overview of some Java diagnostic and monitoring tools for IBM Rational Collaboration Lifecycle Management V5.0 users.
4. Interpreting Unresponsiveness with Java for CLM: This video provides some examples of what to do when experiencing Java unresponsiveness with IBM Rational Collaboration Lifecycle Management V5.0.
Note: The above list is organized in the link to the embedded playlist below: http
On 12 August 2014, IBM
SQA Robot is part of SQA TeamTest . This bundle consists of SQA Robot and SQA Tester.
Since version 2002.05.00, Rational added a function SQAV
IBM Rational Robot Version 220.127.116.11 introduced the OpenComparator function in stand-alone mode. This version also introduced support for 64-bit operating system and made the step into the 64-bit world possible after the end of life of Windows XP. See The
Thanks to Hari, this was all possible.
Robot and her husbands
Consciously or unconsciously, we see history lightly in the form of a conflict between the old and the new. - Johan Huizinga.
Are you using IBM Rational Robot? Robot will go end of life 30 April 2016. That means that IBM no longer supports Robot. In this post I will point out what that could mean to you.
Robot has been out for more than 15 years. Since that time the software world has been changing rapidly and still is developing at breakneck speed. For many present-day applications, Robot is no longer the right tool. For example, Robot is a 32-bit tool. As such, Robot cannot work with 64-bit applications.
A European customer has used Robot from the beginning of this century to monitor their web applications. At that time, only Robot integrated with Tivo
Next: don't shoot the messenger
Therefore I think that a gradual switch over to RFT and RPT would be the best option I can think of. When you decommission an application that you have tested with Robot, you can replace Robot with RFT or RPT for the replacement. The same might apply when you make far-reaching changes to your applications.
Hopefully this post helps you to think about the future of your testing activities. If you'd like to discuss this further, leave a comment here or connect with me on Twitter @GunangWaney. You can also open a service request against IBM support, preferably before 30 April 2016.