I am going to load test Registration process of my project.
This registration process has a security image in last step of registration. This security images changes every time a user comes to this page. Can any one tell me how I can automate this security image?
That would be difficult, unless you know how many image/s are used for that specific page. If that is known then you could use a 'Rnd' function to search for the given name/s of the image/s and set the condition to boolean value.....
One question though.... why is it important to you to 'automate'the security images if you are performance testing, or is this a security test?
Security image is part of registration process and with out providing it I can't continue in registration process as it is mandatory field.
Will it be apt to get it removed from app for the sake of load testing. If I am right that app should not be modified for the sake of Load testing.
This security image is like what we encounter while registering for yahoo or other mail services.Development team says that they can't predict its value in advance.
I'm not sure you can get around this without knowing ahead of time the value in the image. Since the idea behind those images is that a computer cannot get passed them - they require human interaction.
I would recommend:
1) Work with the devs and have them disable this for your test environment (which could effect load obviously).
2) Or have a test environment set up where you know the values coming in and you setup an external file (csv, whatever) with the known values.
2 is preferable since you can more accurately represent the load.
Have DEV create you a magic string that will be valid on ALL requests in your testing environment. Just make sure that the magic number doesn't get sent to production. We have ours turned on and off in a config file for the application so that we can turn this on and off as we need it.
Solution; which we are going to zero in on here would the one suggested by Larry, that is keeping security image same for all the transactions. Dev team has also agreed for the same as it would not require drastic change in code.