[{"_1":2,"_155":-5,"_156":-5},"loaderData",{"_3":4,"_13":14,"_21":22,"_134":135},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","routes/_layout",{"_15":-5,"_16":17,"_18":17,"_19":11,"_20":11},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","showHoneypotTrap","routes/_layout.r.$namespace.$reponame",{"_23":24,"_25":-5,"_26":11,"_27":11,"_28":29,"_30":31,"_32":-5,"_33":11,"_34":35,"_84":-5,"_85":86,"_125":-5,"_126":11,"_127":17,"_128":11,"_129":-5,"_130":11,"_131":-5,"_132":133},"canonicalUrl","https://hub.docker.com/r/sebmoule/http-tests/tags","mcpServer","canSeeDockerfile","canSeeAutobuilds","namespace","sebmoule","reponame","http-tests","cloudBuildSource","isAutobuildsAvailable","repo",{"_36":37,"_38":39,"_41":42,"_43":44,"_45":11,"_46":47,"_48":49,"_50":51,"_53":31,"_28":29,"_54":55,"_56":40,"_57":58,"_59":60,"_61":62,"_63":-5,"_64":58,"_65":66,"_67":11,"_68":29,"_69":70,"_75":17,"_76":77,"_81":29,"_82":83},"categories",[],"content_types",[40],"image","date_registered","2016-12-08T14:12:26.345635Z","description","A Simple HTTP Test Scenarios Tool ","is_private","last_updated","2017-03-20T09:00:52.812132Z","last_modified","2024-10-16T13:48:34.145251Z","media_types",[52],"application/vnd.docker.container.image.v1+json","name","pull_count",435,"repository_type","star_count",0,"status",1,"status_description","active","source","collaborator_count","full_description","# Test HTTP Scenarios\n\nThis is a very simple tool developped using shell & perl and allowing you to make HTTP Tests Scenarios.\n\nYou define your tests using a describing format split in 3 parts :\n\n- Test description tags and Target URL\n- The Request HTTP in plain text\n- The elements you want the script to check in the Response.\n\n[![](https://images.microbadger.com/badges/version/sebmoule/http-tests.svg)](http://microbadger.com/images/sebmoule/http-tests \"Get your own version badge on microbadger.com\") [![](https://images.microbadger.com/badges/image/sebmoule/http-tests.svg)](http://microbadger.com/images/sebmoule/http-tests \"Get your own image badge on microbadger.com\")\n\n[![Docker Hub](https://img.shields.io/badge/docker-ready-blue.svg)](https://hub.docker.com/r/sebmoule/http-tests/) [![Docker Pulls](https://img.shields.io/docker/pulls/sebmoule/http-tests.svg?maxAge=2592000)]() [![Docker Stars](https://img.shields.io/docker/stars/sebmoule/http-tests.svg?maxAge=2592000)]()\n\n\n\n## Embedded tests\n\nYou can derive from this Imge to emmbeded your specific app tests in an autonom docker, (useful if you want to launch tests on a swarm cluster)\n\nExemple of Dockerfile :\n\n```\nFROM sebmoule/http-tests\n\nADD test/ /test/conf/TEST/\n```\n\nThis will copy your test directory inside a new image specific.\n\n\n\n## How to write tests\n\nTo ease the usage the test-http tool is embedded in a docker.\n\nBy default, test-http will try to execute ALL tests `xxx.conf` in ALL `conf/*` directories.\n\n\n### Default Scenario\n\ntest-http is shipped with a DEMO tests which is stored inside `/tests/conf/DEMO` and named `test_001_google.conf`, which makes some requests to google\n\n```\n$ docker run --rm sebmoule/http-tests\n...\n...\nYou're executing : /test/tests/test_http.sh -d ALL -t ALL\nworking on test : ALL in directory DEMO from DEMO\n=> DEMO conf/DEMO/test_001_google.conf OK ()\n\tResult Step 1:1 Validation : 200 OK + Token [OK] (0 ms)\n\t\tResult Step 2:1 Validation : 200 OK + Token [OK] (-1 ms)\n\t\t\tResult Step 3:1 Validation : 301 on www.google.fr [OK] (0 ms)\n\t\t\t\tResult Step 4:1 Validation : 200 OK [OK] (0 ms)\nDEMO : Nb test : 4 Nb Check OK: 7 Nb Checks KO : 0\nNumber of request tested 4 Nb Check OK: 7 Nb Checks KO : 0:\n```\n\nThis as Executed the demo test which is composed of 4 Steps, and it output the result.\n\n### View the Details of execution\n\nIn case of Errors in your tests, the Detailed log execution will be print at the end of the test execution.\n\n\nBut You can either mount the result directory locally or inspect the container to see details logs :\n\n```\n$ docker run --rm -v /tmp/results:/test/tests/results sebmoule/http-tests\n\n$ tree /tmp/results/\n/tmp/results/\n|-- Global_result_ALL_DEMO.txt\n`-- result_ALL_DEMO\n `-- DEMO\n\t |-- detailed.log\n\t `-- result.txt\n```\n\nThe Detail Result is the file `/tmp/results/result_ALL_DEMO/DEMO/detailed.log`\n\nIf There was many config file there will be many results\n\n```\n$ docker run -ti --rm \\\n\t-v $PWD/test_002_google.conf:/test/conf/TEST/test_002_google.conf \\\n\t-v /tmp/results:/test/tests/results \\\n\tsebmoule/http-tests\n\n$ tree /tmp/results/\n/tmp/results/\n|-- Global_result_ALL_DEMO.txt\n|-- html\n`-- result_ALL_DEMO\n |-- DEMO\n | |-- detailed.log\n\t | `-- result.txt\n `-- TEST\n |-- detailed.log\n\t `-- result.txt\n```\t\t\t\t\t\t\t\t\n\n\n### Filter which directory to execute\n\nWe can use a Filter to specify which Test directory execute (default is the keyword `ALL`) using the Environnement Variable `DIR` which must specify a directory in `/tests/conf`\n\n\n```\n$ docker run -ti --rm \\\n\t-v $PWD/test_002_google.conf:/test/conf/TEST/test_002_google.conf \\\n\t-v /tmp/results:/test/tests/results \\\n\t-e DIR=TEST \\\n\tsebmoule/http-tests\n\n$ tree /tmp/results/\n/tmp/results/\n|-- Global_result_ALL_TEST.txt\n`-- result_ALL_TEST\n `-- TEST\n |-- detailed.log\n `-- result.txt\n```\t\t\t\t\t\t\t\t\n\n\n### Filter which test to execute\n\nWe can use a Filter to specify which Test to execute within a directory (default is the keyword `ALL`) using the Environnement Variable `TEST` which must specify a valide `*.conf` file in `/tests/conf/$DIR/`\n\n\n```\n$ docker run -ti --rm \\\n\t-v $PWD/test_002_google.conf:/test/conf/DEMO/test_002_google.conf \\\n\t-v /tmp/results:/test/tests/results \\\n\t-e DIR=DEMO \\\n\t-e TEST=002 \\\n\tsebmoule/http-tests\n```\n\nThis will only execute tests in `conf/DEMO/test_002_google.conf`\n\n```\nYou're executing : /test/tests/test_http.sh -d DEMO -t 002 -p DEV\nworking on test : 002 in directory DEMO from DEMO\n=> DEMO conf/DEMO/test_002_google.conf OK ()\n\tResult Step 1:1 Validation : 200 OK + Token [OK] (-1 ms)\n\tResult Step 2:1 Validation : 200 OK + Token [OK] (0 ms)\n\tResult Step 3:1 Validation : 301 on www.google.fr [OK] (0 ms)\n\tResult Step 4:1 Validation : 200 OK [OK] (0 ms)\nDEMO : Nb test : 4 Nb Check OK: 7 Nb Checks KO : 0 . Detailed Test log : results/result_002_DEMO/DEMO/detailed.log\n```\n\n## Using Tag Environment Variable\n\nIn your `*.conf` files you can defines dynamics Tags that will be ovverrided by their equivalent Environment variable.\n\nyou set the Environment Tag on the form `{{MY_ENV_VAR_TAG}}`\n\nex of .conf file usage with Tag Environment:\n```\n##URLTEST=https://{{MY_SERVER}}\n#########################################################\n#SN# Step 1\n#DN# GET Web Service Status\n#ED# 200 OK + ServiceID\nGET / HTTP/1.1\nUser-Agent: curl/7.35.0\nHost: {{MY_SERVER}}\nAccept: */*\n---\nHTTP/1.1 200 OK\n--------------------\n```\n\nIf you have env var `MY_SERVER=www.google.fr` This will produce this request on `https://www.google.fr`\n```\nGET / HTTP/1.1\nUser-Agent: curl/7.35.0\nHost: www.google.fr\nAccept: */*\n```\n\nYou can also uses Tags in the Verification section (lines below the `---`.\n\n\n## Using Tag File (OLD way)\n\nYou can specify Tag file which will contain basic KEY=VALUE items, allowing you to dynamically change your `*.conf` files depending on target.\n\nYou can have a single generic .conf file which can be executed with a DEV Tag file and with a PROD Tag file.\n\nThe default TAG file is `/tests/tags/TAGS_FILE_DEV`. The `DEV` part is the default and you can change it using the `PLATEFORME` environment variable\n\nex of tags:\n```\n$ cat tags/TAGS_FILE_DEV\n=TEST\n=www.google.fr\n```\n\nex of usage in the .conf file :\n\n```\n##URLTEST=https://\nGET / HTTP/1.1\nUser-Agent: curl/7.35.0\nHost: \nAccept: */*\n---\nHTTP/1.1 200 OK\n--------------------\n```\n\nthis will call https://www.google.fr with request :\n\n```\nGET / HTTP/1.1\nUser-Agent: curl/7.35.0\nHost: www.google.fr\nAccept: */*\n```\n\nThe script will be OK if it found `HTTP/1.1 200 OK` in the response.\n\n\n## Advanced Checks of requests\n\nYou can define Rexexp to check in the response and this allow you to capture variables you can reuses in next requests.\nReuse of variables works only in the same scénario (.conf file).\n\n- if the check line starts with `_$_` then we are in Regexp mode\n - in the previous Example we chack that the response contains the value `Location: http://www.google.fr/` because the `` tag is `www.google.fr`\n - If the responses don't Match that line, then the Test will be KO and we will go to next checks\n\t- If the response Match, we will apply the regexp\n - after what we want to match we set 2 pipes `||` and then a list of variables names separated by space.\n - according to the regexp parenthesis, the variables will be populated\n\t - thoses variables will be accessible through special tag `` where X is the step Number where the values are store and varname is the name of the variable store.\n\t\nexample test.conf:\n```\n##URLTEST=http://\nGET / HTTP/1.1\nUser-Agent: curl/7.35.0\nHost: google.fr\nAccept: */*\n---\nHTTP/1.1 301 Moved Permanently\n_$_ Location: (http://())(/) || url host uri\n--------------------\n```\n\nThe output of the script when executing this test will be :\n\n```\nStep 3:1 Validation : If there is no www. there will be a redirect on it (method=\"GET\")-->\nValidation Test : [ OK ] HTTP/1.1 301 Moved Permanently\nValidation Test : [ OK ] Location: (http://(www.google.fr))(/) found (backup data : url (http://www.google.fr))\nValidation Test : [ OK ] Location: (http://(www.google.fr))(/) found (backup data : host (www.google.fr))\nValidation Test : [ OK ] Location: (http://(www.google.fr))(/) found (backup data : uri (/))\n```\nIt says test is OK and specify what var it has created\n\nWe can reuse those var in Nexts steps :\n\n```\n##URLTEST=\nGET HTTP/1.1\nUser-Agent: curl/7.35.0\nHost: \nAccept: */*\n---\nHTTP/1.1 200 OK\n--------------------\n```\n\n- So, when calling in the Next Step, `` it will be the value `http://www.google.fr`\n- So, when calling in the Next Step, `` it will be the value `www.google.fr`\n- So, when calling in the Next Step, `` it will be the value `/`\n\n\n## Debuging\n\nYou can enable the DEBUG logs of the scripts by adding the `DEBUG=1` environment variable\n\n## Alternatives\n\nYou can Use Jmeter, Robot Framework\n\nThis tools may also be useful : https://github.com/lifeforms/httpcheck\n","has_starred","hub_user","immutable_tags_settings",{"_71":11,"_72":73},"enabled","rules",[74],".*","is_automated","permissions",{"_78":17,"_79":11,"_80":11},"read","write","admin","user","storage_size",187445042,"orgData","recentTags",[87],{"_88":40,"_89":90,"_91":92,"_93":94,"_95":96,"_46":114,"_115":90,"_116":29,"_117":52,"_53":118,"_119":120,"_121":105,"_122":114,"_123":62,"_124":17},"content_type","creator",108909,"full_size",27286918,"id",6689192,"images",[97],{"_98":99,"_100":101,"_102":103,"_104":105,"_106":107,"_108":109,"_110":103,"_111":-5,"_112":92,"_59":62,"_113":-5},"architecture","amd64","digest","sha256:b84571efecded0af06ea290aceebaf45fc07f97bd2dd8cc97118758526b31436","features","","last_pulled","2026-09-23T15:51:41.33585719Z","last_pushed","2017-03-20T09:00:53Z","os","linux","os_features","os_version","size","variant","2017-03-20T09:00:52.533761Z","last_updater","last_updater_username","media_type","latest","repository",1100871,"tag_last_pulled","tag_last_pushed","tag_status","v2","sbxKitMetadata","isPotentialSpam","isHubSbxKitsEnabled","showSbxLogoOverride","sbxTrademarkText","displaySecurityMetadata","tagAttestations","tagsHaveAttestations",[],"routes/_layout.r.$namespace.$reponame.tags",{"_34":136,"_143":144,"_132":153,"_154":11},{"_36":137,"_38":138,"_41":42,"_43":44,"_45":11,"_46":47,"_48":49,"_50":139,"_53":31,"_28":29,"_54":55,"_56":40,"_57":58,"_59":60,"_61":62,"_63":-5,"_64":58,"_65":66,"_67":11,"_68":29,"_69":140,"_75":17,"_76":142,"_81":29,"_82":83},[],[40],[52],{"_71":11,"_72":141},[74],{"_78":17,"_79":11,"_80":11},"tags",{"_145":60,"_146":-5,"_147":-5,"_148":149},"count","next","previous","results",[150],{"_88":40,"_89":90,"_91":92,"_93":94,"_95":151,"_46":114,"_115":90,"_116":29,"_117":52,"_53":118,"_119":120,"_121":105,"_122":114,"_123":62,"_124":17},[152],{"_98":99,"_100":101,"_102":103,"_104":105,"_106":107,"_108":109,"_110":103,"_111":-5,"_112":92,"_59":62,"_113":-5},[],"canDeleteTags","actionData","errors"]

sebmoule/http-tests

Tags for sebmoule/http-tests