octo
/
Zebra
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

fix: Make the start acceptance tests stricter

This commit is contained in:
teor 2020-08-20 20:52:15 +10:00
parent 02e6027c57
commit 3400b72699
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
zebrad/tests/acceptance.rs
View File

@ -186,7 +186,9 @@ fn start_no_args() -> Result<()> {
let output = child.wait_with_output()?; let output = child.wait_with_output()?;
let output = output.assert_failure()?; let output = output.assert_failure()?;
output.stdout_contains(r"Starting zebrad")?; // start is the default mode, so we check for end of line, to distinguish it
// from seed
output.stdout_contains(r"Starting zebrad$")?;
// Make sure the command was killed // Make sure the command was killed
assert!(output.was_killed()); assert!(output.was_killed());
@ -270,7 +272,7 @@ fn valid_generated_config_test() -> Result<()> {
// Unlike the other tests, these tests can not be run in parallel, because // Unlike the other tests, these tests can not be run in parallel, because
// they use the generated config. So parallel execution can cause port and // they use the generated config. So parallel execution can cause port and
// cache conflicts. // cache conflicts.
valid_generated_config("start", r"Starting zebrad")?; valid_generated_config("start", r"Starting zebrad$")?;
valid_generated_config("seed", r"Starting zebrad in seed mode")?; valid_generated_config("seed", r"Starting zebrad in seed mode")?;
Ok(()) Ok(())