History

alina sireneva 8e9e759008 build: use pnpm 9.0.6		2024-05-08 20:06:32 +03:00
..
tests	test(e2e): gracefully handle SESSION_PASSWORD_NEEDED (again)	2024-05-03 05:43:51 +03:00
.dockerignore	test: initial e2e publishing testing for deno	2024-04-23 13:44:11 +03:00
.env.example	test: initial e2e publishing testing for deno	2024-04-23 13:44:11 +03:00
.gitignore	test(e2e-deno): ported tests from e2e-node	2024-04-30 05:34:43 +03:00
cli.sh	ci(e2e-deno): hopefully made it a bit less flaky	2024-04-30 05:38:11 +03:00
deno.json	test(e2e-deno): use @mtcute/deno in tests	2024-04-29 22:09:56 +03:00
docker-compose.yaml	test: initial e2e publishing testing for deno	2024-04-23 13:44:11 +03:00
Dockerfile.build	build: use pnpm 9.0.6	2024-05-08 20:06:32 +03:00
Dockerfile.jsr	test: initial e2e publishing testing for deno	2024-04-23 13:44:11 +03:00
Dockerfile.test	build(deno): updated to deno 1.43.1	2024-05-08 20:06:18 +03:00
init-server.js	test: initial e2e publishing testing for deno	2024-04-23 13:44:11 +03:00
nginx.conf	test: initial e2e publishing testing for deno	2024-04-23 13:44:11 +03:00
README.md	test: initial e2e publishing testing for deno	2024-04-23 13:44:11 +03:00
utils.ts	test(e2e-deno): ported tests from e2e-node	2024-04-30 05:34:43 +03:00

README.md

mtcute e2e tests (Deno edition)

This directory contains end-to-end tests for mtcute under Deno.

They are made for 2 purposes:

Ensure published packages work as expected and can properly be imported
Ensure that the library works with the actual Telegram API

To achieve the first goal, we use a local JSR instance container where we publish the package, and then install it from there in another container

Setting up

Before running the tests, you need to copy .env.example to .env and fill in the values

Running tests

# first start a local jsr instance
./cli.sh start

# push all packages to the local registry
./cli.sh update
# pushing a particular package is not supported due to jsr limitations

# run the tests
./cli.sh run
# or in docker
./cli.sh run-docker