carlowahlstedt / newmanpostman_vsts_task Goto Github PK

Currently, I only get results in the Output section of my VSTS build. It'd be great if I could get the results to appear in the Tests section like they do when I run my unit tests. Any advice on how I can set this up would be much appreciated!

Running this task on a Custom Build Agent, with file paths to newman.cmd, collection.json and environment.json specified. The generated command puts quotes in the wrong place resulting in a failure.

With Misplaced Quotes:
C:\Windows\system32\cmd.exe /D /S /C "C:\npm\newman.cmd run "C:\vstsagent\A1_work\r2\a_App 1.2\drop\bin\Release\test\app.postman_collection.json" -r junit -n 1 -e "C:\vstsagent\A1_work\r2\a_App 1.2\drop\bin\Release\test\app.postman_environment.json""

Should look like:
C:\Windows\system32\cmd.exe /D /S /C C:\npm\newman.cmd run "C:\vstsagent\A1_work\r2\a_App 1.2\drop\bin\Release\test\app.postman_collection.json" -r junit -n 1 -e "C:\vstsagent\A1_work\r2\a_App 1.2\drop\bin\Release\test\app.postman_environment.json"

Is there another way to specify my file paths to handle this situation?

htmlextra added the ability to include postman console.log statements using the --reporter-htmlextra-logs flag. This should be added as an additional flag as it prints a lot of useful information while debugging.

https://www.npmjs.com/package/newman-reporter-htmlextra

When I add a second 'Newman the cli Companion for Postman' to my build - for example by cloning the first one - and click 'Save' (or 'Save & queue') the 'Save' (and 'Save & queue') buttons are not greyed out afterwards, even though my changes have been persisted. Reloading the edit build page causes a "This page is asking you to confirm that you want to leave - data you have entered may not be saved." prompt too, and after reloading the page still thinks there are unsaved changes.

Azure DevOps Version:

• Installation: on premises Microsoft Visual Studio Team Foundation Server Version 15.117.27414.0 (Team Foundation Server 2017 Update 3)
• Task Version: 4

As soon as the azure-pipelines-task-lib library gets updated with the fix for the shelljs security issue, then the task needs fixed.

If global file value is not provided, value is set to 'd:\a\1\s '.
With current implementation arg '-globalfiles' is added with this value and then newman fail since it does not found the file
[command]C:\Windows\system32\cmd.exe /D /S /C "C:\npm\prefix\newman.cmd run --ssl-client-cert d:\a\1\s --ssl-client-key d:\a\1\s --reporter-html-template d:\a\1\s -r "cli,junit" -n 1 **--globals d:\a\1\s** -e d:\a\1\s\PostmanTests

Seems behavior is the same for reporter-html-template, ssl-client-key but handled differently by newman

Newman option is documented as:

--color
Enable or Disable colored CLI output. The color value can be any of the three: on, off or auto(default).
With auto, Newman attempts to automatically turn color on or off based on the color support in the terminal. This behaviour can be modified by using the on or off value accordingly.

But code uses:

    let forceNoColor = tl.getBoolInput('forceNoColor');
    newman.argIf(forceNoColor, ['--no-color']);

Hi Carlo,

I downloaded and configured the NewmanPostman_VSTS_Task, I stored the postman collection.json file in TFS and using it to run in my build pipeline. It works fine from my command line (both locally and via TFS agent), however i'm unable to pass the parameter "-k" for ignoring the SSL from the plugin.

newman run postman_collection.json -k

Can you please advice if there is anyway I can pass the -k option via plugin?

When creating a new Newman task, I am not able to select any report. I am only able to setup a path for the report. This way no report file is generated.

The command that is currently executed:
newman run "mypostman_collection.json" --reporter-junit-export "PATH_TO_REPORT\report.xml" -n 1 --folder "Folder to run" -e "MY.postman_environment.json"

The part "--reporters junit" is missing from this command.

The command that is expected:
newman run "mypostman_collection.json" --reporters junit --reporter-junit-export "PATH_TO_REPORT\report.xml" -n 1 --folder "Folder to run" -e "MY.postman_environment.json"

Is our version of VSTFS too old?

Running on
Microsoft Visual Studio Team Foundation Server
Version 15.117.27414.0

Since #25 (?) , when option -- insecure is set, newman fail with error message

2018-04-03T01:09:56.6819866Z [command]C:\Windows\system32\cmd.exe /D /S /C "C:\npm\prefix\newman.cmd run --insecure -r "cli,html,json,junit" -n 1 --globals D:\a\1\s\PostmanTests\globals.postman_globals.json -e D:\a\1\s\PostmanTests\APITest.postman_environment.json D:\a\1\s\PostmanTests\APITest.postman_collection.json"
2018-04-03T01:09:58.1779293Z ENOENT: no such file or directory, open 'D:\a\1\s\--insecure'
2018-04-03T01:09:58.1779746Z unable to read data from file "--insecure"
2018-04-03T01:09:58.1779873Z { code: 1,
2018-04-03T01:09:58.1779988Z   error: undefined,
2018-04-03T01:09:58.1780142Z   stdout: 'unable to read data from file "--insecure"\n',
2018-04-03T01:09:58.1780303Z   stderr: 'ENOENT: no such file or directory, open \'D:\\a\\1\\s\\--insecure\'\n' }
2018-04-03T01:09:58.1780912Z ##[error]Failed
2018-04-03T01:09:58.1851312Z ##[section]Finishing: Shared

It seems that insecure option can't be set as first parameter, maybe an newman issue, but need to be fixed here as well.

As explained here, verify the extension can handle team shared collections.

It's very handy Task and i was trying to use on on-prine TFS, and set configuration as below

...

and it's showing error as below

EISDIR: illegal operation on a directory, open 'D:\GITDB-Build-1\_work\2\a' error writing file "D:\GITDB-Build-1\_work\2\a" for junit-reporter { code: 1, error: undefined, stdout: 'error writing file "D:\\GITDB-Build-1\\_work\\2\\a" for junit-reporter\n', stderr: 'EISDIR: illegal operation on a directory, open \'D:\\GITDB-Build-1\\_work\\2\\a\'\n' }

NOTE: It's working fine with manual command with newman run "src\CBRE.GITDB.API.Test\PostmanCollections\Transaction.postman_collection.json" -e "src\CBRE.GITDB.API.Test\PostmanCollections\Transaction-DEV.postman_environment.json" -r html,cli,json,junit --reporter-junit-export $(build.artifactstagingdirectory)/op.xml

Is there any specific settings i'm missing?

#happydevelopment

Instead of having a single input for Reporters, change to have a checkbox for each possible input.

• cli
• json
• html
• junit

I've opened up the Azure DevOps project where the builds/releases are for the tasks I've created. It would be great if contributors could setup examples of how to run the task so new comers would have something to look at.

It would be great if you could add another output option of HTML extra (newman-reporter-htmlextra)

https://www.npmjs.com/package/newman-reporter-htmlextra

Scott

I was hoping to be able to specify my collection using a postman provided URL such as: https://www.getpostman.com/collections/secret_hex_guid_here . I tried placing the URL in the "Collection File Source" field, but no luck. Error was: "##[error]Not found collectionFileSource: D:\a\r1\a\https:\www.getpostman.com\collections\cd..." Is what I am trying to do supported?

I encountered this issue, after running the newman got a garbled letter.

and my setting is

thanks, in advance

Whatever Ssloption value is, there is an excption while running the task.
2018-01-26T11:43:45.3311698Z ============================================================================== 2018-01-26T11:43:45.6933045Z found 1 files 2018-01-26T11:43:45.7083798Z ##[error]Not found sslStrict: true

Seems attribute is interpreted as a file and not a bool

Hello, I have just setup the plugin and am struggling with reports. I see the below log line for each of the collections run by the Newman Task.

2018-09-19T18:47:49.6701617Z ##[warning]Invalid results file. Make sure the result format of the file '/datadrive/myagent/_work/r1/a/newman/newman-run-report-2018-09-19-18-47-28-154-0.xml' matches 'JUnit' test results format

Publish Test Results Setup:

Newman Task Setup-:

The only other field I have populated is Reporters, it is set to Junit

Issue summary
I am trying to use self-hosted agent in Azure DevOps to run Postman tests. I am using command prompt to install and run newman.

Configuration under Azure DevOps pipeline

1. Task: Command line
   npm install -g newman

Result: newman installation succeeded.

2. Task: Command line
   newman run

Result: 'newman is not recognized as internal or external...'

Same result even after setting PATH in environment. newman commands works fine on the command prompt by logging into the server where the agent is running as a network service.

The same tasks works fine with hosted agent. I suppose setting up the right path is the problem. But I can't make it solved with setting up global PATH or installing in local. Infact, I can't find right command to install postman to the a local folder where network service can detect. Any pointers will be appreciated.

Expected behavior
The newman should get recognized and running

Azure DevOps Version:

• Installation: Azure DevOps Server, using Windows self-hosted agent as agent pool
• Task Version: Command line version 2.0
• Command Log Output:

Additional context
The same tasks are running fine under hosted agents.

Logs
2019-10-31T08:08:14.5279872Z ========================== Starting Command Output ===========================
2019-10-31T08:08:14.5353866Z ##[debug]Entering Invoke-VstsTool.
2019-10-31T08:08:14.5425506Z ##[debug] Arguments: '/D /E:ON /V:OFF /S /C "CALL "C:\AzurePipelinesAgent\vsts-agent-win-x64-2.155.1_work_temp\7e11d754-5864-4f88-b447-48e7967822ef.cmd""'
2019-10-31T08:08:14.5443533Z ##[debug] FileName: 'C:\Windows\system32\cmd.exe'
2019-10-31T08:08:14.5454298Z ##[debug] WorkingDirectory: 'C:\AzurePipelinesAgent\vsts-agent-win-x64-2.155.1_work\r2\a\FunctionalTests\drop'
2019-10-31T08:08:14.5494469Z ##[command]"C:\Windows\system32\cmd.exe" /D /E:ON /V:OFF /S /C "CALL "C:\AzurePipelinesAgent\vsts-agent-win-x64-2.155.1_work_temp\7e11d754-5864-4f88-b447-48e7967822ef.cmd""
2019-10-31T08:08:14.5609419Z 'newman' is not recognized as an internal or external command,
2019-10-31T08:08:14.5615051Z operable program or batch file.
2019-10-31T08:08:14.5626922Z ##[debug]Exit code: 1
2019-10-31T08:08:14.5655515Z ##[debug]Leaving Invoke-VstsTool.
2019-10-31T08:08:14.5907128Z ##[error]Cmd.exe exited with code '1'.

Allow adding additional custom reporter names in addition to the "Reporters" multi-select list.

The VSTS task output currently is very hard to read, using these two options should provide clean output

If I specify let's say report.xml as Reporter JUnit Export parameter, this file should exits; otherwise the task will result in error.

The same invocation by CLI will work instead!

newman run mycollection.json -r junit -n 1 -e myenv.json --reporter-junit-export=report.xml

Workaround: place a task before, with following command, for instance:
true > report.xml

When trying to run Postman tests in Azure DevOps Pipeline, received this error:
[command]/home/vsts/work/node_modules/newman/bin/newman.js run /home/vsts/work/r1/a/_[Build] Accounting/service/Accounting API Testing.postman_collection.json -n 3 -e /home/vsts/work/r1/a

error: EISDIR: illegal operation on a directory, read

##[error]The process '/home/vsts/work/node_modules/newman/bin/newman.js' failed with exit code 1

This code was working fine before just now. I notice your last commit was an hour ago. Could be related...

Hi,
I am using the task in an Azure pipeline and have collection, global and environment json files. Newman npm is being installed correctly.
When the Newman task comes to run it always fails with the following error: "##[error]Could not find any collection files in the path provided"
Note: I have tried different pattern matching to point to the file but nothing works.
I know that the Newman cli is now on v4.5.1 whereas as the task is v3, could this be the issue?

Hi,

When executing the TFS "Newman the cli Companion for Postman" task on a self-hosted agent, I get this error:

[error]Cannot read property 'split' of null.

Task version is: 3.0.7
Newman is installed correctly using the nmp task and it works correctly if I call it via command line task.

The full log text is below:

2018-04-17T11:28:44.1077091Z ##[section]Starting: Newman - Postman
2018-04-17T11:28:44.1077091Z ==============================================================================
2018-04-17T11:28:44.1077091Z Task : Newman the cli Companion for Postman
2018-04-17T11:28:44.1077091Z Description : Using Newman, one can effortlessly run and test a Postman Collections directly from the command-line. Now in a task!
2018-04-17T11:28:44.1077091Z Version : 3.0.7
2018-04-17T11:28:44.1077091Z Author : Carlo Wahlstedt
2018-04-17T11:28:44.1077091Z Help : More Information
2018-04-17T11:28:44.1077091Z ==============================================================================
2018-04-17T11:28:44.7483368Z found 1 files
2018-04-17T11:28:44.7639654Z ##[error]Cannot read property 'split' of null
2018-04-17T11:28:44.7795871Z ##[section]Finishing: Newman - Postman

Cheers,
Guy

Is there an option to suppress exit code 1 in case of test failures. We would like to use publish test results step to publish the failures and the fail the build in this test results.

Current exit code error -
##[error]The process '/usr/local/bin/newman' failed with exit code 1

Thanks,
Srini

The extension doesn't show up in the marketplace search and when I go directly to the extension page is says:
This extension is now unpublished from Marketplace. You can choose to uninstall it.

https://marketplace.visualstudio.com/items?itemName=carlowahlstedt.NewmanPostman&ssr=false#overview

I have the --ignore-redirects flag set in the Newman task. "--ignore-redirects" is being sent in the command

[command]C:\windows\system32\cmd.exe /D /S /C "C:\npm\prefix\newman.cmd run "D:\a\r1\a\Staging Artifacts\automation\postman\collections\RegressionTestsSPI.postman_collection" -r "cli,junit" -n 1 --globals "D:\a\r1\a\Staging Artifacts\automation\postman\globals\globals.postman_globals" --ignore-redirects -e "D:\a\r1\a\Staging Artifacts\automation\postman\environments\staging.postman_environment""

The redirects are still happening in the tests though. The tests work fine in Postman and Newman locally.

I was getting the below error

Command used to genarate reports : newman run MyAutomationAPITesting.postman_collection.json -e Development.postman_environment.json --reporters cli,junit --reporter-junit-export TestResult/result-tests.xml

Below is my publish results task

I can't find a way to provide multiple global vars. My understanding is each key=value must be provided on the command line with the --global-var switch, e.g. --global-var key1=value --global-var key2=value. It appears the task if a space is used is trying to send it all as one command, or if a new line is used, don't include anything but the first line.

If I use the task without the Reporters (e.g. cli or cli,html) it only prompts out the possible command line arguments.

I'm gettingt the error. and can't export the html report file.
I have alos tried run the command npm insatll fs lodash previously
and how can I run this command --reporter-html-export ?

2018-02-17T12:29:37.4028268Z ##[section]Starting: Newman - Postman
2018-02-17T12:29:37.4034128Z ==============================================================================
2018-02-17T12:29:37.4034363Z Task         : Newman the cli Companion for Postman
2018-02-17T12:29:37.4034614Z Description  : Using Newman, one can effortlessly run and test a Postman Collections directly from the command-line. Now in a task!
2018-02-17T12:29:37.4034827Z Version      : 3.0.0
2018-02-17T12:29:37.4034990Z Author       : Carlo Wahlstedt
2018-02-17T12:29:37.4035213Z Help         : [More Information](https://github.com/carlowahlstedt/NewmanPostman_VSTS_Task/blob/master/README.md)
2018-02-17T12:29:37.4035430Z ==============================================================================
2018-02-17T12:29:38.0457685Z [command]C:\Windows\system32\cmd.exe /D /S /C "C:\npm\prefix\newman.cmd run --ssl-client-cert D:\a\1\s --ssl-client-key D:\a\1\s --reporter-html-template D:\a\1\s -r html -n 1 -e D:\a\1\s\environment.postman_environment.json D:\a\1\s\collection.postman_collection.json"
2018-02-17T12:29:45.7205887Z { Error: EISDIR: illegal operation on a directory, read
2018-02-17T12:29:45.7246710Z     at Object.fs.readSync (fs.js:675:18)
2018-02-17T12:29:45.7261430Z     at tryReadSync (fs.js:540:20)
2018-02-17T12:29:45.7325624Z     at Object.fs.readFileSync (fs.js:583:19)
2018-02-17T12:29:45.7330158Z     at new PostmanHTMLReporter (C:\npm\prefix\node_modules\newman\lib\reporters\html\index.js:53:42)
2018-02-17T12:29:45.7345469Z     at C:\npm\prefix\node_modules\newman\lib\run\index.js:319:68
2018-02-17T12:29:45.7372680Z     at arrayEach (C:\npm\prefix\node_modules\newman\node_modules\lodash\lodash.js:537:11)
2018-02-17T12:29:45.7385318Z     at Function.forEach (C:\npm\prefix\node_modules\newman\node_modules\lodash\lodash.js:9344:14)
2018-02-17T12:29:45.7386037Z     at C:\npm\prefix\node_modules\newman\lib\run\index.js:290:39
2018-02-17T12:29:45.7399318Z     at C:\npm\prefix\node_modules\newman\node_modules\postman-runtime\lib\backpack\index.js:56:34
2018-02-17T12:29:45.7411154Z     at C:\npm\prefix\node_modules\newman\node_modules\postman-runtime\lib\runner\index.js:96:20
2018-02-17T12:29:45.7412132Z     at extractRunnableItems (C:\npm\prefix\node_modules\newman\node_modules\postman-runtime\lib\runner\extract-runnable-items.js:135:35)
2018-02-17T12:29:45.7424512Z     at PostmanCollectionRunner.run (C:\npm\prefix\node_modules\newman\node_modules\postman-runtime\lib\runner\index.js:87:9)
2018-02-17T12:29:45.7452089Z     at C:\npm\prefix\node_modules\newman\lib\run\index.js:110:16
2018-02-17T12:29:45.7465570Z     at C:\npm\prefix\node_modules\newman\lib\run\options.js:246:9
2018-02-17T12:29:45.7466536Z     at C:\npm\prefix\node_modules\newman\node_modules\async\dist\async.js:473:16
2018-02-17T12:29:45.7467535Z     at C:\npm\prefix\node_modules\newman\node_modules\async\dist\async.js:3674:9 errno: -4068, code: 'EISDIR', syscall: 'read' }
2018-02-17T12:29:45.7558178Z newman warning: "html" reporter could not be loaded.
2018-02-17T12:30:26.8089948Z ##[error]C:\npm\prefix\newman.cmd failed with return code: 1
2018-02-17T12:30:26.8113958Z ##[section]Finishing: Newman - Postman

Hi,

after a successful run of the task (junit test output is generated) I get the following error message:

2018-03-07T13:40:39.5316103Z ##[section]Starting: Newman - Postman
2018-03-07T13:40:39.5316103Z ==============================================================================
2018-03-07T13:40:39.5316103Z Task : Newman the cli Companion for Postman
2018-03-07T13:40:39.5316103Z Description : Using Newman, one can effortlessly run and test a Postman Collections directly from the command-line. Now in a task!
2018-03-07T13:40:39.5316103Z Version : 3.0.4
2018-03-07T13:40:39.5316103Z Author : Carlo Wahlstedt
2018-03-07T13:40:39.5316103Z Help : More Information
2018-03-07T13:40:39.5316103Z ==============================================================================
2018-03-07T13:40:40.0315995Z found 1 files
2018-03-07T13:40:40.1097247Z [command]C:\Windows\system32\cmd.exe /D /S /C "C:\Users\TFSSERVICE\AppData\Roaming\npm\newman.cmd run --ssl-client-cert E:\TFS-Build\vsts-agent-win7-x64-2.105.6_work\r11\a --ssl-client-key E:\TFS-Build\vsts-agent-win7-x64-2.105.6_work\r11\a -r junit -n 2 -e "E:\TFS-Build\vsts-agent-win7-x64-2.105.6_work\r11\a\CAS Drive REST Service\PostmanFiles\DRI-WIN2016-03.postman_environment.json" "E:\TFS-Build\vsts-agent-win7-x64-2.105.6_work\r11\a\CAS Drive REST Service\PostmanFiles\REST Service.postman_collection.json""
2018-03-07T13:41:17.1098040Z { code: 1, error: undefined, stdout: '', stderr: '' }
2018-03-07T13:41:17.1254323Z ##[error]Failed
2018-03-07T13:41:17.1254323Z ##[section]Finishing: Newman - Postman

Do you have any idea about this topic?
Can I activate more logging?

Thanks for your help.

Due to a limitation of newman the only way to pass variables in during run time in TFS is using global variables.
When we trigger a collection and pass all variables in using tfs, no environment files are used.
It would be nice if the environment file was not mandatory as in this scenario its not required.

Hi all

We try to setup newman in our release pipeline and a bit lost. We have pretty nice and clear messages in the console, but in VSTS output looks like a mess.
First of all, error message is empty. To be honest, we did expect error message same like in the newman cli:

expected response to have status code 200 but got 404
at assertion:0 in test-script
inside "Path \ In\ Collection"

The stack trace also a very useless: it's a single huge and long line of text where everything messed up and a lot of debug info (like internal script names and so on).

Is it our config wrong or a test script wrong or by design?

Hi,

the task works fine before the last update.
The newman task now throws the following error.

2018-03-06T14:13:48.1211972Z ##[section]Starting: Newman - Postman
2018-03-06T14:13:48.1211972Z ==============================================================================
2018-03-06T14:13:48.1211972Z Task : Newman the cli Companion for Postman
2018-03-06T14:13:48.1211972Z Description : Using Newman, one can effortlessly run and test a Postman Collections directly from the command-line. Now in a task!
2018-03-06T14:13:48.1211972Z Version : 3.0.3
2018-03-06T14:13:48.1211972Z Author : Carlo Wahlstedt
2018-03-06T14:13:48.1211972Z Help : More Information
2018-03-06T14:13:48.1211972Z ==============================================================================
2018-03-06T14:13:48.2774578Z module.js:471
2018-03-06T14:13:48.2774578Z throw err;
2018-03-06T14:13:48.2774578Z ^
2018-03-06T14:13:48.2774578Z
2018-03-06T14:13:48.2774578Z Error: Cannot find module 'vsts-task-lib/task'
2018-03-06T14:13:48.2774578Z at Function.Module._resolveFilename (module.js:469:15)
2018-03-06T14:13:48.2774578Z at Function.Module._load (module.js:417:25)
2018-03-06T14:13:48.2774578Z at Module.require (module.js:497:17)
2018-03-06T14:13:48.2774578Z at require (internal/module.js:20:19)
2018-03-06T14:13:48.2774578Z at Object. (E:\TFS-Build\vsts-agent-win7-x64-2.105.6_work_tasks\NewmanPostman_4e74f3b0-c5b7-48cf-970e-8d7071818557\3.0.3\newmantask.js:12:12)
2018-03-06T14:13:48.2774578Z at Module._compile (module.js:570:32)
2018-03-06T14:13:48.2774578Z at Object.Module._extensions..js (module.js:579:10)
2018-03-06T14:13:48.2774578Z at Module.load (module.js:487:32)
2018-03-06T14:13:48.2774578Z at tryModuleLoad (module.js:446:12)
2018-03-06T14:13:48.2774578Z at Function.Module._load (module.js:438:3)
2018-03-06T14:13:48.3399492Z ##[error]Exit code 1 returned from process: file name 'E:\TFS-Build\vsts-agent-win7-x64-2.105.6\externals\node\bin\node.exe', arguments '"E:\TFS-Build\vsts-agent-win7-x64-2.105.6_work_tasks\NewmanPostman_4e74f3b0-c5b7-48cf-970e-8d7071818557\3.0.3\newmantask.js"'.
2018-03-06T14:13:48.3555746Z ##[section]Finishing: Newman - Postman

I tried to install the vsts-task-lib by myself. But it doesn't solve the problem.
Is this library a new requiment with version 3.0.3?

I have the newman task set up:

1. File type
2. pointing to a collection folder on a repo
3. we want to run all collections matching 2 patterns (see screenshot)
4. htmlextra enabled. A directory is specified for the html extra output (Reporter Html Export)

when all of these are configured, then there are not any html extra reports generated and saved at the directory location. This problem is not seen if using URL collection type. The "workaround" for this is to specify an actual html file path in the (Reporter Html Export) field. But since we specified multiple collections that single file will be overwritten by the last collection that you ran.

Some documentation on how to use this as part of the build/release process is essential.

Hi,

I found another small bug in the UI.

It would be great if the task used npx for running newman so that newman doesn't have to be installed on the server running the collection.

See your code:

let sslStrict = tl.getBoolInput('sslStrict');
newman.argIf(sslStrict, ['--insecure']);

The --insecure option is added to the newman command line when sslStrict is set to true. I assume it should be the opposite.

If either of them aren't entered, then it still uses them with an empty path. Need to remove them if the path is empty.

Describe the bug
Not possible to use formdata file on azure environment.

To Reproduce
Steps to reproduce the behavior:

1. Create scenario for sending file
   

2. Check the file does exist on build agent
   

3. Scenario is failed because file parameter doesn't contain data. File is empty.

4. Execute the same scenario on local environment - it works. File is sent correctly.

5. For extra validation - it is possible to adjust the scenario to check if it starts execution:
   
   it this case file is missing and newman cli informs about it.
   

Expected behavior
It was working till today. make it possible to send file via newman cli
When you select file on remote environment - retrieve the file and send it.

Screenshots
If applicable, add screenshots to help explain your problem.

Azure DevOps Version:

• Installation: Azure DevOps
• Task Version: 3+, 4+,
• Command Log Output: [e.g. [command]C:\windows\system32\cmd.exe /D /S /C

Additional context
Started failing from today.

Help those coming to use it but not sure how in VSTS to install before using.

The VSTS Marketplace listing Q&A section has a link to the GitHub repository for the extension. Unfortunately, that link is 404 as it seems the repo was renamed and the link didn't get updated...

Might want to fix that. ;)

https://marketplace.visualstudio.com/items?itemName=carlowahlstedt.NewmanPostman#qna

Hi there,

Are there any plans to include a data binding option to the VSTS task so that csv data can be bound to the newman task similar to:

http://blog.getpostman.com/2014/10/28/using-csv-and-json-files-in-the-postman-collection-runner/

Currently the Newman command to implement data binding is something like:

Newman run {collectionName} -e {environmentName} -d {data.csv}

It would save having to use a PowerShell script for this step.

Thanks,

Liam 👍

Add an additional option onto the HTML report location so you can have the code set the HTML name to the collection being run.

I have started to look at it, but unsure where I could pick up the collection name.

The “Newman the cli Companion for Postman” is a great addon for VSTS Tasks.
I have successfully run the Newman task but I am not able to get the report. It says –
[warning]No test result files matching **/TEST-*.xml were found.
Can you please help me out with this? Whats the value I should put in the Test Result Files
Note: I selected nUnit

This was a question emailed to me:

I was using the NewmanPostman_VSTS_Task on the hosted agents. This was working fine, but now we moved to our own build servers (windows) and getting this exception.

2018-09-18T19:07:00.0786053Z ##[error]Unable to locate executable file: 'newman'. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also verify the file has a valid extension for an executable file.

My current PATH variable looks like this

PATH=C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\ProgramData\chocolatey\bin;C:\Program Files\nodejs;C:\Program Files\dotnet;C:\Program Files\Microsoft SQL Server\130\Tools\Binn;C:\Users\Administrator\AppData\Local\Microsoft\WindowsApps;C:\Users\Administrator\AppData\Roaming\npm;C:\Windows\ServiceProfiles\NetworkService\AppData\Roaming\npm\newman

Was the task designed to run on a custom agent ?

Kind regards,