Is it good to go ahead with webservice load testing?












-2















We have an application which is meant for Android, iOS and desktop all 3 and all 3 are consuming webservices.



What I would like to know is that, should we record scenarios from Android, iOS and desktop seperately and make script or we can just hit the web services using jmeter?










share|improve this question





























    -2















    We have an application which is meant for Android, iOS and desktop all 3 and all 3 are consuming webservices.



    What I would like to know is that, should we record scenarios from Android, iOS and desktop seperately and make script or we can just hit the web services using jmeter?










    share|improve this question



























      -2












      -2








      -2


      1






      We have an application which is meant for Android, iOS and desktop all 3 and all 3 are consuming webservices.



      What I would like to know is that, should we record scenarios from Android, iOS and desktop seperately and make script or we can just hit the web services using jmeter?










      share|improve this question
















      We have an application which is meant for Android, iOS and desktop all 3 and all 3 are consuming webservices.



      What I would like to know is that, should we record scenarios from Android, iOS and desktop seperately and make script or we can just hit the web services using jmeter?







      web-services jmeter






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 19 '18 at 17:45









      Anonymous

      4231038




      4231038










      asked Nov 19 '18 at 6:50









      Anonymous UserAnonymous User

      82




      82
























          1 Answer
          1






          active

          oldest

          votes


















          0














          Well-behaved load test should represent application under test real-life usage as close as possible. If desktop, Android and iOS applications use the same endpoint and send the same requests in terms of parameters - it will be enough to come up with only one Thread Group holding request(s) representing the load.



          If there are differences depending on the platform i.e. in request parameters, headers, cookies, etc. - it's better to go for different Thread Groups representing different users sitting on different platforms or consider using i.e. Throughput Controller to mimic real anticipated distribution of the requests basing on the source platform.






          share|improve this answer























            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53369620%2fis-it-good-to-go-ahead-with-webservice-load-testing%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            Well-behaved load test should represent application under test real-life usage as close as possible. If desktop, Android and iOS applications use the same endpoint and send the same requests in terms of parameters - it will be enough to come up with only one Thread Group holding request(s) representing the load.



            If there are differences depending on the platform i.e. in request parameters, headers, cookies, etc. - it's better to go for different Thread Groups representing different users sitting on different platforms or consider using i.e. Throughput Controller to mimic real anticipated distribution of the requests basing on the source platform.






            share|improve this answer




























              0














              Well-behaved load test should represent application under test real-life usage as close as possible. If desktop, Android and iOS applications use the same endpoint and send the same requests in terms of parameters - it will be enough to come up with only one Thread Group holding request(s) representing the load.



              If there are differences depending on the platform i.e. in request parameters, headers, cookies, etc. - it's better to go for different Thread Groups representing different users sitting on different platforms or consider using i.e. Throughput Controller to mimic real anticipated distribution of the requests basing on the source platform.






              share|improve this answer


























                0












                0








                0







                Well-behaved load test should represent application under test real-life usage as close as possible. If desktop, Android and iOS applications use the same endpoint and send the same requests in terms of parameters - it will be enough to come up with only one Thread Group holding request(s) representing the load.



                If there are differences depending on the platform i.e. in request parameters, headers, cookies, etc. - it's better to go for different Thread Groups representing different users sitting on different platforms or consider using i.e. Throughput Controller to mimic real anticipated distribution of the requests basing on the source platform.






                share|improve this answer













                Well-behaved load test should represent application under test real-life usage as close as possible. If desktop, Android and iOS applications use the same endpoint and send the same requests in terms of parameters - it will be enough to come up with only one Thread Group holding request(s) representing the load.



                If there are differences depending on the platform i.e. in request parameters, headers, cookies, etc. - it's better to go for different Thread Groups representing different users sitting on different platforms or consider using i.e. Throughput Controller to mimic real anticipated distribution of the requests basing on the source platform.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 19 '18 at 14:10









                Dmitri TDmitri T

                70.3k33458




                70.3k33458






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53369620%2fis-it-good-to-go-ahead-with-webservice-load-testing%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    How to pass form data using jquery Ajax to insert data in database?

                    National Museum of Racing and Hall of Fame

                    Guess what letter conforming each word