I don't know if anyone has run across this issue when there are debugging or running there coded UI automation project. I've read the answers to this very same question asked on stackoverflow and they all seem related to having this conflict when multiple thread running. Now i don't think i have multiple threads running since this is not a multi-thread app.
While doing a lot of reading and checking my code i think i've found the reason. I think when i'm in my current class and i new up a new class that does a few method within that class, i'm assuming that i lose the instance of the current object and i'm assuming that this causes a new thread. The only reason i say this is because from some of the thread i was reading it states that if you new up an instance of another other class that this can cause this same event. Though i'm not all that familiar on why this does this. I also don't know if this is caused because i have two different test methods
Now if this is correct and is caused because i new up a new class inside my current class. How do keep my automation threads in step, and keep my instance in my current class stable and running on the same thread even when i new up a new class within it?.
CarouselOptionLinks myNewCarOpPage = new CarouselOptionLinks();
I dont currently know how to keep the threads or instance running instep when i new up this class inside my current class.
Aucun commentaire:
Enregistrer un commentaire