Forum Discussion

Thomas83's avatar
Thomas83
New Contributor
4 years ago

Mobile testing and capturing traffic

Dear all,   I need help 😉 At the time of this message, I test a mobile app manually and with Fiddler I inspect resquest/response from my app. Sometimes I have to change de body of the request/resp...
Android
iOS
  • vinniew's avatar
    vinniew
    4 years ago

    Hi Thomas, 

     

    Yes its clear. 

     

    My understanding from the OP was that you were manually doing this by picking up a device using fiddler to provide you with the response information, then comparing it manually to your baseline/reference. 

     

    Essentially you are manually ensuring the response information and validating it against that baseline

     

    If the end goal is to test the service request would it not make sense to focus on this and test the api service using a dedicated tool like Soap UI/Ready API. 

     

    The key element here is that were reducing the manual process you are currently using, In RAPI we can parametrize API tests, Data Drive API tests and validate responses. We can also build up tests quite easily and look at automation in our API tests

     

    You can still test the UI component of your APP in TC and automate functional UI tests in TC. 

     

    And then if you want you could run those API tests in a tool like TC were it makes sense in your TC flow. 

     

    See https://support.smartbear.com/testcomplete/docs/working-with/integration/ready-api/index.html

Thomas83's avatar
Thomas83
New Contributor

Dear Vinniew,
This morning I realize that "test service request and validate the response based on a baseline/reference" in your message is not the only thing I need ^^'

 

I would like to launch my mobile app automatically on the device with Testcomplete and, in parallel, capture the mobile traffic with proxy. During all the automatic tasks with TestComplete on the device, the proxy (like fiddler or mitmproxy), could change some parameters and testcomplete will wait until "something" happened (good or bad ^^)

 

Exemple : 

0. Prepare response body or baseline/reference before the test begin.

1. Testcomplete lauch the app

1.1 With the opening of the app, proxy capture the mobile traffic and compare with a reference all the request/response which the device emit. If it's ok the test continue. In some case, I need to modify some parameters from the response to see how the app react (before the launching or during the app is active).

2. Automatics steps on the device with Testcomplete 

2.1 The proxy capture and analyze traffic and if it's not coherent, stop the test.

 

Hope all is clear 

(english is not ma mother tongue)

 

Thanks for your help

Thomas

vinniew's avatar
vinniew
Staff
4 years ago

Hi Thomas, 

 

Yes its clear. 

 

My understanding from the OP was that you were manually doing this by picking up a device using fiddler to provide you with the response information, then comparing it manually to your baseline/reference. 

 

Essentially you are manually ensuring the response information and validating it against that baseline

 

If the end goal is to test the service request would it not make sense to focus on this and test the api service using a dedicated tool like Soap UI/Ready API. 

 

The key element here is that were reducing the manual process you are currently using, In RAPI we can parametrize API tests, Data Drive API tests and validate responses. We can also build up tests quite easily and look at automation in our API tests

 

You can still test the UI component of your APP in TC and automate functional UI tests in TC. 

 

And then if you want you could run those API tests in a tool like TC were it makes sense in your TC flow. 

 

See https://support.smartbear.com/testcomplete/docs/working-with/integration/ready-api/index.html