« Return to Thread: Utterly fail to set up a TPTP URL Test
Utterly fail to set up a TPTP URL Test
by Andre
::
Rate this Message:
Hi there
I am busy with TPTP for 2 full work days meanwhile, trying desperately to invoke one simple TPTP URL Test. After failing me with dozens of setups I ended up having a very very simple project just kindly asking for one basic HTTP GET of www.eclipse.org (localhost:8080 ain't much cooperative either) and still it refuses a decent run giving me "fail rc=400". So reponse code is 400, bad news.
Some further details.
First I was trying to apply closely the steps discussed here...
Creating URL tests: http://www.eclipse.org/tptp/home/documents/tutorials/viewlets/v4.1/EW-URLTest/EW-URLTest/EW-URLTest_viewlet_swf.html
This tutorial gives good theoretical information to start with but completely fails in supplying a practical approach. Because the wizard called 'Test/Recordings/HTTP Recording' mentioned in the tutorial simply doesn't exist in the current TPTP platform (anymore).
But I don't regard this as severe since I guess it is quite possible to build up an TPTP URL Test manually.
I did this by creating...
* Java project
* folder testing
* wizard 'Test/TPTP URL Test' named \testing\testing.testsuite
* creating precisely one http GET request within that test
* supplying www.eclipse.org as hostname (PORT 80) (among countless other tries, e.g. localhost:8080)
* absoulte path: / (among countless other tries such as index.html on my local machine, which
was successfully delivered by asking for http://localhost:8080/index.html using firefox, of course)
* no HTTP GET Headers supplied
* adding this http request in "Behaviour"
* Auto-generated the firing class by "Generate" (context-menu) (in Test-Perspective )
* and finally Run it (in Test-Perspective )
this yielded a log file named \testing.execution that keeps saying "fail". It cheekingly fails when
assertTrue(text, response.getCode() < 400 && response.getCode() > 0);
saying the server (localhost or any internet server such as www.eclipse.org) replied with rc=400, which means "bad request"
I "burned" money worth of 2 work days with this and my first feedback to my manager was: "TPTP is still in its infancy and will require a year or so to become a tool we could consider doing our profiling with." Okay guys. If this does give you some itches, please tell me where I am going wrong. My eternal gratitude to you would be garantueed.
Even further questions regarding my setup steps could be helpful. At some times this is all that is needed.
Cheers and have a good one
André
I am busy with TPTP for 2 full work days meanwhile, trying desperately to invoke one simple TPTP URL Test. After failing me with dozens of setups I ended up having a very very simple project just kindly asking for one basic HTTP GET of www.eclipse.org (localhost:8080 ain't much cooperative either) and still it refuses a decent run giving me "fail rc=400". So reponse code is 400, bad news.
Some further details.
First I was trying to apply closely the steps discussed here...
Creating URL tests: http://www.eclipse.org/tptp/home/documents/tutorials/viewlets/v4.1/EW-URLTest/EW-URLTest/EW-URLTest_viewlet_swf.html
This tutorial gives good theoretical information to start with but completely fails in supplying a practical approach. Because the wizard called 'Test/Recordings/HTTP Recording' mentioned in the tutorial simply doesn't exist in the current TPTP platform (anymore).
But I don't regard this as severe since I guess it is quite possible to build up an TPTP URL Test manually.
I did this by creating...
* Java project
* folder testing
* wizard 'Test/TPTP URL Test' named \testing\testing.testsuite
* creating precisely one http GET request within that test
* supplying www.eclipse.org as hostname (PORT 80) (among countless other tries, e.g. localhost:8080)
* absoulte path: / (among countless other tries such as index.html on my local machine, which
was successfully delivered by asking for http://localhost:8080/index.html using firefox, of course)
* no HTTP GET Headers supplied
* adding this http request in "Behaviour"
* Auto-generated the firing class by "Generate" (context-menu) (in Test-Perspective )
* and finally Run it (in Test-Perspective )
this yielded a log file named \testing.execution that keeps saying "fail". It cheekingly fails when
assertTrue(text, response.getCode() < 400 && response.getCode() > 0);
saying the server (localhost or any internet server such as www.eclipse.org) replied with rc=400, which means "bad request"
I "burned" money worth of 2 work days with this and my first feedback to my manager was: "TPTP is still in its infancy and will require a year or so to become a tool we could consider doing our profiling with." Okay guys. If this does give you some itches, please tell me where I am going wrong. My eternal gratitude to you would be garantueed.
Even further questions regarding my setup steps could be helpful. At some times this is all that is needed.
Cheers and have a good one
André
« Return to Thread: Utterly fail to set up a TPTP URL Test
| Free embeddable forum powered by Nabble | Forum Help |
