diesel-rs/diesel

Add integration tests for examples

Open

#777 opened on Mar 4, 2017

View on GitHub
 (9 comments) (2 reactions) (0 assignees)Rust (12,054 stars) (1,003 forks)batch import
good first issuehelp wantedtests

Description

We currently have the app from the Getting Started guide implemented for all backends, but there are no tests to ensure they all behave the same.

The app implements several simple binaries to create/display/publish/delete posts. Writings some tests that interact with all the binaries and assert their output is good would be great (it doesn't even have to cover all failure cases).

I wrote the assert_cli crate for a similar use-case. There might be better crates for that now, though. Or actually, it might be possible to do that in a shell script. (Don't know how well that works on Windows, though.)

Contributor guide

Tech stack
rust
Domain
testing
Issue type
test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Rust programmingCLI testing conceptsDiesel ORM basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65
Research direction
Investigate the example apps in the 'examples' directory. Write integration tests using assert cli or a shell script that run the binaries for each backend and verify their output. Ensure tests cover the basic CRUD flow and are runnable via cargo test. Review existing comments for guidance on test structure.