Contributions
Re: TE does not see libraries and files inside the project
Guys, the problem is that the project STOPPED working. I did not import anything new or changed anything. TE STOPPED seeingmethod definitions imported from another .py file inside the project. That means my statements: 'import requests ' and 'from my_second_file import *' stopped importing anything. TE says 'no module named requests' and 'some_my_method is not defined' (for all methods) The same project works fine on my host machine (also did not change anything here).1.7KViews0likes3CommentsTE does not see libraries and files inside the project
My project structureincludesa .py file with 'test steps' and a .py file with step definitions. I did not make any changes in the project structure, but all my tests fail with errors indicating thatmy 'steps' are not defined. It also says that some libraries are missing, but they are in place. And it worked fine just couple of days ago. The issue appears on virtual machine with Test Execute. The same project works fine on my host machine. It happened before, but I don't remember how it was solved (maybe it just had gone...)... I did an install repair for TE,but it did not help. Any ideas?1.8KViews0likes8CommentsRe: testedapp does not run
Thank you for your reply,tristaanogre I do all the verifications (kinda 'if the process exists') and before the app is expected to run it first tries to close via UI, if not - tries to perform Close(), if not - performs Terminate(). From what I remember the behavior is as follows. When it says - there is 1 instance of the app running, cannot start another instance - it moves forward the test and does not hang. When it actually cannot start the app it says smth like Process not found. I will wait for the test execution to complete andshare the messages I get there.2.4KViews0likes1Commenttestedapp does not run
Sometimes I face the issue with starting my TestedApp.The issue appears on virtual machines, tests are executed by TestExecute via Jenkins. I use TestedApps.myapp.Run() in my OnStartTest event.TestExecute says 'Waiting for myapp' and cannot start it unless I start it manually. After that for several tests it can successfully start the app. Later it can either successfully start the app for all tests or 'hang' again. Since the issue is not stable I can't come up with any ideas on how to fix that. Any suggestions?2.5KViews0likes8CommentsRe: Minimizing 'false' failures
If it's never Visible, I don't really care if it Exists, and if it is Visible, then it has to already Exist. Unfortunately, for me it is not as straightforward as you described. Sometimes (let's say, to quit the app between tests) I need to perform different actions based on what exact screen is visible, so the logic is: if this one is visible, click that button, if another one - click another and so on. I cannot rely on the expected app state based on the last step since the test can fail somewhere in the middle and TE will not be able to quit the app and proceed with tests. I cannot Terminate the app, since I have other processes to quit, which happens with regular quit of my app via UI actions. To implement that first I started with Visible only, but I got error kinda 'You are trying to get a property Visible of an element that does not exist'. I did not want that error, because for me it is not actually an error, I expect that element can be absent on screen. And I am OK with that. I perform specific verification of element visibility if needed. Sothe best working decision I was able to implement to meet all my possible scenarios and avoid unnecessary errors: firstcheck if an element Exists, and only after that (if it Exists) I am checking if an element is visible.1KViews0likes0Comments