icarus 0.5.8

Build MCP (Model Context Protocol) servers that run as Internet Computer canisters
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45

# Icarus SDK Tests

This directory contains the comprehensive test suite for the Icarus SDK.

## Structure

- **unit/** - Unit tests for individual functions and modules
- **integration/** - Integration tests for cross-crate functionality
- **examples/** - Example usage that also serves as documentation and tests

## Running Tests

```bash
# Run all tests
cargo test

# Run only unit tests
cargo test --test unit_*

# Run only integration tests  
cargo test --test integration_*

# Run with coverage (requires cargo-tarpaulin)
cargo tarpaulin --out Html

# Run specific test
cargo test test_name
```

## Writing Tests

### Unit Tests
Unit tests should focus on testing individual functions in isolation. Place them in `tests/unit/` with descriptive names like `test_auth.rs`, `test_storage.rs`.

### Integration Tests
Integration tests should test the interaction between multiple components. Place them in `tests/integration/` with names like `test_tool_lifecycle.rs`.

### Examples
Examples in `tests/examples/` should demonstrate real-world usage patterns and also serve as tests to ensure the examples work.

## Coverage Goals

- Minimum: 70% overall coverage
- Target: 85% for core functionality
- Critical paths: 95% coverage