LoneWanderer04
Occasional Contributor
Joined 5 years ago
User Profile
User Widgets
Contributions
Re: Vis.js graph testing using TestComplete
I talked to the dev and they are using the canvas object for vis.js, and I saw your reply to: https://community.smartbear.com/t5/TestComplete-Functional-Web/How-to-work-with-Canvas-Object/td-p/171128 Unfortunately due to the requirements I have, I don't know if there's much I'll be able to do with TestComplete itself other then recording and replaying or something similar. since I need to do more then verify the graph, I need to be able to click nodes, drag, etc. the various nodes that are being drawn in order to do other functionality. The problem with recording that I encountered already is that if the screen is at all different size then what the test was originally recorded on, the test will fail as the coordinates are different.1.2KViews1like0CommentsVis.js graph testing using TestComplete
Hello everybody! I'm working on a piece of software that has vis.js graphs implemented. The most I can get from non-calculated fields is the X and Y offset as they are represented in the vis.js graph itself, so -250, -50 with 0,0 being the center of the graph. Does anybody know any way to get TestComplete to be able to recognize the offsets at the very minimum, or any other more efficient way of testing a graph? By default it's clicking at the pixel coordinates I pass into Click or HoverMouse, so -250, -50 is off the graph when I try to FindElement on the graph element, then pass in those coordinates to Click or HoverMouse. The other issue is that I can't use pixel coordinates because we want this to run on multiple computers if possible, so the pixel coordinates would be different on each, causing unexpected actions.Solved1.4KViews0likes5CommentsRe: ReadyAPI - "Remote host terminated the handshake" on server with SNI enabled
If I was provided a license in the original purchase for 3.3.0 ReadyAPI and 4.9 License Server for a floating license, am I able to update both of those to use the newest ReadyAPI? I noted that 3.5 needs the 5.0+ license server, and wanted to make sure the key I was given would work on later versions before I download everything again.4.9KViews0likes3CommentsRe: ReadyAPI - "Remote host terminated the handshake" on server with SNI enabled
Do you have a link where I can download that specific version? I checked the downloads page and it only has 3.5.0 of ReadyAPI. Also does that version work with Protection! 4.9.4 version of the Floating License manager? That and 3.3.0 were all we were given when we purchased the product a few weeks ago.16KViews0likes5CommentsReadyAPI - "Remote host terminated the handshake" on server with SNI enabled
Hello everybody, We are setting up a test suite using ReadyAPI 3.3.0. It's making HTTPS Rest calls, using NTLM authentication which I set up and seems to succeed. The issue I'm running into is that every other call fails due to the following error: Error getting response; javax.net.ssl.SSLHandshakeException: Remote host terminated the handshake. I've dug into a lot of solutions at this point, and I'm running out of ideas. I tried editing the ReadyAPI vmoptions in the bin folder to add: -Dsoapui.https.protocols=SSLv3,TLSv1.2 -Dsoapui.https.ciphers=TLS_RSA_WITH_AES_256_CBC_SHA256 I've tried adding the following to the ready-api.bat file: set JAVA_OPTS=%JAVA_OPTS% -Dsoapui.https.protocols="TLSv1.2" set JAVA_OPTS=%JAVA_OPTS% -Djavax.net.debug=all set JAVA_OPTS=%JAVA_OPTS% -Djdk.tls.client.protocols="TLSv1.2" set JAVA_OPTS=%JAVA_OPTS% -Dhttps.protocols="TLSv1.2" But none of these solutions have worked so far. Is there anybody else that has run into this issue, and how you got around it to fix it?Solved22KViews0likes13CommentsRe: ReadyAPI - "Remote host terminated the handshake" on server with SNI enabled
So been continuing to look at this. The server configuration is going through a Load Balancer on the specific server I run the tests against. We shut off one of the nodes completely and that seems to make it pass, so later today we are going to look into the Load Balancer configuration, since it appears that something is up with having calls go through multiple nodes. UPDATE: It appears to be due to the fact that the two main servers we use are configured with SNI. According to https://stackoverflow.com/questions/31245378/ssl-request-fails-from-soap-ui-works-with-fiddler-proxy, this seems to be due to ReadyAPI's Apache HttpClient 4.1.1 still not supporting that behavior (at least according to everything we've checked). My question evolves to the following: Does anybody know a way of overwriting Java in ReadyAPI so I manually overwrite the SNI to what I need? SNIHostName17KViews0likes7CommentsRe: ReadyAPI - "Remote host terminated the handshake" on server with SNI enabled
Its a good thought, but that was one of the first things I checked, the Raws of the calls are the same, but it has nothing to do with delays from what I've seen. I've waited upwards of multiple minutes between calls, as long as the last call was a failure due to handshakes, the next call will succeed. The more odd detail is if I run all the API calls together in a suite, only the first call in the suite will get the handshake error, the rest will all succeed even though a lot of them of being called one after the other in quick succession, further putting the timer idea as not being the main problem. I'll reach out to the server guys to see if there is anything on the logs, but they were telling me that they think it's on ReadyAPI's side since they weren't seeing anything the other day. From what I can tell, the response just doesn't even go out when that happens, since the handshake fails right away, so it makes sense the server didn't have anything in depth.17KViews0likes9CommentsRe: ReadyAPI - "Remote host terminated the handshake" on server with SNI enabled
I'll try to clarify as much as I can. We have a test suite where all the REST calls are done via NTLM. The current issue I'm encountering is if I execute an API call, every other run gives me the error I listed. Nothing changes between attempts, other then I'll get a success, then "Remote host terminated the handshake" then success, then "Remote host terminated the handshake". The two scenarios I've tried is running each call individually which does the above behavior, and running all the calls together in a full suite of tests, at which point the first API call in the suite gets that error. Example: 1st run: POST *endpoint 1* - Success, I get a JSON package returned. 2nd run: POST *endpoint 1* - failure Error getting response; javax.net.ssl.SSLHandshakeException: Remote host terminated the handshake 3rd run: POST *endpoint 1* - Success, json package from 1st run returned 4th run: POST *endpoint 1* - failure Error getting response; javax.net.ssl.SSLHandshakeException: Remote host terminated the handshake17KViews0likes11Comments