Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use Cargo to build and run tests and benchmarks #78

Merged
merged 2 commits into from Feb 16, 2015

Commits on Feb 16, 2015

  1. Use Cargo to build and run tests

    html5ever-external-test.rs is now gone. Its custom test runner has moved
    into tokenizer.rs and tree_builder.rs. We're using the #[start]
    attribute to define our own entry point (#[main] isn't respected for
    tests) which generates the test cases and calls through to
    test::test_main.
    
    tests/util.rs now lives in its own test_util crate. It's the only way I
    could figure out to share this functionality between the tokenizer and
    tree builder integration tests.
    
    Makefile.in is now a little simpler because we can just use `cargo test`
    to handle building the tests and examples and and running the tests.
    Top-level make targets like `build`, `check`, and `examples` continue to
    work (though `make examples` also builds the tests now).
    aroben committed Feb 16, 2015
  2. Use Cargo to build and run benchmarks

    This is quite similar to the cargoization of tests in the previous
    commit. html5ever-external-bench is now gone. benches/tokenizer.rs
    includes its own test harness that calls through to test::test_main.
    aroben committed Feb 16, 2015
You can’t perform that action at this time.