Testing - Twiggy🌱 (original) (raw)

1. Introduction
2. 1. 📦 Install
3. 2. 💡 Concepts
4. 1. 2.1. Call Graph
   2. 2.2. Paths
   3. 2.3. Dominators and Retained Size
   4. 2.4. Generic Functions and Monomorphization
5. 3. 🏋️‍♀️ Usage
6. 1. 3.1. ⌨ Command Line Interface
   2. 1. 3.1.1. twiggy top
         1. 3.1.2. twiggy paths
         2. 3.1.3. twiggy monos
         3. 3.1.4. twiggy dominators
         4. 3.1.5. twiggy diff
         5. 3.1.6. twiggy garbage
   3. 3.2. 🦀 As a Crate
   4. 3.3. 🕸 On the Web with WebAssembly
7. 4. 🔎 Supported Binary Formats
8. 5. 🙌 Contributing to Twiggy
9. 1. 5.1. Building
   2. 5.2. Testing
   3. 5.3. Code Formatting
   4. 5.4. Pull Requests
   5. 5.5. Team

Twiggy🌱

Testing

$ cargo test --all --exclude twiggy-wasm-api

Authoring New Tests

Integration tests live in the twiggy/tests directory:

twiggy/tests
├── expectations
├── fixtures
└── tests.rs

• The twiggy/tests/tests.rs file contains the #[test] definitions.
• The twiggy/tests/fixtures directory contains input binaries for tests.
• The twiggy/tests/expectations directory contains the expected output of test commands.

Updating Test Expectations

To automatically update all test expectations, you can run the tests with theTWIGGY_UPDATE_TEST_EXPECTATIONS=1 environment variable set. Make sure that you look at the changes before committing them, and that they match your intentions!

TIP: You can use git add -p to examine individual hunks when staging changes before committing!