Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I figured out a way to perform endpoint tests using Rust.
#[tokio::test]allows running tests in Tokio runtime, making it possible to run a server and perform requests.tests/with some integration tests. They can be run withcargo runalong with unit tests or separately withcargo run --tests, the only prerequisite being that the database must be up (ofc).cargo run --lib, so I changed the Github Actions workflow accordingly.#[serial]macro. This is because the database is a critical resource. This prolongs execution time, but ensures tests' isolation and stability. A single module (in this case tests contained within a single file) can be run withcargo test --test [module_name].