component_model_types 0.26.0

Component model.
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
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110

# Component Model Types Tests

## Organization Principles

Tests organized by functional domain (smoke tests vs corner case tests) rather than by methodology (unit, integration). Smoke tests verify basic functionality without circular dependencies. Corner case tests explore edge cases and advanced usage patterns.

## Directory Structure

```
tests/
├── readme.md              # This file
├── smoke_test.rs          # Basic functionality verification
├── corner_cases.rs        # Edge cases and boundary conditions
└── manual/                # Manual testing
    ├── readme.md          # Manual testing procedures
    └── -*.md              # Temporary test plans/results
```

### Scope

**Responsibilities:**

Organizes all automated tests for component_model_types trait system functionality. Covers basic trait implementation verification (Assign, AssignWithType, OptionExt), edge case testing (empty values, type conversions, builder patterns), and integration testing with collection_tools dependency. Targets Rust 1.70+ with no_std support.

**In Scope:**

- Core trait functionality (Assign, AssignWithType, OptionExt)
- Builder pattern support (impute method chaining)
- Type conversion testing (Into trait integration)
- Option extension behavior (None → Some, Some → Some transitions)
- Edge cases (empty strings, boundary values, multiple assignments)
- Feature gating verification (enabled, types_component_assign)
- Dependency loading verification (collection_tools)

**Out of Scope:**

- Derive macro generation (covered in component_model crate)
- Performance/benchmarking (types-only crate, minimal performance concerns)
- End-user integration tests (covered in consumer crates: former, component_model)
- Procedural macro tests (no macros in this crate)

## Domain Map

| Domain | Test Location | What It Tests |
|--------|---------------|---------------|
| Basic trait functionality | `smoke_test.rs` | Assign, AssignWithType, OptionExt basic behavior |
| Edge cases | `corner_cases.rs` | Builder patterns, empty values, type conversions |
| Manual verification | `manual/` | Examples execution, feature combinations |
| Dependency loading | `smoke_test.rs::smoke_test_crate_loads` | collection_tools integration |

## Adding New Tests

**Q: Testing new trait method?**
→ Add to `smoke_test.rs` if basic functionality, `corner_cases.rs` if edge case

**Q: Testing new type conversion?**
→ Add to `corner_cases.rs::test_type_conversion_*` family

**Q: Testing new Option behavior?**
→ Add to `smoke_test.rs` (basic) or `corner_cases.rs` (edge case like Some→Some)

**Q: Testing feature flag interaction?**
→ Add feature-gated test to appropriate file (use `#[cfg(feature = "...")]`)

**Q: Testing entirely new trait or module?**
→ 1. Create new test file named after module (e.g., `popular_types_test.rs`)
→ 2. Update this readme.md with new domain entry
→ 3. Add to domain map table above

## Test File Naming Conventions

- **`smoke_test.rs`**: Baseline functionality, always passes or build fails
- **`corner_cases.rs`**: Edge cases, boundary conditions, advanced patterns
- **`[module]_test.rs`**: Module-specific tests (if needed in future)

## Running Tests

```bash
# Run all tests with all features
cargo nextest run --all-features

# Run smoke tests only
cargo nextest run smoke_test --all-features

# Run corner case tests only
cargo nextest run corner_cases --all-features

# Run with no features (tests feature gating)
cargo nextest run --no-default-features

# Run documentation tests
cargo test --doc --all-features

# Run full test suite (level 3)
w3 .test l::3
```

## Manual Testing

See `manual/readme.md` for manual testing procedures and comprehensive example testing.

## Test Organization Standards

All tests follow test_organization.rulebook.md standards:

- **Test Matrix**: Each file documents comprehensive test matrix
- **One Aspect Per Test**: Each test function tests single behavior
- **Environmental Independence**: No reliance on external state
- **Feature Gating**: Tests use appropriate `#[cfg(feature = "...")]` guards
- **Documentation**: Module-level and function-level doc comments required