rust/src/test/stdtest/path.rs


// Testing a few of the path manipuation functions

use std;

import std::fs;
import std::os;

#[test]
fn test() {
  assert(!fs::path_is_absolute("test-path"));

  log "Current working directory: " + os::getcwd();

  log fs::make_absolute("test-path");
  log fs::make_absolute("/usr/bin");
}
Adding a test case for getcwd and related functions. 2011-06-17 13:30:56 -05:00
			`// Testing a few of the path manipuation functions`

			`use std;`

			`import std::fs;`
			`import std::os;`

The Big Test Suite Overhaul This replaces the make-based test runner with a set of Rust-based test runners. I believe that all existing functionality has been preserved. The primary objective is to dogfood the Rust test framework. A few main things happen here: 1) The run-pass/lib-* tests are all moved into src/test/stdtest. This is a standalone test crate intended for all standard library tests. It compiles to build/test/stdtest.stageN. 2) rustc now compiles into yet another build artifact, this one a test runner that runs any tests contained directly in the rustc crate. This allows much more fine-grained unit testing of the compiler. It compiles to build/test/rustctest.stageN. 3) There is a new custom test runner crate at src/test/compiletest that reproduces all the functionality for running the compile-fail, run-fail, run-pass and bench tests while integrating with Rust's test framework. It compiles to build/test/compiletest.stageN. 4) The build rules have been completely changed to use the new test runners, while also being less redundant, following the example of the recent stageN.mk rewrite. It adds two new features to the cfail/rfail/rpass/bench tests: 1) Tests can specify multiple 'error-pattern' directives which must be satisfied in order. 2) Tests can specify a 'compile-flags' directive which will make the test runner provide additional command line arguments to rustc. There are some downsides, the primary being that Rust has to be functioning pretty well just to run _any_ tests, which I imagine will be the source of some frustration when the entire test suite breaks. Will also cause some headaches during porting. Not having individual make rules, each rpass, etc test no longer remembers between runs whether it completed successfully. As a result, it's not possible to incrementally fix multiple tests by just running 'make check', fixing a test, and repeating without re-running all the tests contained in the test runner. Instead you can filter just the tests you want to run by using the TESTNAME environment variable. This also dispenses with the ability to run stage0 tests, but they tended to be broken more often than not anyway. 2011-07-12 21:01:09 -05:00			`#[test]`
			`fn test() {`
Adding a test case for getcwd and related functions. 2011-06-17 13:30:56 -05:00			`assert(!fs::path_is_absolute("test-path"));`

			`log "Current working directory: " + os::getcwd();`

			`log fs::make_absolute("test-path");`
			`log fs::make_absolute("/usr/bin");`
			`}`