about summary refs log tree commit diff
path: root/src/test/stdtest/int.rs
AgeCommit message (Collapse)AuthorLines
2012-01-17libcore: Move core tests into libcoreBrian Anderson-99/+0
2011-12-13Copy first batch of material from libstd to libcore.Graydon Hoare-3/+5
2011-11-15Replaced constant functions with actual constants in std and updated testsStefan Plantikow-3/+3
Fixes issue #1165
2011-11-01Ignore should_fail tests on windowsBrian Anderson-0/+4
2011-11-01Add should_fail annotation for unit testsMatt Brubeck-0/+24
This allows test cases to assert that a function is expected to fail. Tests annotated with "should_fail" will succeed only if the function fails.
2011-10-31Correct handling of non-numeric chars in parse_bufMatt Brubeck-0/+22
Without this fix, int::parse_buf and uint::parse_buf return incorrect results for any strings that contain non-numeric characters. Fixes #1102.
2011-10-30Fix int::parse_buf for negative numbers (#1102)Matt Brubeck-1/+16
2011-10-17[Lib] int.rs, uint.rs: added max_value, min_valueDavid Rajchenbach-Teller-0/+7
2011-09-02Reformat. Issue #855Brian Anderson-5/+5
2011-09-01Rename std::istr to std::str. Issue #855Brian Anderson-1/+1
2011-08-27Convert std::int to istrs. Issue #855Brian Anderson-6/+6
2011-08-20ReformatBrian Anderson-1/+1
This changes the indexing syntax from .() to [], the vector syntax from ~[] to [] and the extension syntax from #fmt() to #fmt[]
2011-07-27Reformat for new syntaxMarijn Haverbeke-1/+1
2011-07-24The Big Test Suite OverhaulBrian Anderson-0/+2
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-09Add sha1 and int tests to stdtest. Issue #428Brian Anderson-0/+23