40 lines
999 B
Markdown
40 lines
999 B
Markdown
# Tests
|
|
|
|
This directory is for smoke tests and validation checks for Atlas infrastructure.
|
|
|
|
## What Belongs Here
|
|
|
|
- Smoke tests for installation phases.
|
|
- Validation checks for mounts, services, network identity, and repository state.
|
|
- Script syntax checks.
|
|
- Non-secret test fixtures.
|
|
|
|
## What Must Not Be Stored Here
|
|
|
|
- Secrets.
|
|
- Real production data.
|
|
- SQL backups.
|
|
- Large generated test output.
|
|
- Package caches.
|
|
- Environment-specific local overrides.
|
|
|
|
## Naming Conventions
|
|
|
|
- Use lower-case hyphenated names.
|
|
- Prefer names that describe the observable behaviour being checked.
|
|
- Group tests by area when useful, for example `tests/smoke/`.
|
|
|
|
## Expected Future Structure
|
|
|
|
Current planned areas include:
|
|
|
|
```text
|
|
tests/smoke/
|
|
```
|
|
|
|
Additional test groups should be added only when they have clear ownership and purpose.
|
|
|
|
## Security Considerations
|
|
|
|
Tests must not expose secrets or mutate production data unless explicitly designed and approved. Prefer read-only validation where practical.
|