We are building a new experience for our SmartBear Community.
This site is now read-only. You can still browse and search as usual. Learn More

Forum Discussion

Thomas83's avatar
Thomas83
New Contributor
5 years ago
Solved

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
    5 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

vinniew's avatar
vinniew
Icon for Staff rankStaff
5 years ago

It sounds like you are looking to test the service requests and validate the responses based on your baseline or reference. 

 

ReadyAPI Test is dedicated to testing the service request of your application and you can easily validate responses.

 

You can also further the scope into Performance testing using ReadyAPI performance but if its just functional testing then ReadyAPI Test will suffice.

 

ReadyApi integrates into TestComplete or you could build your API tests and keep them seperate to UI tests in TC. 

 

Check it out

 

https://smartbear.com/product/ready-api/overview/?utm_source=aw&utm_medium=ppcg&utm_term=readyapi&utm_content=485054157796&utm_campaign=9551020241&gclid=Cj0KCQiAhP2BBhDdARIsAJEzXlH7GWjuqry_iOOilcZ8g-ekTHnBQ4xXm4GFKcNIIYrwy0J8EpR2q00aAhkHEALw_wcB&gclsrc=aw.ds

 

 

Thomas83's avatar
Thomas83
New Contributor
5 years ago

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
    Icon for Staff rankStaff
    5 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

  • AlexKaras's avatar
    AlexKaras
    Community Hero
    5 years ago

    Hi Thomas,

     

    I am not an expert with Fiddler, but it seems to me that it is possible to set it up (using Fiddler Script or AutoResponder) to modify request/response data on the fly.

    Another idea is to consider ServiceV -- one more component of ReadyAPI -- which definitely seems to be able to do what you are talking about.

    https://support.smartbear.com/readyapi/docs/virtualization/routing/conditional.html