Simone_Eidel
New Contributor
Joined 10 years ago
User Profile
User Widgets
Contributions
Image touch not in target or recognition area
I have a mobile application to test which was developed with qml and v-play. Because the v-play wrappes the qml, my object browser tree wouldn't go very deep. I can't see the objects, only some overlays or so. So I'm trying to test the application with the image based approach. But I have the problem, that my image touch isn't where I defined the area. Because I can't see any objects, if I just click the area I want my touch to be, the initial target area is the size of the whole display. When I then set the recognition area, my touch is never in this region. Then I tried to give some coordinates, starting with 10-10 to see, where the touch will be. But then I got an error message, that my touch point (with negative coordinates) is out of the devices screen bound. I wondered how that can be, as my target area is the screen itself and the documentation says, the 10-10 is measured from the upper left corner. Then I tried to set the initial target area around the point where my touch should be. Because I was sure, even if the touch wouldn't be in the recognition area, at least it wouldn't leave the target area. But at this point I was wrong. Again the touch was on the same spot as at my first try. Trying again with coordinates, I got again the error with the touch point out of screen bounds. Now I tried to put the target area around some text, because the image search function would surely find that. And I had the recognition area outside the target area. Again my touch was at the same spot as before, but not in the target nor the recognition area. I coundn't find any reason for that in the documentation. When I now highlighted my area on the screen, the highlighted area was where the touch is, but not where my regions were defined. So what can I do, that I get my touch were I want it and not somewhere else?Why fails the testrunner when a error occured before?
My tests are a mix of running a SoapUI testcase with Testcomplete and then checking the database entries with a script. Now, as soon, as one of my scripts sends an error, after each further SoapUI testcase call, the testrunner reports "The test has failed. See Additional Information for details.", even if there was no error in the SoapUI testcase at all. And at the end, if just one error occurs, I have in the log a number of errors reported, where one is a real one and the others are just the number of runs of SoapUI testcases which followed after one real error occured. Here is a part of the additional info of the testrunner, which thinks he failed: SoapUI 5.1.3 TestCaseRunner Summary ----------------------------- Time Taken: 1161ms Total TestSuites: 0 Total TestCases: 1 (0 failed) Total TestSteps: 3 Total Request Assertions: 4 Total Failed Assertions: 0 Total Exported Results: 3 That mixes my reports really up and makes it hard to find the real errors.
