coreutils/tests/test_seq.rs
Joseph Crail 7ef4bb37a8 tests: consolidate into one crate
The main motivation is to move toward running those tests for a specific
target, that is, if a test won't run on Windows, then we shouldn't build
it. This was previously the default behavior and prevented a successful
run on AppVeyor.

I borrowed this pattern from the tests in the Cargo project.
2016-05-22 03:46:54 -04:00

31 lines
812 B
Rust

use common::util::*;
static UTIL_NAME: &'static str = "seq";
#[test]
fn test_count_up() {
let (_, mut ucmd) = testing(UTIL_NAME);
let out = ucmd.args(&["10"]).run().stdout;
assert_eq!(out, "1\n2\n3\n4\n5\n6\n7\n8\n9\n10\n");
}
#[test]
fn test_count_down() {
let (_, mut ucmd) = testing(UTIL_NAME);
let out = ucmd.args(&["--", "5", "-1", "1"]).run().stdout;
assert_eq!(out, "5\n4\n3\n2\n1\n");
}
#[test]
fn test_separator_and_terminator() {
let (_, mut ucmd) = testing(UTIL_NAME);
let out = ucmd.args(&["-s", ",", "-t", "!", "2", "6"]).run().stdout;
assert_eq!(out, "2,3,4,5,6!");
}
#[test]
fn test_equalize_widths() {
let (_, mut ucmd) = testing(UTIL_NAME);
let out = ucmd.args(&["-w", "5", "10"]).run().stdout;
assert_eq!(out, "05\n06\n07\n08\n09\n10\n");
}