Forum Discussion
AlexKaras
15 years agoChampion Level 3
Hi Tim,
This is my understanding that may be not completely correct, but I see the reason in essentially different functionality. Regular UI test functions in the terms of UI elements and (user) actions over them. User does not care what is going on from the system point of view when, for example, the combo-box item is selected. The only thing the user is interested in is how applicaton reacts on the selected combo-box item change from the business/functional point of view.
On the contrary, HTTP load testing does not care what is going on with the tested application from the functional point of view. Even more, HTTP load testing does not care if it is the same application or not that sends requests to the server. The only thing HTTP load testing cares of is what was requested from the server and in what order the requests were send. And as long as the content of the requests and their order remains unchanged, HTTP load test would not require changes if, for example, developers change the tested (AJAX) application so that it requests data not on the selected combo-box item change, but on the button click. It is evident, that the mention application change requires adoption of the regular UI test.
Considering the above, personally I hardly see how load test can be combined with the UI test if both tests are not recorded simultaneously. But do we really need such 'doubled' functionality?
This is my understanding that may be not completely correct, but I see the reason in essentially different functionality. Regular UI test functions in the terms of UI elements and (user) actions over them. User does not care what is going on from the system point of view when, for example, the combo-box item is selected. The only thing the user is interested in is how applicaton reacts on the selected combo-box item change from the business/functional point of view.
On the contrary, HTTP load testing does not care what is going on with the tested application from the functional point of view. Even more, HTTP load testing does not care if it is the same application or not that sends requests to the server. The only thing HTTP load testing cares of is what was requested from the server and in what order the requests were send. And as long as the content of the requests and their order remains unchanged, HTTP load test would not require changes if, for example, developers change the tested (AJAX) application so that it requests data not on the selected combo-box item change, but on the button click. It is evident, that the mention application change requires adoption of the regular UI test.
Considering the above, personally I hardly see how load test can be combined with the UI test if both tests are not recorded simultaneously. But do we really need such 'doubled' functionality?