|
Jyothsna Posts: 3
6/3/2024
|
Hi everyone,
When recording and validating a script that includes WebSocket sessions, I am receiving the following errors in the script editor:
Line: 10, Position: 8 "The element 'Transaction' has invalid child element 'WebSocketSession'." List of possible elements expected: 'SessionContainer, Loop, Transaction, Session, Action, Rendezvous, ResetConnections, Condition, While, Page, SetCookie, Delay, Comment, AbortIteration, Validators'."
Line: 13, Position: 10 "The element 'Page' has invalid child element 'WebSocketSession'.
It appears that the XML schema does not contain the WebSocketSession or WebSocketFrame elements, which results in validation errors whenever WebSocket sessions are recorded as part of the script.
Note: When I record HTTP requests, the script is recorded and validated in the Script Editor without any errors. Issue is only, when recording WebSocket requests, it says elements are not supported in the schema.
Has anyone else encountered this issue? If so, how did you resolve it? Is there an update or workaround available to include WebSocket sessions and frames in the XML schema correctly?
Any assistance would be greatly appreciated!
Thanks in advance.
|
|
|
0
link
|
|
George @StresStimulus Administrator Posts: 568
6/3/2024
|
The screenshot suggests that the script editor detected a mismatch between the test configuration XML script and the internal .xsd schema for validating manually written customer XML. The validation message is a warning caused by the .xsd schema not being updated. However, it can be ignored. It does not affect the WebSocket operation. For optimal use, we advise using the script editor only for manually created XML. If your XML was created through the UI, using the script editor is unnecessary, as the automatically created XML is always correct. This will help streamline your workflow.
Support for web sockets has been significantly upgraded in StresStimulus v6.0 (currently in public beta and will be released later this month). The .xsd schema will also be updated at that time.
- Cheers
|
|
|
0
link
|
|
Jyothsna Posts: 3
6/3/2024
|
Hi George,
Thank you for the information. I appreciate the clarification regarding the schema warning.
I would like to mention that the script in the script editor which is currently failing, was created automatically when we recorded the WebSocket traffic using StressStimulus 6.0. It was not manually created. Despite this, the script is failing.
The reason for validating the auto-recorded script was that we think it's affecting WebSocket operations. Initially, a few auto-Correlations are working fine and correct parameters are passed as part of the requests. However, after a few WebSocket requests, the extractors in auto-correlation are fetching the correct values, but when passing the parameter value to the requests, the opening quotation mark is missing. We suspect this could be a tool issue, as we found that the script recorded was failing to validate.
Could you please provide further assistance on resolving the issue? Do we need to wait for the release of the schema update for this to get fixed?
Thank you.
|
|
|
0
link
|
|
George @StresStimulus Administrator Posts: 568
6/4/2024
|
Thank you for your update.
In my previous response, I meant to say that the script created through UI and not manually has the correct syntax, and the warning displayed by the script editor about incorrect syntax can be ignored. This is not to say that your script (even with correct syntax) will always create requests required by your application and scenario while executing.
Based on your update that the script is failing, I assume that while the script is fully executed (not throwing runtime execution error causing the test to stop), the server may return application errors, or a transaction on the server is not completed according to your application specification. If this is the case, such errors are caused by the script not being correctly configured, which makes it incompatible with your application scenario. For example, it can miss a manual correlation or parameterization, which your scenario requires to avoid compromising a duplicate constraint. You can try parameterizing your script as described https://support.stresstimulus.com/display/doc59/Creating+a+Parameter
Our support engineer must inspect a script configuration during a screen-sharing session to fix it completely. If you are evaluating StresStimulus, contact sales to arrange a POC session. If you are an existing customer, contact your support rep.
- Cheers
|
|
|
0
link
|
|
Jyothsna Posts: 3
6/4/2024
|
Thanks George. I have requested for a demo yesterday and waiting for the email confirmation yet. We can screenshare and show the issues we are experiencing during the demo.
|
|
|
0
link
|