Add end-to-end test setup #38

Open
opened 2024-01-15 15:15:09 +01:00 by morten-olsen · 0 comments
morten-olsen commented 2024-01-15 15:15:09 +01:00 (Migrated from github.com)

Create a setup that can do end-to-end testing of an entire flow. The main goal currently will be to enable regression testing as the project progresses, as well as doing TDD-light when fixing bugs.

  • Start an actual server on a random port
  • Interact with it using the actual API
  • Make assertions/snapshots on CLI output
  • Make assertions on the server runtime

Additional

  • Should use a virtual FS(Not feasible due to the use of socket files, so instead it will use temp dirs)
  • Analyse coverage across the project
  • Run an in-memory database (Since introducing a temp dir, it might as well store the database there)

Focus:
Testing the examples provided throughout the documentation to ensure they work

Create a setup that can do end-to-end testing of an entire flow. The main goal currently will be to enable regression testing as the project progresses, as well as doing TDD-light when fixing bugs. * Start an actual server on a random port * Interact with it using the actual API * Make assertions/snapshots on CLI output * Make assertions on the server runtime Additional * ~Should use a virtual FS~(Not feasible due to the use of socket files, so instead it will use temp dirs) * Analyse coverage across the project * ~Run an in-memory database~ (Since introducing a temp dir, it might as well store the database there) Focus: Testing the examples provided throughout the documentation to ensure they work
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
experiments/mini-loader#38
No description provided.