PHPackages                             psybizz/http-endpoint-tester - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [HTTP & Networking](/categories/http)
4. /
5. psybizz/http-endpoint-tester

AbandonedArchivedProject[HTTP & Networking](/categories/http)

psybizz/http-endpoint-tester
============================

Test application for http(s) endpoints written in node.js

v1.0.3(10y ago)01.3kMITJavaScript

Since Oct 23Pushed 10y ago1 watchersCompare

[ Source](https://github.com/psybizz/http-endpoint-tester)[ Packagist](https://packagist.org/packages/psybizz/http-endpoint-tester)[ Docs](https://github.com/psybizz/http-endpoint-tester)[ RSS](/packages/psybizz-http-endpoint-tester/feed)WikiDiscussions master Synced 1mo ago

READMEChangelogDependenciesVersions (3)Used By (0)

http-endpoint-tester
====================

[](#http-endpoint-tester)

A HTTP endpoint tester using node.js, inspired by the [node-test-tutorial](https://github.com/DBeath/node-test-tutorial) of David Beath and the talk of Danny Dinneen at the 2014 edition of the Endpoint conference.

The tool is written to be used in a CI pipeline with jenkins, to test endpoints of rest(ful) API's. That's why it depends on environment variables, this makes it easy to use the tool in a CI pipeline.

Usage
-----

[](#usage)

### initialise environment

[](#initialise-environment)

`npm install`

This will install/update all the required modules for running the tests

Also a composer wrapper is provided, implemented to keep our own jenkins as stupid as possible ;)

### Run tests

[](#run-tests)

`ENDPOINT_PATHS= ENDPOINT_HOST=: SITE_URI= ./node_modules/.bin/mocha --ui tdd`

Adding paths to test
--------------------

[](#adding-paths-to-test)

Select the project in resources Open paths.json and add the following stanza:

```
[
    {
            "path": "/api/info",
            "method": "GET",
            "headers": {
                "header1": "value1",
                "header2": "value2"
            },
            "statusCode": [200, 302],
            "public": 1,
            "secure": 0,
            "requireFQDN": 0,
            "timeout": 500
    },
    {
        // another stanza
    }
]
```

path: path to test
method: GET,POST, PUT or PATCH
statuscode: \[statuscode(s)\]
public: should endpoint be available in production
secure: use http or https (needs to be implemented) timeout: timeout in milliseconds
requireFQDN: mark a test as optional or required when an site uri has been specified. ( optional parameter )

public and secure are not implemented yet.

NOTE on site\_uri: this will be set as host header in the request object as demanded by the HTTP1.1 standard, but the request/request implementation will use this value as proxy. So when the tested host is not identical to the site\_uri, you are strongly advised to specify followRedirects to false.

Resources
---------

[](#resources)

- [Request class for node.js](https://github.com/mikeal/request)
- [Mocha test framework](http://http://mochajs.org/)
- [Chai assertion library](https://github.com/chaijs/chai)

Todo
----

[](#todo)

- implement https support

###  Health Score

29

—

LowBetter than 59% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity14

Limited adoption so far

Community7

Small or concentrated contributor base

Maturity64

Established project with proven stability

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~53 days

Total

2

Last Release

3806d ago

Major Versions

v0.1.2 → v1.0.32015-12-16

### Community

Maintainers

![](https://www.gravatar.com/avatar/f7fba15cb3ea9aa944fa93ed0d74feea96b3191a187e7194aa38923413b591b5?d=identicon)[merlijntishauser](/maintainers/merlijntishauser)

---

Top Contributors

[![merlijntishauser](https://avatars.githubusercontent.com/u/5768194?v=4)](https://github.com/merlijntishauser "merlijntishauser (14 commits)")

---

Tags

httptestsnodejs

### Embed Badge

![Health badge](/badges/psybizz-http-endpoint-tester/health.svg)

```
[![Health](https://phpackages.com/badges/psybizz-http-endpoint-tester/health.svg)](https://phpackages.com/packages/psybizz-http-endpoint-tester)
```

###  Alternatives

[guzzlehttp/psr7

PSR-7 message implementation that also provides common utility methods

7.9k1.0B3.2k](/packages/guzzlehttp-psr7)[psr/http-message

Common interface for HTTP messages

7.1k1.0B5.5k](/packages/psr-http-message)[psr/http-factory

PSR-17: Common interfaces for PSR-7 HTTP message factories

1.9k692.9M1.9k](/packages/psr-http-factory)[psr/http-client

Common interface for HTTP clients

1.7k680.7M2.1k](/packages/psr-http-client)[symfony/http-client

Provides powerful methods to fetch HTTP resources synchronously or asynchronously

2.0k314.0M3.4k](/packages/symfony-http-client)[psr/link

Common interfaces for HTTP links

2.5k144.1M68](/packages/psr-link)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)