Introduce release testing #1

New Issue

opiation · 2026-07-22T17:06:34Z

opiation commented

2026-07-22 17:06:34 +00:00

In the spirit of testing things as close as possible to how they are used, let's test the installation and consumption of this package. We need an automated test showing this package actively being installed by various JavaScript package managers and used by various runtimes.

Package managers:

npm
pnpm
yarn
bun
deno

Runtimes:

node
deno
bun
browser?

Some example use cases we should prove work well:

// test-script.js
import {...} from "@heliopolis/js"

npm install && node ./test-script.js
pnpm install && node ./test-script.js
yarn install && node ./test-script.js
bun install && node ./test-script.js
deno install && node ./test-script.js

npm install && deno run ./test-script.js
pnpm install && deno run ./test-script.js
yarn install && deno run ./test-script.js
bun install && deno run ./test-script.js
deno run ./test-script.js

npm install && bun ./test-script.js
pnpm install && bun ./test-script.js
yarn install && bun ./test-script.js
bun install && bun ./test-script.js
deno install && bun ./test-script.js

In the spirit of testing things as close as possible to how they are used, let's test the installation and consumption of this package. We need an automated test showing this package actively being installed by various JavaScript package managers and used by various runtimes. Package managers: - [ ] npm - [ ] pnpm - [ ] yarn - [ ] bun - [ ] deno Runtimes: - [ ] node - [ ] deno - [ ] bun - [ ] browser? Some example use cases we should prove work well: ```js // test-script.js import {...} from "@heliopolis/js" ``` ```shell npm install && node ./test-script.js pnpm install && node ./test-script.js yarn install && node ./test-script.js bun install && node ./test-script.js deno install && node ./test-script.js npm install && deno run ./test-script.js pnpm install && deno run ./test-script.js yarn install && deno run ./test-script.js bun install && deno run ./test-script.js deno run ./test-script.js npm install && bun ./test-script.js pnpm install && bun ./test-script.js yarn install && bun ./test-script.js bun install && bun ./test-script.js deno install && bun ./test-script.js ```

opiation self-assigned this 2026-07-22 17:06:34 +00:00

opiation commented

2026-07-22 17:19:30 +00:00

A good test script needs to be representative of actual package usage. A thorough test script likely imports every available package export from every available module. It would be even more wonderful of we could run the entire test suite this way and in every runtime. That would give maximum confidence in the package outside of building full-fledged apps using the package.

opiation commented

2026-07-22 17:20:52 +00:00

'Twould also be good for the installation and import tests to be identical to those documented in the package README.md.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: heliopolis/js#1