Hi Andre,
I regret that you are having issues with TPTP. I would like to discuss this a bit more to fully understand your issues before you move on from the project.
First, what version of TPTP are you using? Are you using the Agent Controller or Integrated Agent Controller? What OS, JRE (version/vendor), browser (version/vendor) are you using?
When you were recording on localhost:8080 and received the 400 return code (assuming the web server was running locally), were you recording with Internet Explorer V7? If so, did you see the following TPTP release note:
http://www.eclipse.org/tptp/home/downloads/4.5.0/documents/releasenotes/releasenotes4_5_0.html#4_CTI_8
As TPTP enhancement https://bugs.eclipse.org/bugs/show_bug.cgi?id=139699 indicates, the URL recorder and test type currently does not support complex transactional scenarios. However, these scenarios are currently supported one of our consuming products, IBM Rational Performance Tester. Unfortunately, we have not had sufficient project resources to deliver this enhancement in the open-source. However, one of the benefits of open-source software is community contributions. Would you or your company be interested in contributing a patch for this enhancement?
PS
__________________________
Paul Slauenwhite
IBM Toronto Lab, Canada
Internet: paules@...
Telephone: (905) 413-3861
Tie Line: 313-3861
__________________________
Please consider the environment before printing this email.
Andre <Andre.Kuhn@...>
Hi there
So I have given up any hope of resolving this. We abandoned our goal of
profiling our current project for our customer using TPTP. This brought
about our decision:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=139699
"The org.eclipse.hyades.test.http.runner.HttpResponse class does not expose
the complete HTTP response. For example, session ID. Thus it is impossible
to modify a recorded http session to replace the recorded sessionid with the
sessionid returned by the login http request. This makes TPTP url testing
impossible for our framework.
URL Test was originally intended to do "URL blasting", and does not support
a number of capabilities that make it suitable for more complex
transactional scenarios that require data correlation (for example). There
will need to be some additional APIs added to fully support data
correlation, and as such, a group of related defects are being targeted for
the next release, 4.3. The intent in those related improvements will be to
make it possible via additional API and completed functionality for a user
(or consuming tool) to program data correlation in by editing the generated
test, but not to have the URL test gen provide automatic data correlation in
its generated tests. "
Our problems with TPTP Url Test start at an even earlier stage. Meanwhile I
was able to successfully request an HTTP GET to www.eclipse.org (path: /).
But localhost:8080 still fails with Code 400. Even if we could solve this
after hours (and a huge pile of money later) passed by, we would then run
into the "session-trouble" outlined above.
Okay, so good luck with this platform. I sincerely hope you guys will do
good for the future.
Cheers
André
--
View this message in context: http://www.nabble.com/Utterly-fail-to-set-up-a-TPTP-URL-Test-tp21357057p21372662.html
Sent from the Eclipse TPTP - Testing Tools - Dev mailing list archive at Nabble.com.
_______________________________________________
tptp-testing-tools-dev mailing list
tptp-testing-tools-dev@...
https://dev.eclipse.org/mailman/listinfo/tptp-testing-tools-dev
_______________________________________________
tptp-testing-tools-dev mailing list
tptp-testing-tools-dev@...
https://dev.eclipse.org/mailman/listinfo/tptp-testing-tools-dev