Socket
Socket
Sign inDemoInstall

@linus/testy

Package Overview
Dependencies
118
Maintainers
1
Versions
9
Alerts
File Explorer

Advanced tools

Install Socket

Detect and block malicious and high-risk dependencies

Install

    @linus/testy

No fuss doctests for Node.js - test your @examples


Version published
Weekly downloads
2
decreased by-33.33%
Maintainers
1
Created
Weekly downloads
 

Readme

Source

🧪 Testy

Testy is no fuss doctests for Node.js. Document your code with JSDoc, provide your @example, and run your tests with Mocha.

CI status CodeQL status

Installation

$ npm install @linus/testy

Usage

  1. In your code, document your functions with JSDoc tags, providing @example tags for your examples:
/**
 * A cool function
 * 
 * @param {string} name
 * @returns {string} A greeting
 * @example hello("Mr von Neumann")
 * //=> "Hello, Mr von Neumann!"
 */
 export function hello(name) {
  return `Hello, ${name}!`;
 }

Notes: The function under test must be exported, and it cannot be a default export. Only named exports work. The expected result must be prefixed with the string //=> on the beginning of a new line, after the example code.

  1. To execute the test, add a file which is discovered by Mocha (e.g. in a tests/ directory), and call testy with the path to the file to be tested:
import { testy } from "@linus/testy";

/**
 * A test
 */
describe("Tests", () => testy("hello.js"));
  1. Run mocha and relax. Your code and your examples are tested!
$ npm test

  Tests
    hello.js
      hello
        ✔ hello("Mr von Neumann")
//=> "Hello, Mr von Neumann!"


  1 passing (6ms)

Advanced

Testy can handle Promises (in both examples and expected results), expected Errors (both thrown Errors and rejected Promises), generator functions, and more. Examples are in test/spec. This also acts as the specification and test suite for Testy.

Development

Testy is under active development. Pull requests are welcome:

  1. Fork the repository
  2. Clone the project to your own machine
  3. Commit changes to a new branch of your fork
  4. Push your work (making sure the code is tested!)
  5. Submit a pull request

Authors

Linus Thiel linus@yesbabyyes.se.

Thank you

  • kiwicopple for providing @supabase/doctest-js, giving rise to adequate frustration to think of a new solution.
  • 75lb for the jsdoc-api module, which does all of the heavy lifting.
  • ry as always, for Node.js, Deno and more.

License

ISC License

Copyright 2022 Linus Thiel.

Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.

THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

Keywords

FAQs

Last updated on 20 May 2024

Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc