You're welcome Doriant

Happy to know this Ritesh

Glad it was helpful Mukesh

You're welcome John

You're welcome

So happy to see this message Md.Mahfuzul. Share your knowledge with all

You're welcome

You're welcome Erick

Наиболее желанный

Hi, glad to know this you can find all here - automationstepbystep.com/ It is an AWS windows EC2 and is paid. You can goto aws.amazon.com sign up and then get an ec2 machine as required

@@RaghavPal I'll check. Thank you.

Hi Manpreet, not yet on Karate, will do

Hi Roshan, there should be no data saved from website, it saves your test

Hi Abhishek, yes it should work with the url. Pls try

Hi Franco, where is the url variables stored. If your collection uses environment variables, To provide an accompanying set of environment variables, export the template from Postman and run them with the -e flag newman run www.getpostman.com/collections/id -e environment.json github.com/postmanlabs/newman/issues/1336

Hi Manpreet, there is a video in this series, You basically will need to get the newman command. Also you can find a complete series on Jenkins here - automationstepbystep.com/

Yes, it should work as setup

Hi Amruta, you can use -d flag and provide location of your csv or json file $ newman run mycollection.json -d data.json Steps to run test cases from command line :- • Open CMD • Now reach to the folder where your JSON are saved • Now hit command as below newman run Test_Collection.postman_collection.json -e Environment.postman_environment.json -g globals.postman_globals.json -d demoData.csv -reporters cli,html In above command -e represents environment variable, -g global variable, -d csv data file name, -reporters cli,html represents output as console and html reports. www.cuelogic.com/blog/postman-tutorial-for-automation

Hi Palak, Pls check if the path for newman is added in your Path environment variable Open Control Panel -> System and Security -> System -> Advanced System Settings -> Environment Variables In "User variables" or "System variables" find variable PATH and add node.js folder path as value. (DO NOT DELETE EXISTING VALUES) Usually it is C:\Program Files\Nodejs;. If variable doesn't exists, create it. Restart your IDE or computer. ----------- stackoverflow.com/questions/51381299/npm-package-error-newman-is-not-recognized-as-an-internal-or-external-command

@@RaghavPal Thanks Raghav. It worked.

@Usman Rafiq yes, i have already installed with that command that was got version "@newman 4.5.5" even though getting same ----not recognized. please help me

Hi Usman, Pls check if the path for newman is added in your Path environment variable Open Control Panel -> System and Security -> System -> Advanced System Settings -> Environment Variables In "User variables" or "System variables" find variable PATH and add node.js folder path as value. (DO NOT DELETE EXISTING VALUES) Usually it is C:\Program Files\Nodejs;. If variable doesn't exists, create it. Restart your IDE or computer. ----------- newman' is not recognized as an internal or external command,

Thanks for the help Usman

Hi Sri Ram, are you behind any proxy or vpn

@@RaghavPal Yes Raghav.

@@RaghavPal Yes I am behind proxy. Is there any settings I can do to run my collection url?

or export enviornment as json and run with -e env.json

Hassan Let's break down the issue and solution step by step: Issue: * You're using Postman for API testing * You're trying to run your collections remotely * When you share a collection and run it remotely, it doesn't use variables declared at the environment level * This causes errors or test failures when those variables are used in the tests Reason: * Environment variables are specific to the local Postman instance and are not automatically shared when running collections remotely. * Remote runs don't have access to the environment variables defined in your local Postman instance. Solution 1: Define environment variables as collection variables * Instead of defining variables at the environment level, define them as collection variables. * This way, the variables will be part of the collection and will be available when running the collection remotely. Solution 2: Export environment as JSON and run with -e env.json * Export your environment variables as a JSON file using Postman's "Export" feature. * When running the collection remotely, use the `-e` flag followed by the path to the exported JSON file (e.g., `env.json`). * This will allow the remote run to use the environment variables defined in the JSON file. Example command: ``` newman run -e env.json ``` Replace `` with the actual ID of your collection, and `env.json` with the path to your exported environment variables JSON file. By using one of these solutions, you should be able to successfully run your collections remotely with the environment variables available -

Binita When running Postman from the command line, you can manage variables using Newman, which is Postman's command-line collection runner. Here's how you can do it: 1. Environment Variables: Export your env in a file. You can pass an environment file using the `-e` or `--environment` flag. For example: ``` newman run collection.json -e environment.json ``` In the `environment.json` file, you can define your variables and their values. 2. Data Variables: If your variables are coming from data files, you can use the `-d` or `--iteration-data` flag to specify a data file. For example: ``` newman run collection.json -d data.json ``` In the `data.json` file, you can define your variables and their values. 3. Global Variables: You can also set global variables using the `-g` or `--globals` flag. 4. Setting Variables in Scripts: Inside your Pre-request and Test scripts in Postman, you can set environment and global variables using the `pm.environment.set` and `pm.globals.set` functions³. For example: ``` pm.environment.set("variable_key", "variable_value"); ``` Remember to replace `collection.json`, `environment.json`, and `data.json` with your actual file paths. Also, replace `variable_key` and `variable_value` with your actual variable names and values. I hope this helps

@@RaghavPal Thank you for the solution Dada. But will this work if I am running the collection URL remotely instead of the running it using newman in command line?

you should have newman and should export the required files on the system where you are running the command

@@RaghavPal thank you so much. :)

Hi Tulasi, sorry for late reply, what is mom here, is it npm. may be you have not installed node js or env variables for node not set on the system

@@RaghavPal yes sir,I didn't install node js

Hi Jaya, have you checked if the variable names are correct and there is no type or spaces, Also try to debug kzfaq.info/get/bejne/pMthhdaKyM3Pg40.html This may also help - stackoverflow.com/questions/54352177/postman-test-failure-false-to-be-truthy

@@RaghavPal Thank you , I will check the same. One more think which i wanted to share, The tutorial is very helpful for a beginner(Like me 😊). Is thr any other deatiled tutorial shared by you in the same topic. If yes, please share with us. Thank you -Jaya

Hi Val, pls give details, what part of the video are you referring.