orchid-orm-benchmarks
wirepig
orchid-orm-benchmarks | wirepig | |
---|---|---|
6 | 6 | |
12 | 48 | |
- | - | |
6.2 | 4.5 | |
6 months ago | 3 months ago | |
TypeScript | JavaScript | |
- | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
orchid-orm-benchmarks
-
How do you create test cases for APIs?
Here are my tests for an example project. The logic is quite straightforward: create db records, make a request, check the response, and if it was a mutating request check how it affected the database.
-
Examples of APIs that follows the best practices and are production ready on Github?
And if you like to see a random example project here is mine, but my point is that a random project won't really help because each project has a unique set of frameworks/libs/practices and it changes almost everything.
-
Announcing a new TypeScript ORM
Or you can clone this examples repo and play with the Blog API code.
-
Is there a good example of a real world NodeJS API project?
I have an example app, and have written documentation based on it, and I'd appreciate it if you could look and give some feedback. Yes, the doc is about ORM, but imagine the ORM is just an implementation detail and instead look at how validations, controllers, repos, and especially tests are done. Source code, and long boring tutorial about it. Really, check the tests here, they are special. It doesn't have "service" because the app is too simple, but I usually have a service layer as a files with exported functions. Error handling is in app.ts.
-
Rate my project made with Express + TS
I keep all routes in a separate file: routes.ts, in case of multiple API versions it could be "routes.v1.ts", "routes.v2.ts" and so on. v1 and v2 can reuse the same controllers.
-
Writing & organizing Node.js API Tests the right way
I wrote some tests for sample app as well, maybe could be interesting for you to check it out: here, criticism is welcome, just as I like to criticize
wirepig
-
How do you create test cases for APIs?
Not sure which API you're referring to, but if you need to mock some other dependency over the network, check out wirepig (I'm the author).
- Wirepig – Mock HTTP and TCP deps with real sockets in Node.js tests
- Show HN: Wirepig – Mock HTTP and TCP deps with real sockets in Node.js tests
-
I made wirepig, a simple way to mock HTTP and TCP dependencies in tests.
Documentation
Repo
What are some alternatives?
projecthunt-api - API for projecthunt a project hunting platform
toxy - Hackable HTTP proxy for resiliency testing and simulated network conditions
swagger-petstore
Hermione - Testplane (ex-hermione) browser test runner based on mocha and wdio
nodejs-integration-tests-best-practices - ✅ Beyond the basics of Node.js testing. Including a super-comprehensive best practices list and an example app (March 2024)
testcontainers-node - Testcontainers is a NodeJS library that supports tests, providing lightweight, throwaway instances of common databases, Selenium web browsers, or anything else that can run in a Docker container.
survey-manager - A survey manager and creator project with node, typescript and react
jasmine - Simple JavaScript testing framework for browsers and node.js
node-rest-starter - A Node.js starter containing common components and services as a reference API.
nightwatch - Integrated end-to-end testing framework written in Node.js and using W3C Webdriver API. Developed at @browserstack
kysely - A type-safe typescript SQL query builder [Moved to: https://github.com/kysely-org/kysely]
tape - tap-producing test harness for node and browsers