Forum Discussion
tristaanogre
9 years agoEsteemed Contributor
Ok... curiosity question... what exactly are you testing? It seems you are spending a lot of time getting TestComplete to interact with GMAIL when you are actually testing some other sort of process that is generating the email. Specifically, it sounds like you are checking to make sure a link is generated with the proper values, etc.
So, there are two pieces to this... the process that generates the link, and the link itself which navigayes to a particular page. It seems the actual generation of the email is ancillary.
I'm assuming there is some predictability to the link generation. So, it seems to me you don't really need to check the email, you simply need to a) check in a database or some other storage to see if an email conraining the appropriate link was generated... an SQL query might solve that and check the link against expected values then b) Simply open a browser using the predicted link value and verify that the page to which you navigated is correct. Seems that mucking around with gmail, an application outside of your scope of control, seems a futile effort as all it will take is for Google to change a bit of code and, therefore, invalidate your tests.
Another suggestion : get with your programmers to create a simple email client for he sole purpose to receive the emails. Set up a local exchang server in your test environment and run your emails through that. This way, you control all the pieces and you no longer have to mess with Google.
So, there are two pieces to this... the process that generates the link, and the link itself which navigayes to a particular page. It seems the actual generation of the email is ancillary.
I'm assuming there is some predictability to the link generation. So, it seems to me you don't really need to check the email, you simply need to a) check in a database or some other storage to see if an email conraining the appropriate link was generated... an SQL query might solve that and check the link against expected values then b) Simply open a browser using the predicted link value and verify that the page to which you navigated is correct. Seems that mucking around with gmail, an application outside of your scope of control, seems a futile effort as all it will take is for Google to change a bit of code and, therefore, invalidate your tests.
Another suggestion : get with your programmers to create a simple email client for he sole purpose to receive the emails. Set up a local exchang server in your test environment and run your emails through that. This way, you control all the pieces and you no longer have to mess with Google.
AlexKaras
9 years agoCommunity Hero
The only $0.02 that I can add to the otherwise absolutely exaustive Robert's reply is that if for some reason you *really need* to check with some external mail server, you may consider some other (free) mail service with much simpler UI. Mailinator.com might be one of the possible alternatives.