vinayhs 270002JFCW Visits (1170)
Here are typical steps that needs to be followed to set up TCP recording in Rational Integration Tester ( RIT ) . Suppose the TCP/IP application is running on the port 9089 on a <Application host>
4. Once the above configuration is set , start the recording on the Logical Component that was created. you should be able to see the messages in the recording stuido of RIT.
Rajeshavanthi 2700022MCX Visits (1248)
In a very typical scenario, To create a test, many testers currently sit at a PC and alternate between completing an action in the application under test and writing the step on a notepad. When the test is complete on paper, the tester (or in some cases an administrative assistant for the testing group) types the steps into a standard test template, frequently using either Microsoft Word or Microsoft Excel. Following this procedure, a single manual test is essentially written twice.
Eliminating the need to write each test twice can save you time for other testing.
In addition to writing tests twice, much time is spent adapting existing tests for similar new tests. For example, a tester might create a test to log into the application under test as an administrator, and then adapt that test to log into the application under test as a regular user. This adaptation typically takes one of two forms:
• Open the existing test, edit steps as needed, and save the test with a new filename.
• Open a new test template, copy steps from the existing test, edit steps as needed, and save the new test.
Reducing duplication among many tests reduces the time you spend maintaining test scripts.
Testers typically receive many new software builds during a development cycle, often at an increasingly rapid rate toward the end of the cycle.
When a build contains a new feature or a fix that requires modifying the steps of a test, all of the tests that relate to the new feature or fix must be updated to reflect the change in the application under test. Although this update process is not difficult to manage when only a few tests require updating, when dozens (or hundreds) of tests are affected by changes to a commonly used area of the application under test, such as a login screen, updating can be very time-consuming. Eliminating or reducing the work that is required to keep many tests up to date can save you time for additional testing.
As you increase the efficiency of your testing effort, you can use the saved time to conduct additional tests. Rational Quality Manager can help you work more efficiently in each of the testing activities:
• Creating tests: Rational Quality Manager helps you to manage reusable content and use it in similar tests. As a result, you spend less time authoring tests.
• Running tests: Rational Quality Manager associates text to be typed in the application under test with an execution step. Rational Quality Manager also associates verification text with a test step, and then compares the comparison. Rational Quality Manager provides test data variables so that you can define a test once and run it many times to accommodate different data input values. These features save you time typing in the application under test, comparing actual to expected results, and testing different data values.
• Reporting test results: Rational Quality Manager provides customizable reports that reflect test result data from all phases of the project. These reports save time that you would have spent manually tabulating test results for reporting.
• Maintaining tests: Rational Quality Manager reduces the amount of required test maintenance by storing reusable content only once. As a result, you spend less time updating many similar tests.
Cause: The Java Plugin is being blocked by Chro
PaulLiskay 06000284J3 Visits (1124)
How to do a silent install of IBM Rational Performance Tester (RPT), or the RPT Load agent is a common topic. To do one on Linux is a bit trickier than on Microsoft Windows because most people are more familiar with Windows than Linux. Don't worry, it's still relatively easy and straight forward.
The approach I took was:
1. download IM 1.8.2 and the RPT 8.7 Agent repositories
2. copy from Windows machine to Linux machine using pscp, a Windows version of scp (secure copy)
3. install the standalone Installation Manager 1.8.2 for Linux
4. run that Installation Manager in GUI mode to create a response file needed for the silent install
5. then run Installation Manager from the command line using the response file generated in step 4 to install the agent silently.
Here's the steps
1. download IM 1.8.2 from htt
2. copy to Linux machine, I'm copying to /tmp/IM182
3. unzip on Linux machine to /tmp/IM182
[root@citmx373 IM182]# unzip age
4. install IM
[root@citmx373 IM182]# pwd
5. copy the agent to the Linux machine, I'm copying to /tmp/RPT87Agent
6. unzip it
[root@citmx373 RPT87Agent]# pwd
7. run IM in GUI mode to create a response file
[root@citmx373 eclipse]# pwd
8. Verify creation of response file
root@citmx373 eclipse]# ls /tmp
9. Do the silent install using the response file just created
[root@citmx373 eclipse]# pwd
10. Verify installation.
Check that the majordomo.config file exists and has the right hostname of the RPT workbench. Then check if the agent is started.
[root@citmx373 Majordomo]# pwd
11, Check agent status on RPT workbench by clicking on the agent status icon
RohitBalduwa 2700066W8H Visits (1152)
The Collaborative Lifecycle Management (CLM) upgrade scripts - Jazz Team Server (JTS), Change and Configuration Management (CCM), Quality Management (QM), Requirements Management (RM) provides an additional command line para
This new command line para
The upgrade scripts also provides other parameters(such as -noPrompt -noStepPrompt –overwrite -noVerify)
As a result, the automation of the upgrade scripts can be achieved by prevent all the user interactions.
An example command to perform JTS upgrade by suppressing all the user interactions:
However, vvc_upgrade.bat, dm_upgrade.bat, and relm_upgrade.bat don't support the noEditor option.Therefore, running these three upgrade batch files still require manual user interaction.