newman support for setNextRequest












0















As part of PostMan collection there's a request which does setNextRequest using the below snippet. This snippet executes fine via PostMan collection runner, however it fails when executed via newman cli it errors out with 'expected false to be truthy at assertion:1 in test-script inside "Get Position"'. Does newman support the setNextRequest api, any other suggestions to achieve the same.



var responseJSON;
var maxTime = new Date(pm.globals.get("$requestMaxTime"));
try {
responseJSON = JSON.parse(responseBody);
if(responseJSON.Code !== pm.globals.get("testCODE")) {
if(maxTime > new Date()) {
postman.setNextRequest("Delay");
}
else {
tests["code is saved"] = responseJSON.Code === pm.globals.get("testCODE");
}
}
else {
tests["code is saved"] = responseJSON.Code === pm.globals.get("testCODE");
}
}
catch (e) { }









share|improve this question























  • What command do you use? Why are you using a mixture of the old and newer syntax?

    – Danny Dainton
    Nov 21 '18 at 7:02













  • Is there a downside to the mix and match, are there some known issues regarding this approach? Newbie query, how can the snippet be changed to newer method. Wrapped newman in a powershell script. param([string]$CollectionPath, [string]$EnvironmentPath, [string]$DataPath) newman run $CollectionPath -e $EnvironmentPath -d $DataPath

    – user457485
    Nov 21 '18 at 7:24













  • Depends how much rework that you would what to do when the older syntax eventually gets removed from the application. pm.test allows you to use pm.expect with the chaijs module, which is better in my opinion. Also, pm.response.json() will parse the body so no need to do what you're doing with it. What file are you using on the CLI for the globals?

    – Danny Dainton
    Nov 21 '18 at 7:48













  • It's a JSON file which has the data variables defined.

    – user457485
    Nov 22 '18 at 1:23











  • I understand that but you're not including in your Newman run script. I wasn't sure if that was the reason it wasn't working.

    – Danny Dainton
    Nov 22 '18 at 7:03
















0















As part of PostMan collection there's a request which does setNextRequest using the below snippet. This snippet executes fine via PostMan collection runner, however it fails when executed via newman cli it errors out with 'expected false to be truthy at assertion:1 in test-script inside "Get Position"'. Does newman support the setNextRequest api, any other suggestions to achieve the same.



var responseJSON;
var maxTime = new Date(pm.globals.get("$requestMaxTime"));
try {
responseJSON = JSON.parse(responseBody);
if(responseJSON.Code !== pm.globals.get("testCODE")) {
if(maxTime > new Date()) {
postman.setNextRequest("Delay");
}
else {
tests["code is saved"] = responseJSON.Code === pm.globals.get("testCODE");
}
}
else {
tests["code is saved"] = responseJSON.Code === pm.globals.get("testCODE");
}
}
catch (e) { }









share|improve this question























  • What command do you use? Why are you using a mixture of the old and newer syntax?

    – Danny Dainton
    Nov 21 '18 at 7:02













  • Is there a downside to the mix and match, are there some known issues regarding this approach? Newbie query, how can the snippet be changed to newer method. Wrapped newman in a powershell script. param([string]$CollectionPath, [string]$EnvironmentPath, [string]$DataPath) newman run $CollectionPath -e $EnvironmentPath -d $DataPath

    – user457485
    Nov 21 '18 at 7:24













  • Depends how much rework that you would what to do when the older syntax eventually gets removed from the application. pm.test allows you to use pm.expect with the chaijs module, which is better in my opinion. Also, pm.response.json() will parse the body so no need to do what you're doing with it. What file are you using on the CLI for the globals?

    – Danny Dainton
    Nov 21 '18 at 7:48













  • It's a JSON file which has the data variables defined.

    – user457485
    Nov 22 '18 at 1:23











  • I understand that but you're not including in your Newman run script. I wasn't sure if that was the reason it wasn't working.

    – Danny Dainton
    Nov 22 '18 at 7:03














0












0








0








As part of PostMan collection there's a request which does setNextRequest using the below snippet. This snippet executes fine via PostMan collection runner, however it fails when executed via newman cli it errors out with 'expected false to be truthy at assertion:1 in test-script inside "Get Position"'. Does newman support the setNextRequest api, any other suggestions to achieve the same.



var responseJSON;
var maxTime = new Date(pm.globals.get("$requestMaxTime"));
try {
responseJSON = JSON.parse(responseBody);
if(responseJSON.Code !== pm.globals.get("testCODE")) {
if(maxTime > new Date()) {
postman.setNextRequest("Delay");
}
else {
tests["code is saved"] = responseJSON.Code === pm.globals.get("testCODE");
}
}
else {
tests["code is saved"] = responseJSON.Code === pm.globals.get("testCODE");
}
}
catch (e) { }









share|improve this question














As part of PostMan collection there's a request which does setNextRequest using the below snippet. This snippet executes fine via PostMan collection runner, however it fails when executed via newman cli it errors out with 'expected false to be truthy at assertion:1 in test-script inside "Get Position"'. Does newman support the setNextRequest api, any other suggestions to achieve the same.



var responseJSON;
var maxTime = new Date(pm.globals.get("$requestMaxTime"));
try {
responseJSON = JSON.parse(responseBody);
if(responseJSON.Code !== pm.globals.get("testCODE")) {
if(maxTime > new Date()) {
postman.setNextRequest("Delay");
}
else {
tests["code is saved"] = responseJSON.Code === pm.globals.get("testCODE");
}
}
else {
tests["code is saved"] = responseJSON.Code === pm.globals.get("testCODE");
}
}
catch (e) { }






postman postman-collection-runner






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 21 '18 at 6:52









user457485user457485

112111




112111













  • What command do you use? Why are you using a mixture of the old and newer syntax?

    – Danny Dainton
    Nov 21 '18 at 7:02













  • Is there a downside to the mix and match, are there some known issues regarding this approach? Newbie query, how can the snippet be changed to newer method. Wrapped newman in a powershell script. param([string]$CollectionPath, [string]$EnvironmentPath, [string]$DataPath) newman run $CollectionPath -e $EnvironmentPath -d $DataPath

    – user457485
    Nov 21 '18 at 7:24













  • Depends how much rework that you would what to do when the older syntax eventually gets removed from the application. pm.test allows you to use pm.expect with the chaijs module, which is better in my opinion. Also, pm.response.json() will parse the body so no need to do what you're doing with it. What file are you using on the CLI for the globals?

    – Danny Dainton
    Nov 21 '18 at 7:48













  • It's a JSON file which has the data variables defined.

    – user457485
    Nov 22 '18 at 1:23











  • I understand that but you're not including in your Newman run script. I wasn't sure if that was the reason it wasn't working.

    – Danny Dainton
    Nov 22 '18 at 7:03



















  • What command do you use? Why are you using a mixture of the old and newer syntax?

    – Danny Dainton
    Nov 21 '18 at 7:02













  • Is there a downside to the mix and match, are there some known issues regarding this approach? Newbie query, how can the snippet be changed to newer method. Wrapped newman in a powershell script. param([string]$CollectionPath, [string]$EnvironmentPath, [string]$DataPath) newman run $CollectionPath -e $EnvironmentPath -d $DataPath

    – user457485
    Nov 21 '18 at 7:24













  • Depends how much rework that you would what to do when the older syntax eventually gets removed from the application. pm.test allows you to use pm.expect with the chaijs module, which is better in my opinion. Also, pm.response.json() will parse the body so no need to do what you're doing with it. What file are you using on the CLI for the globals?

    – Danny Dainton
    Nov 21 '18 at 7:48













  • It's a JSON file which has the data variables defined.

    – user457485
    Nov 22 '18 at 1:23











  • I understand that but you're not including in your Newman run script. I wasn't sure if that was the reason it wasn't working.

    – Danny Dainton
    Nov 22 '18 at 7:03

















What command do you use? Why are you using a mixture of the old and newer syntax?

– Danny Dainton
Nov 21 '18 at 7:02







What command do you use? Why are you using a mixture of the old and newer syntax?

– Danny Dainton
Nov 21 '18 at 7:02















Is there a downside to the mix and match, are there some known issues regarding this approach? Newbie query, how can the snippet be changed to newer method. Wrapped newman in a powershell script. param([string]$CollectionPath, [string]$EnvironmentPath, [string]$DataPath) newman run $CollectionPath -e $EnvironmentPath -d $DataPath

– user457485
Nov 21 '18 at 7:24







Is there a downside to the mix and match, are there some known issues regarding this approach? Newbie query, how can the snippet be changed to newer method. Wrapped newman in a powershell script. param([string]$CollectionPath, [string]$EnvironmentPath, [string]$DataPath) newman run $CollectionPath -e $EnvironmentPath -d $DataPath

– user457485
Nov 21 '18 at 7:24















Depends how much rework that you would what to do when the older syntax eventually gets removed from the application. pm.test allows you to use pm.expect with the chaijs module, which is better in my opinion. Also, pm.response.json() will parse the body so no need to do what you're doing with it. What file are you using on the CLI for the globals?

– Danny Dainton
Nov 21 '18 at 7:48







Depends how much rework that you would what to do when the older syntax eventually gets removed from the application. pm.test allows you to use pm.expect with the chaijs module, which is better in my opinion. Also, pm.response.json() will parse the body so no need to do what you're doing with it. What file are you using on the CLI for the globals?

– Danny Dainton
Nov 21 '18 at 7:48















It's a JSON file which has the data variables defined.

– user457485
Nov 22 '18 at 1:23





It's a JSON file which has the data variables defined.

– user457485
Nov 22 '18 at 1:23













I understand that but you're not including in your Newman run script. I wasn't sure if that was the reason it wasn't working.

– Danny Dainton
Nov 22 '18 at 7:03





I understand that but you're not including in your Newman run script. I wasn't sure if that was the reason it wasn't working.

– Danny Dainton
Nov 22 '18 at 7:03












1 Answer
1






active

oldest

votes


















0














if you write setNextRequest in your postman : it will execute successfully



postman.setNextRequest("");



once you export the test as Collection v2.1 (recommended):



json file will come as : "postman.setNextRequest("");"



add to your newman test



run the test with command : newman run test.js



try that !!






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%2f53406665%2fnewman-support-for-setnextrequest%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














    if you write setNextRequest in your postman : it will execute successfully



    postman.setNextRequest("");



    once you export the test as Collection v2.1 (recommended):



    json file will come as : "postman.setNextRequest("");"



    add to your newman test



    run the test with command : newman run test.js



    try that !!






    share|improve this answer




























      0














      if you write setNextRequest in your postman : it will execute successfully



      postman.setNextRequest("");



      once you export the test as Collection v2.1 (recommended):



      json file will come as : "postman.setNextRequest("");"



      add to your newman test



      run the test with command : newman run test.js



      try that !!






      share|improve this answer


























        0












        0








        0







        if you write setNextRequest in your postman : it will execute successfully



        postman.setNextRequest("");



        once you export the test as Collection v2.1 (recommended):



        json file will come as : "postman.setNextRequest("");"



        add to your newman test



        run the test with command : newman run test.js



        try that !!






        share|improve this answer













        if you write setNextRequest in your postman : it will execute successfully



        postman.setNextRequest("");



        once you export the test as Collection v2.1 (recommended):



        json file will come as : "postman.setNextRequest("");"



        add to your newman test



        run the test with command : newman run test.js



        try that !!







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Jan 18 at 17:44









        ShahinShahin

        113




        113
































            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%2f53406665%2fnewman-support-for-setnextrequest%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

            鏡平學校

            ꓛꓣだゔៀៅຸ໢ທຮ໕໒ ,ໂ'໥໓າ໼ឨឲ៵៭ៈゎゔit''䖳𥁄卿' ☨₤₨こゎもょの;ꜹꟚꞖꞵꟅꞛေၦေɯ,ɨɡ𛃵𛁹ޝ޳ޠ޾,ޤޒޯ޾𫝒𫠁သ𛅤チョ'サノބޘދ𛁐ᶿᶇᶀᶋᶠ㨑㽹⻮ꧬ꧹؍۩وَؠ㇕㇃㇪ ㇦㇋㇋ṜẰᵡᴠ 軌ᵕ搜۳ٰޗޮ޷ސޯ𫖾𫅀ल, ꙭ꙰ꚅꙁꚊꞻꝔ꟠Ꝭㄤﺟޱސꧨꧼ꧴ꧯꧽ꧲ꧯ'⽹⽭⾁⿞⼳⽋២៩ញណើꩯꩤ꩸ꩮᶻᶺᶧᶂ𫳲𫪭𬸄𫵰𬖩𬫣𬊉ၲ𛅬㕦䬺𫝌𫝼,,𫟖𫞽ហៅ஫㆔ాఆఅꙒꚞꙍ,Ꙟ꙱エ ,ポテ,フࢰࢯ𫟠𫞶 𫝤𫟠ﺕﹱﻜﻣ𪵕𪭸𪻆𪾩𫔷ġ,ŧآꞪ꟥,ꞔꝻ♚☹⛵𛀌ꬷꭞȄƁƪƬșƦǙǗdžƝǯǧⱦⱰꓕꓢႋ神 ဴ၀க௭எ௫ឫោ ' េㇷㇴㇼ神ㇸㇲㇽㇴㇼㇻㇸ'ㇸㇿㇸㇹㇰㆣꓚꓤ₡₧ ㄨㄟ㄂ㄖㄎ໗ツڒذ₶।ऩछएोञयूटक़कयँृी,冬'𛅢𛅥ㇱㇵㇶ𥄥𦒽𠣧𠊓𧢖𥞘𩔋цѰㄠſtʯʭɿʆʗʍʩɷɛ,əʏダヵㄐㄘR{gỚṖḺờṠṫảḙḭᴮᵏᴘᵀᵷᵕᴜᴏᵾq﮲ﲿﴽﭙ軌ﰬﶚﶧ﫲Ҝжюїкӈㇴffצּ﬘﭅﬈軌'ffistfflſtffतभफɳɰʊɲʎ𛁱𛁖𛁮𛀉 𛂯𛀞నఋŀŲ 𫟲𫠖𫞺ຆຆ ໹້໕໗ๆทԊꧢꧠ꧰ꓱ⿝⼑ŎḬẃẖỐẅ ,ờỰỈỗﮊDžȩꭏꭎꬻ꭮ꬿꭖꭥꭅ㇭神 ⾈ꓵꓑ⺄㄄ㄪㄙㄅㄇstA۵䞽ॶ𫞑𫝄㇉㇇゜軌𩜛𩳠Jﻺ‚Üမ႕ႌႊၐၸဓၞၞၡ៸wyvtᶎᶪᶹစဎ꣡꣰꣢꣤ٗ؋لㇳㇾㇻㇱ㆐㆔,,㆟Ⱶヤマފ޼ޝަݿݞݠݷݐ',ݘ,ݪݙݵ𬝉𬜁𫝨𫞘くせぉて¼óû×ó£…𛅑הㄙくԗԀ5606神45,神796'𪤻𫞧ꓐ㄁ㄘɥɺꓵꓲ3''7034׉ⱦⱠˆ“𫝋ȍ,ꩲ軌꩷ꩶꩧꩫఞ۔فڱێظペサ神ナᴦᵑ47 9238їﻂ䐊䔉㠸﬎ffiﬣ,לּᴷᴦᵛᵽ,ᴨᵤ ᵸᵥᴗᵈꚏꚉꚟ⻆rtǟƴ𬎎

            Why https connections are so slow when debugging (stepping over) in Java?