You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -88,11 +88,13 @@ Dockerfiles are provided for amd64 & arm64 flavours
88
88
89
89
##### Building images
90
90
91
+
You can build the Docker images with a specific Explore.CLI version by passing the `VERSION` build argument. If the `VERSION` argument is not provided, the default value specified in the Dockerfile will be used.
Assert.Equal("This is a GET request and it is used to \"get\" data from an endpoint. There is no request body for a GET request, but you can use query parameters to help specify the resource you want data on (e.g., in this request, we have `id=1`).\n\nA successful GET response will have a `200 OK` status, and should include some kind of response body - for example, HTML web content or JSON data.",postmanCollection?.Item?[0].Request?.Description?.Content?.ToString());
"description": "# 🚀 Get started here\n\nThis template guides you through CRUD operations (GET, POST, PUT, DELETE), variables, and tests.\n\n## 🔖 **How to use this template**\n\n#### **Step 1: Send requests**\n\nRESTful APIs allow you to perform CRUD operations using the POST, GET, PUT, and DELETE HTTP methods.\n\nThis collection contains each of these [request](https://learning.postman.com/docs/sending-requests/requests/) types. Open each request and click \"Send\" to see what happens.\n\n#### **Step 2: View responses**\n\nObserve the response tab for status code (200 OK), response time, and size.\n\n#### **Step 3: Send new Body data**\n\nUpdate or add new data in \"Body\" in the POST request. Typically, Body data is also used in PUT request.\n\n```\n{\n \"name\": \"Add your name in the body\"\n}\n\n ```\n\n#### **Step 4: Update the variable**\n\nVariables enable you to store and reuse values in Postman. We have created a [variable](https://learning.postman.com/docs/sending-requests/variables/) called `base_url` with the sample request [https://postman-api-learner.glitch.me](https://postman-api-learner.glitch.me). Replace it with your API endpoint to customize this collection.\n\n#### **Step 5: Add tests in the \"Scripts\" tab**\n\nAdding tests to your requests can help you confirm that your API is working as expected. You can write test scripts in JavaScript and view the output in the \"Test Results\" tab.\n\n<img src=\"https://content.pstmn.io/fa30ea0a-373d-4545-a668-e7b283cca343/aW1hZ2UucG5n\" alt=\"\" height=\"1530\" width=\"2162\">\n\n## 💪 Pro tips\n\n- Use folders to group related requests and organize the collection.\n \n- Add more [scripts](https://learning.postman.com/docs/writing-scripts/intro-to-scripts/) to verify if the API works as expected and execute workflows.\n \n\n## 💡Related templates\n\n[API testing basics](https://go.postman.co/redirect/workspace?type=personal&collectionTemplateId=e9a37a28-055b-49cd-8c7e-97494a21eb54&sourceTemplateId=ddb19591-3097-41cf-82af-c84273e56719) \n[API documentation](https://go.postman.co/redirect/workspace?type=personal&collectionTemplateId=e9c28f47-1253-44af-a2f3-20dce4da1f18&sourceTemplateId=ddb19591-3097-41cf-82af-c84273e56719) \n[Authorization methods](https://go.postman.co/redirect/workspace?type=personal&collectionTemplateId=31a9a6ed-4cdf-4ced-984c-d12c9aec1c27&sourceTemplateId=ddb19591-3097-41cf-82af-c84273e56719)",
"description": "This is a GET request and it is used to \"get\" data from an endpoint. There is no request body for a GET request, but you can use query parameters to help specify the resource you want data on (e.g., in this request, we have `id=1`).\n\nA successful GET response will have a `200 OK` status, and should include some kind of response body - for example, HTML web content or JSON data."
45
+
},
46
+
"response": []
47
+
},
48
+
{
49
+
"name": "Post data",
50
+
"event": [
51
+
{
52
+
"listen": "test",
53
+
"script": {
54
+
"exec": [
55
+
"pm.test(\"Successful POST request\", function () {",
"raw": "{\n\t\"name\": \"Add your name in the body\"\n}",
70
+
"options": {
71
+
"raw": {
72
+
"language": "json"
73
+
}
74
+
}
75
+
},
76
+
"url": {
77
+
"raw": "{{base_url}}/info",
78
+
"host": [
79
+
"{{base_url}}"
80
+
],
81
+
"path": [
82
+
"info"
83
+
]
84
+
},
85
+
"description": "This is a POST request, submitting data to an API via the request body. This request submits JSON data, and the data is reflected in the response.\n\nA successful POST request typically returns a `200 OK` or `201 Created` response code."
86
+
},
87
+
"response": []
88
+
},
89
+
{
90
+
"name": "Update data",
91
+
"event": [
92
+
{
93
+
"listen": "test",
94
+
"script": {
95
+
"exec": [
96
+
"pm.test(\"Successful PUT request\", function () {",
"raw": "{\n\t\"name\": \"Add your name in the body\"\n}",
111
+
"options": {
112
+
"raw": {
113
+
"language": "json"
114
+
}
115
+
}
116
+
},
117
+
"url": {
118
+
"raw": "{{base_url}}/info?id=1",
119
+
"host": [
120
+
"{{base_url}}"
121
+
],
122
+
"path": [
123
+
"info"
124
+
],
125
+
"query": [
126
+
{
127
+
"key": "id",
128
+
"value": "1"
129
+
}
130
+
]
131
+
},
132
+
"description": "This is a PUT request and it is used to overwrite an existing piece of data. For instance, after you create an entity with a POST request, you may want to modify that later. You can do that using a PUT request. You typically identify the entity being updated by including an identifier in the URL (eg. `id=1`).\n\nA successful PUT request typically returns a `200 OK`, `201 Created`, or `204 No Content` response code."
133
+
},
134
+
"response": []
135
+
},
136
+
{
137
+
"name": "Delete data",
138
+
"event": [
139
+
{
140
+
"listen": "test",
141
+
"script": {
142
+
"exec": [
143
+
"pm.test(\"Successful DELETE request\", function () {",
"description": "This is a DELETE request, and it is used to delete data that was previously created via a POST request. You typically identify the entity being updated by including an identifier in the URL (eg. `id=1`).\n\nA successful DELETE request typically returns a `200 OK`, `202 Accepted`, or `204 No Content` response code."
0 commit comments