{"_id":"mtest","_rev":"62-c0474579648153394141f0d7e7b1e72b","name":"mtest","description":"Multibrowser test environment","dist-tags":{"latest":"0.0.5"},"versions":{"0.0.1":{"name":"mtest","version":"0.0.1","author":{"name":"DigitalNatives"},"description":"Multibrowser test environment","preferGlobal":"true","bin":{"mtest-server":"./bin/server","mtest-runner":"./bin/runner"},"dependencies":{"request":"*"},"_id":"mtest@0.0.1","readme":"ERROR: No README.md file found!","dist":{"shasum":"2148328af6a0d3d71aa4b7fdce472e9ab1547adf","tarball":"https://registry.npmjs.org/mtest/-/mtest-0.0.1.tgz","integrity":"sha512-qOZA+YGEIsghDYI1ONHLdAvuHWRf89Sb4RVgFLZqAdKctkEavHpL2GyBdd7W09xgy5PlBJPMbpZy6DwKAx6xlw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIEa3M6oCx4hRQPkejx1htzu5MT9fvftmi7oiaw9ThL9pAiEApvOdcSYQGcG4OTNHRxd5p+K+iDzFjCjSdHkbqZI25Ao="}]},"_npmVersion":"1.1.62","_npmUser":{"name":"gdotdesign","email":"guszti5@hotmail.com"},"maintainers":[{"name":"gdotdesign","email":"guszti5@hotmail.com"}],"directories":{}},"0.0.3":{"name":"mtest","version":"0.0.3","author":{"name":"DigitalNatives"},"description":"Multibrowser test environment","preferGlobal":"true","bin":{"mtest-server":"./bin/server","mtest-runner":"./bin/runner"},"dependencies":{"request":"*"},"readme":"MTest\n=====\n\nMultiplatform / Browser testing via node.js servers to communicate over http and open browser sequentially.\n\n### Installation\n\n```npm install mtest -g```\n\nIn some Linux distrubutions sudo maybe neccessery for the **-g** flag.\n\n### Configuration\nMTest uses `mtest.json` for configuration:\n\n```json\n{\n  \"page\": \"http://{{ip/hostname}}:{{port}}\",\n  \"ip\": \"{{ip of the machine runnig the runner}}\",\n  \"port\": 4001,\n  \"cluster\": {\n    \"{{remote ip}}\": [\"{{browser}}\",\"{{browser}}\",...]\n  }\n}\n```\n\n### Executables\nMTest comes with two executables:\n  * `mtest-runner` This is responsible for calling remote machines. This process will exit with 0 for sucess or 1 for failure.\n  * `mtest-server` This is the executable to be run on the servers\n\n### Running Tests\nWhen the page opens in the browser it's expected to run the tests and send the results to (POST) ```http://localhost:400/report```\nwith the following json:\n```json\n{ \"failed\": #, \"passed\": #, \"skipped\": #, \"pending\": #, \"count\": #}\n```\nWhere the # are the counts.\n\nAfter this request the **mtest-server** closes the current and opens the next browser in the queue or sends reports to the runner\nif no browsers are left.\n\nIf there is even one failed step in any of the reports the test is considered failed and the **mtest-runner** will exit with code 1.\n\n## IE setup\nFor IE you will need to add the hostname/ip of the server hosting the test page to your local networks,\nand maybe lower security in order for the XHR request to reach localhost.\n\n## Supported Browsers / Platforms\n  * linux: chrome / firefox\n  * windows: chrome / firefox / ie\n  * mac: chrome / firefox / safari\n\nMore browsers will be added in the future.\n\n_Currenty the values for the app paths are hard wired, there will be configuration for this in the future_\n\n# Example Scenario\nmtest.json:\n```json\n{\n  \"page\": \"http://192.168.0.1:3000\",\n  \"ip\": \"192.168.0.1\",\n  \"port\": 4001,\n  \"cluster\": {\n    \"REMOTE1-ip\": [\"firefox\",\"chrome\",\"safari\"],\n    \"REMOTE2-ip\": [\"firefox\",\"chrome\",\"ie\"]\n  }\n}\n```\n  * Start mtest-server on REMOTE 1\n  * Start mtest-server on REMOTE 2\n  * Start mtest-runner on 192.168.0.1\n  * REMOTE 1 opens firefox with url... sends results to localhost:4000\n  * REMOTE 1 opens chrome with url ... sends results to localhost:4000\n  * REMOTE 1 opens safari with url ... sends results to localhost:4000\n  * REMOTE 1 sends results to 19.168.0.1:4001\n  * REMOTE 2 opens firefox with url ... sends results to localhost:4000\n  * REMOTE 2 opens chrome with url ... sends results to localhost:4000\n  * REMOTE 2 opens ie with url ... sends results to localhost:4000\n  * REMOTE 2 sends results to 19.168.0.1:4001\n  * mtest-runner exits on 192.168.0.1\n","_id":"mtest@0.0.3","dist":{"shasum":"78a5435ae4af9a9a68cbd0055fe9a0df00594eb4","tarball":"https://registry.npmjs.org/mtest/-/mtest-0.0.3.tgz","integrity":"sha512-lBbAmnmqMxYtfPj5XBhVxzhq++qcut/Se476YDF+DOPY+pA/v4DB1FwUda4n92Pn9yKPDw8iQ92xhOCAtjDtbg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDIUJO+wvNJT90PHOzxAE1Bmz82bknWeuJy5Dt8iN1iyQIhAM96taybLNYDp5cGWttBu1KAsyDnP8GI5ijbhaKYFVox"}]},"_npmVersion":"1.1.62","_npmUser":{"name":"gdotdesign","email":"guszti5@hotmail.com"},"maintainers":[{"name":"gdotdesign","email":"guszti5@hotmail.com"}]},"0.0.4":{"name":"mtest","version":"0.0.4","author":{"name":"DigitalNatives"},"description":"Multibrowser test environment","preferGlobal":"true","bin":{"mtest-server":"./bin/server","mtest-runner":"./bin/runner"},"dependencies":{"request":"*"},"readme":"MTest\n=====\n\nMultiplatform / Browser testing via node.js servers to communicate over http and open browser sequentially.\n\n### Installation\n\n```npm install mtest -g```\n\nIn some Linux distrubutions sudo maybe neccessery for the **-g** flag.\n\n### Configuration\nMTest uses `mtest.json` for configuration:\n\n```json\n{\n  \"page\": \"http://{{ip/hostname}}:{{port}}\",\n  \"ip\": \"{{ip of the machine runnig the runner}}\",\n  \"port\": 4001,\n  \"cluster\": {\n    \"{{remote ip}}\": [\"{{browser}}\",\"{{browser}}\",...]\n  }\n}\n```\n\n### Executables\nMTest comes with two executables:\n  * `mtest-runner` This is responsible for calling remote machines. This process will exit with 0 for sucess or 1 for failure.\n  * `mtest-server` This is the executable to be run on the servers\n\n### Running Tests\nWhen the page opens in the browser it's expected to run the tests and send the results to (POST) ```http://localhost:400/report```\nwith the following json:\n```json\n{ \"failed\": #, \"passed\": #, \"skipped\": #, \"pending\": #, \"count\": #}\n```\nWhere the # are the counts.\n\nAfter this request the **mtest-server** closes the current and opens the next browser in the queue or sends reports to the runner\nif no browsers are left.\n\nIf there is even one failed step in any of the reports the test is considered failed and the **mtest-runner** will exit with code 1.\n\n## IE setup\nFor IE you will need to add the hostname/ip of the server hosting the test page to your local networks,\nand maybe lower security in order for the XHR request to reach localhost.\n\n## Supported Browsers / Platforms\n  * linux: chrome / firefox\n  * windows: chrome / firefox / ie\n  * mac: chrome / firefox / safari\n\nMore browsers will be added in the future.\n\n_Currenty the values for the app paths are hard wired, there will be configuration for this in the future_\n\n# Example Scenario\nmtest.json:\n```json\n{\n  \"page\": \"http://192.168.0.1:3000\",\n  \"ip\": \"192.168.0.1\",\n  \"port\": 4001,\n  \"cluster\": {\n    \"REMOTE1-ip\": [\"firefox\",\"chrome\",\"safari\"],\n    \"REMOTE2-ip\": [\"firefox\",\"chrome\",\"ie\"]\n  }\n}\n```\n  * Start mtest-server on REMOTE 1\n  * Start mtest-server on REMOTE 2\n  * Start mtest-runner on 192.168.0.1\n  * REMOTE 1 opens firefox with url... sends results to localhost:4000\n  * REMOTE 1 opens chrome with url ... sends results to localhost:4000\n  * REMOTE 1 opens safari with url ... sends results to localhost:4000\n  * REMOTE 1 sends results to 19.168.0.1:4001\n  * REMOTE 2 opens firefox with url ... sends results to localhost:4000\n  * REMOTE 2 opens chrome with url ... sends results to localhost:4000\n  * REMOTE 2 opens ie with url ... sends results to localhost:4000\n  * REMOTE 2 sends results to 19.168.0.1:4001\n  * mtest-runner exits on 192.168.0.1\n","_id":"mtest@0.0.4","dist":{"shasum":"bdcc94eb64dd01478140284f0f331566e7e1e164","tarball":"https://registry.npmjs.org/mtest/-/mtest-0.0.4.tgz","integrity":"sha512-7+SJYxt/dIKq8V1h9EJNnvgoDAJ3wg+WqxLbyRWmx/BBdutlx66GaKCqrEqp7FFhEs0400guOEZEmlJmr0aRsQ==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQDDd2E5u6bNGrdlGXzX8/d+N6Afx29RL3mjokcgGWBDFgIgfcvPXKu4ohEYnkhCQn+L3kFAeuz2Ko7HbdiSuetUGpI="}]},"_npmVersion":"1.1.62","_npmUser":{"name":"gdotdesign","email":"guszti5@hotmail.com"},"maintainers":[{"name":"gdotdesign","email":"guszti5@hotmail.com"}]},"0.0.5":{"name":"mtest","version":"0.0.5","author":{"name":"DigitalNatives"},"description":"Multibrowser test environment","preferGlobal":"true","bin":{"mtest-server":"./bin/server","mtest-runner":"./bin/runner"},"dependencies":{"request":"*"},"readme":"MTest\n=====\n\nMultiplatform / Browser testing via node.js servers to communicate over http and open browser sequentially.\n\n### Installation\n\n```npm install mtest -g```\n\nIn some Linux distrubutions sudo maybe neccessery for the **-g** flag.\n\n### Configuration\nMTest uses `mtest.json` for configuration:\n\n```json\n{\n  \"page\": \"http://{{ip/hostname}}:{{port}}\",\n  \"ip\": \"{{ip of the machine runnig the runner}}\",\n  \"port\": 4001,\n  \"cluster\": {\n    \"{{remote ip}}\": [\"{{browser}}\",\"{{browser}}\",...]\n  }\n}\n```\n\n### Executables\nMTest comes with two executables:\n  * `mtest-runner` This is responsible for calling remote machines. This process will exit with 0 for sucess or 1 for failure.\n  * `mtest-server` This is the executable to be run on the servers\n\n### Running Tests\nWhen the page opens in the browser it's expected to run the tests and send the results to (POST) ```http://localhost:400/report```\nwith the following json:\n```json\n{ \"failed\": #, \"passed\": #, \"skipped\": #, \"pending\": #, \"count\": #}\n```\nWhere the # are the counts.\n\nAfter this request the **mtest-server** closes the current and opens the next browser in the queue or sends reports to the runner\nif no browsers are left.\n\nIf there is even one failed step in any of the reports the test is considered failed and the **mtest-runner** will exit with code 1.\n\n## IE setup\nFor IE you will need to add the hostname/ip of the server hosting the test page to your local networks,\nand maybe lower security in order for the XHR request to reach localhost.\n\n## Supported Browsers / Platforms\n  * linux: chrome / firefox\n  * windows: chrome / firefox / ie\n  * mac: chrome / firefox / safari\n\nMore browsers will be added in the future.\n\n_Currenty the values for the app paths are hard wired, there will be configuration for this in the future_\n\n# Example Scenario\nmtest.json:\n```json\n{\n  \"page\": \"http://192.168.0.1:3000\",\n  \"ip\": \"192.168.0.1\",\n  \"port\": 4001,\n  \"cluster\": {\n    \"REMOTE1-ip\": [\"firefox\",\"chrome\",\"safari\"],\n    \"REMOTE2-ip\": [\"firefox\",\"chrome\",\"ie\"]\n  }\n}\n```\n  * Start mtest-server on REMOTE 1\n  * Start mtest-server on REMOTE 2\n  * Start mtest-runner on 192.168.0.1\n  * REMOTE 1 opens firefox with url... sends results to localhost:4000\n  * REMOTE 1 opens chrome with url ... sends results to localhost:4000\n  * REMOTE 1 opens safari with url ... sends results to localhost:4000\n  * REMOTE 1 sends results to 19.168.0.1:4001\n  * REMOTE 2 opens firefox with url ... sends results to localhost:4000\n  * REMOTE 2 opens chrome with url ... sends results to localhost:4000\n  * REMOTE 2 opens ie with url ... sends results to localhost:4000\n  * REMOTE 2 sends results to 19.168.0.1:4001\n  * mtest-runner exits on 192.168.0.1\n","_id":"mtest@0.0.5","dist":{"shasum":"54faf096c544dd14b213c4fc6ba2c1fe2514a8bc","tarball":"https://registry.npmjs.org/mtest/-/mtest-0.0.5.tgz","integrity":"sha512-oJ8wd35tZGdm796TdsbOleBf+9engrepaPrdBnmq6lEDOgfPF2h8xaJeP566FBwBQDpcjX/7YIMK90dfMKmhrQ==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCTBeGXtQLV4K83VDFSAYRhAE+24PbpvTrYE+T0yry+KgIhALXnf10WNguQa3nr844vtl6uzlSdiqSvSii4GG42X5Cz"}]},"_npmVersion":"1.1.62","_npmUser":{"name":"gdotdesign","email":"guszti5@hotmail.com"},"maintainers":[{"name":"gdotdesign","email":"guszti5@hotmail.com"}]}},"readme":"ERROR: No README.md file found!","maintainers":[{"name":"gdotdesign","email":"guszti5@hotmail.com"}],"time":{"modified":"2022-06-20T12:38:41.798Z","created":"2012-12-11T08:48:41.367Z","0.0.1":"2012-12-11T08:48:43.779Z","0.0.2":"2012-12-11T09:23:25.213Z","0.0.3":"2013-03-25T09:09:46.126Z","0.0.4":"2013-03-25T09:17:45.924Z","0.0.5":"2013-03-25T09:31:59.595Z"},"author":{"name":"DigitalNatives"}}