abstractest

Abstract testing processor

Hypothesis

Find out if it's possible to declare unit tests in some generic notation, and execute them via any appropriate provider.

Usage

Install:

yarn add -D abstractest @abstractest/jest

Write a test:

// src/test/js/foo.test.js

import { describe, it, expect } from 'abstractest'

describe('foo()', () => {
  it('works as expected', () => {
    expect(foo()).toEqual('bar')
  })
})

Run tests via the required runner:

abstractest --runner=jest src/test/js/**/*.test.js

Contents

Package	Description	Latest
@abstractest/core	abstractest core utils
@abstractest/expect	Assertion library for abstractest
@abstractest/fixture-basic-test	Testing fixtures
@abstractest/infra	abstractest monorepo infra assets
@abstractest/jest	Jest runner for abstractest
@abstractest/native	Native node:test runner for abstractest
@abstractest/types	abstractest types
abstractest	CLI for abstractest

Implementation notes

• Does not provide whole module mocking by design. It's recommended to use some kind of di/ioc for this purpose.
• Enforces ESM usage. Declare explicit file extensions (.cjs, '.mjs', '.mts', etc) to get necessary module context or initialize the legacy CommonJS API in place.

License

MIT