Testing #51

New issue

Closed

opened 2025-04-27 22:20:33 +00:00 by ElhamAryanpur · 4 comments

ElhamAryanpur commented

2025-04-27 22:20:33 +00:00

(Migrated from github.com)

All of our lua and teal api should be tested. Including servers, and others. The test can be done using the packaged 'lust' test library for logic tests with expected outcomes.

This is only for logic tests on all aspects, not benchmarking or stress testing. If a behavior matches the expected outcome, it is then correct.

All of our lua and teal api should be tested. Including servers, and others. The test can be done using the packaged 'lust' test library for logic tests with expected outcomes. This is only for logic tests on all aspects, not benchmarking or stress testing. If a behavior matches the expected outcome, it is then correct.

ElhamAryanpur commented

2026-02-16 12:51:16 +00:00

(Migrated from github.com)

@Mira5121804 start with this one

Mira5121804 commented

2026-02-16 12:53:12 +00:00

(Migrated from github.com)

okey

0riginaln0 commented

2026-04-11 06:20:14 +00:00

(Migrated from github.com)

It would be great if we had an option to perform end-to-end testing without actually spinning up the server or using real network requests.

To achieve this, we need the ability to:

Construct a Request object,
Call the server with the Request without involving real network operations,
Access the internals of the Response.

From a quick search, here are some resources that can help us implement this:

tower::ServiceExt::{oneshot, ready, ready_oneshot}
The third-party library [axum-test](https://github.com/JosephLenton/axum-test)

But maybe there is a better approach

It would be great if we had an option to perform end-to-end testing without actually spinning up the server or using real network requests. To achieve this, we need the ability to: - Construct a `Request` object, - Call the server with the `Request` without involving real network operations, - Access the internals of the `Response`. From a quick search, here are some resources that can help us implement this: 1. `tower::ServiceExt::{oneshot, ready, ready_oneshot}` 2. The third-party library [[axum-test](https://github.com/JosephLenton/axum-test)](https://github.com/JosephLenton/axum-test) But maybe there is a better approach

ElhamAryanpur commented

2026-04-12 17:26:40 +00:00

(Migrated from github.com)

oh these can work, but using the actual networking stack can help to test it truly in real world environments. in my opinion, much better than dry runs