Community
Participate
Working Groups
Location does not contain port number. The location wizard and editor does not allow the user to specify a custom port number for the local/remote target host where the Agent Controller is configured and running. Instead, all locations are forced to use the default port number for specified in the Test preferences (see 194752). Since users can configure the port number for the Agent Controller, users should be able to customize the port number for the host specified in each location. For example, creating several locations referencing different hosts with different ports. This would require a change to the underlying Test Profile model to include the port number.
Included in 4.5 plan for the Test Tools project.
Jerome, I will handle this defect.
There is a useful "Test Connection" button to validate connectivity and availability of a remote AC, but it is buried on the Hosts preferences page under the Profiling and Logging preference folder. This location is pretty much undiscoverable by a Test user, and since AC test connectivity is just as important from Test as from Profiling and Logging, the current location seems like an odd place to (only) surface it. It is requested that this function be made available from one or preferably both of these places: 1. Right-click operation from the Test Navigator when a Location is selected. 2. A button within the Location editor. The reason this is very important is that there are configurations of a consuming testing product which will not include the Profiling and Logging function, including its preferences, which will result in loss of functionality.
Deferring to I7 as discussed by PMC/AG (http://wiki.eclipse.org/TPTP-AG-20080331#Test_Project).
(In reply to comment #0) > This would require a change to the underlying Test Profile model to include the > port number. Adding dependency from test model update defect.
(In reply to comment #5) > (In reply to comment #0) > > > This would require a change to the underlying Test Profile model to include the > > port number. > > Adding dependency from test model update defect. > It is not clear that the model needs to change. Location has a variable number of name/value pair properties so these kinds of things can be provided without model changes. I suggest you exploit this design feature and then figure out how to deal with backward compatible models that are missing the value.
(In reply to comment #6) > (In reply to comment #5) > > (In reply to comment #0) > > > > > This would require a change to the underlying Test Profile model to include the > > > port number. > > > > Adding dependency from test model update defect. > > > > It is not clear that the model needs to change. > Location has a variable number of name/value pair properties so these kinds of > things can be provided without model changes. > > I suggest you exploit this design feature and then figure out how to deal with > backward compatible models that are missing the value. > I will look at adding this as a variable, instead of changing the model.
(In reply to comment #7) > I will look at adding this as a variable, instead of changing the model. Adding a 'port' property to the 'General Properties' property group is one way to export this configuration to the user. However, the user would have to navigate to the General Properties tab to view/modify the value, which is not very user friendly since the host name is on the Overview tab.
Given Harm's concerns about extending the Test model, I will investigate our our consumers configure the Agent Controller port for multi-host scenarios before continuing. The dependency on test model update defect was never added.
(In reply to comment #9) > The dependency on test model update defect was never added. https://bugs.eclipse.org/bugs/show_bug.cgi?id=221097
Hours updated for triage and design discussions with Harm.
Deferring to future as approved by the TPTP PMC (http://dev.eclipse.org/mhonarc/lists/tptp-pmc/msg04926.html).
Note, if the port number is to be added to locations, the underlying Test Profile model will need to be updated as well, including the Rose model (/org.eclipse.tptp.platform.models/rose).
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. Since this defect is more than 2 years old, it may be no longer relevant. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this defect is resolved as WONTFIX. If this defect is still relevant and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.
Closing.
