recent posts recent posts - RSS

11 days ago
Topic:
Replaying scripts in D365 - F&O Application

George @StresStimulus
George @StresStimulus
Administrator
Posts: 566
Visble response size difference is one indication of an error as described https://support.stresstimulus.com/display/doc60/Resolving+Errors+and+Warnings. You may be missing a parameter.


- Cheers
14 days ago
Topic:
Replaying scripts in D365 - F&O Application

sachpatel
sachpatel
Posts: 14
The recording or parameterisation isn't the issue. Because the sales order gets created in the UI. The problem is being able to handle the notifications that appear in the header. I have been able to work on getting one type of notification working. However, I'm not able to handle notifications that appear in the "Action Center" using the same looping method. It's not a HTTP 500 I am seeing now. But the response sizes are visibly different, i.e the replayed version is much smaller. Any suggestions?
25 days ago
Topic:
Replaying scripts in D365 - F&O Application

sachpatel
sachpatel
Posts: 14
I have recently been recording scripts against D365 F&O application using SS v5.9. The initial recording is fine. However, there is a "Refresh" request that fails. I have put the Refresh request within a "Do...while" loop until it finds a specific text in the response. However, when I replay the script, it fails with a HTTP 500. When I tried testing the script with the original recordings of the "Refresh" requests, which were a few, it passed. It only failed because the text still didn't appear after the 3rd attempt of sending the Refresh request.

I noticed in the request there are a couple of values which are not auto correlated: "CallBackId", "LastAcknowledgedSequenceNumber" and "SequenceNumber". It looks very difficult to correlate these values from when they first appear because they can jump up by several numbers in between requests.

Has anyone else experienced this problem? If so, how was it overcome?


Thank you.
28 days ago
Topic:
how to rerecord and append existing test case

Sudha chow
Sudha chow
Posts: 2
Thanks George will try that
6/19/2024
Topic:
how to rerecord and append existing test case

George @StresStimulus
George @StresStimulus
Administrator
Posts: 566
One way to append new recorded transactions to an existing script is as follows:

1. Record a new script in the same test (described: https://support.stresstimulus.com/display/doc59/Recording+Test+Case)
2. Clone the transactions from the new script to the existing one (either by cloning, described: https://support.stresstimulus.com/display/doc59/Clone+Objects, or by drag-and-drop, described https://support.stresstimulus.com/display/doc59/Drag+and+drop+cloning)

However, it will only work if your new recorded transaction is compatible with the existing script. Otherwise, your application will not be able to process the new script playback.
6/17/2024
Topic:
how to rerecord and append existing test case

Sudha chow
Sudha chow
Posts: 2
how to rerecord and append existing test case

I get options of add to existing test case but prompts me to record from the beginning. Any help is appreciated
6/4/2024
Topic:
Issue with WebSocketSession Element in XML Schema

Jyothsna
Jyothsna
Posts: 3
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.
6/4/2024
Topic:
Issue with WebSocketSession Element in XML Schema

George @StresStimulus
George @StresStimulus
Administrator
Posts: 566
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
6/3/2024
Topic:
Different ramp-up for different scripts

George @StresStimulus
George @StresStimulus
Administrator
Posts: 566
To create different ramp-ups for different scripts, StresStimulus has a Multi-load pattern where you can specify multiple step-loads and bind each script with a different load as described https://support.stresstimulus.com/display/doc59/Multi-load+pattern
You have 16 scripts for your situation so you can create 16 step-load patterns. Then, assign each script to the corresponding step load.
If you need further assistance to create the multi-step load, let me know your specific requirement, and I will help you create it.
6/3/2024
Topic:
Issue with WebSocketSession Element in XML Schema

Jyothsna
Jyothsna
Posts: 3
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.
6/3/2024
Topic:
Issue with WebSocketSession Element in XML Schema

George @StresStimulus
George @StresStimulus
Administrator
Posts: 566
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
6/3/2024
Topic:
Different ramp-up for different scripts

Unregistered User
Unregistered User
Posts: 514
Currently, for our test, we use Step-load test scenario where we gradually ramp up users and then run a test for peak hour.

However, we are not sure how the ramp-up happens. We want to ensure the script with fewer users are ramped up slowly.

Can we control the ramp-up for each script (we have 16) in any way?
6/3/2024
Topic:
Issue with WebSocketSession Element in XML Schema

Jyothsna
Jyothsna
Posts: 3
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.