fs_usage_sys 0.1.4

A Rust wrapper for macOS fs_usage to monitor file system events with advanced filtering
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

# Testing Guide

## Running Tests

### Basic Tests (No sudo required)
```bash
cargo test
# or
./lint.sh
```

### Tests Requiring Sudo
Some tests require sudo permissions because `fs_usage` must be run as root on macOS:

```bash
# Run all tests including those requiring sudo
sudo cargo test -- --ignored --nocapture

# Run specific test with sudo
sudo cargo test test_captures_write_operations -- --ignored --nocapture
```

### CI Testing
For CI environments where sudo is available without password:

```bash
./scripts/test_with_sudo.sh
```

## Test Categories

1. **Unit Tests** - Test parsing and internal logic (no sudo required)
2. **Integration Tests** - Test monitor lifecycle (some require sudo)
3. **File System Tests** - Test actual file system event capture (require sudo)

## Troubleshooting

If tests fail with "No events were captured":
- Ensure you're running with sudo
- The monitored path must exist and be accessible
- fs_usage might need more time to start up
- Some paths (like temp directories) might not be properly monitored by fs_usage

## GitHub Actions CI

The ignored tests that require sudo can be run in CI by:
1. Using a macOS runner
2. Configuring passwordless sudo
3. Running `./scripts/test_with_sudo.sh`