About data correlation.
We record ONE big scenario, e.g. Login_Search_Create_Logout
Then we make all necessary correlations, data replacing, assign variables etc., and divide this scenario on blocks, like I said above.
Hi,
Thank you a lot for describing the way you are going - this is something that I have interest in.
I will appreciate it if you also can answer these questions:
a) If, say, login sequence changes, do you prefer re-record just it and than make data correlation to match the already existing one made initially or do you prefer to re-record the whole big scenario ?
b) Do you have any processes/enforcing rules/etc. that you follow to guarantee that, say, login sequence recorded a week ago still corresponds to reality? I.e. that requests were not added or removed during past week and that the data sent and received have the same format and contents? Any better practice other than re-record the sequence and compare it with the existing one? Maybe you have something to comment for the https://community.smartbear.com/t5/LoadComplete-Feature-Requests/Make-it-possible-to-compare-and-synchronize-requests-for/idi-p/138803 feature request?
Hi Alex,
First of all I want to clarify, that we perform load testing mostly to control changes outside of API of our applications. E.g. new encryption module was integrated or database version was upgraded or something else. I mean that API itself is rather stable for a very long period. For example authentication calls in our CRM system were not changed for the last 2 years or even more. So I think it easier for us to re-record scenario in the case of significant API changes. Small changes can be fixed manually.
As for your second question. We have a number of API tests, which cover basic functionality and check data structure. We run them before performing load testing to be sure that the application works at all.
