What should I use if I want to test a warning message appears on the screen for an application? I need to perform a number of steps first to get the intended screen. Would it be best to use JMeter to do this and then when I get to the intended screen I can assert that the response contains the warning message? Or should it all be done using Selenium and it would be slower but at least it's going through the actual UI?
Any advice? Or integrate the 2? Use JMeter to perform all the steps to get to the actual screen that I want to test (so that my test runs quicker doing the steps that I'm not actually looking to test) then use Selenium to test that screen and the warning message?
Trying to get my head around the best one to use. I'm liking JMeter and I know it's meant for load testing but if i can use it to run the parts of my test that I'm not actually testing (via http calls) in order to get the part I want to actually test quicker then that makes more sense surely? If the warning message appears in the response in the JMeter http call then why use Selenium at all?