cancel
Showing results for 
Search instead for 
Did you mean: 

different behaviour between readyAPI and testRunner

SOLVED
Highlighted
Frequent Contributor

different behaviour between readyAPI and testRunner

Hello,

I currently encounter a problem using testRunner.

I run a test in ReadyAPI and it works fine.

I run the same test using testRunner without any reporting option (from ReadyAPI application) then it fails.

It indicates that it cannot find my API (code 404), I guess that there is a setting that is not correct but I can't figure out which one.

thanks for any help

 

 

I have another problem :

- I run a testCase with testRunner that uses an API called switchOn with a custom property deviceX

it works

- I run the API switchOn directly, setting the custom property deviceY :

  • Running it from the interface works fine (I switch on deviceY)
  • Running it from the testRunner does not work properly, it switches on deviceX, even if UID=deviceY is set in the properties tab.

Previous data is still set and not overwritten by new data, how can this happen ????

 

 

Alex

1 ACCEPTED SOLUTION

Accepted Solutions
Frequent Contributor

Re: different behaviour between readyAPI and testRunner

Well, it was a problem of git update that desynchronized my executions.

not a ReadyAPI problem

 

sorry for inconvenience

1 REPLY 1
Frequent Contributor

Re: different behaviour between readyAPI and testRunner

Well, it was a problem of git update that desynchronized my executions.

not a ReadyAPI problem

 

sorry for inconvenience

New Here?
Join us and watch the welcome video:
Top Kudoed Authors