aboutsummaryrefslogtreecommitdiff
path: root/todo.org
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-05-20 14:48:49 -0400
committerCraig Jennings <c@cjennings.net>2026-05-20 14:48:49 -0400
commit173331fe191d32cfc6585968f0b9ccc043a3e94b (patch)
tree7ba34eb6462cf46efb352c1c0dbc7a4daa70ce17 /todo.org
parented212d4bc036fd7243deb530df6c1115c821ed6e (diff)
downloadarchsetup-173331fe191d32cfc6585968f0b9ccc043a3e94b.tar.gz
archsetup-173331fe191d32cfc6585968f0b9ccc043a3e94b.zip
chore: clean dead todo.org doc-links and file three docs to outbox
I removed three dead `file:` links in todo.org. They pointed at docs that were never written: testing-strategy.org, firmware-cleanup.org, and PLAN-browser-themes.org. Each task body already carries that content inline, so the links were dead weight. I also reworded the Testinfra task's lead-in that claimed the testing-strategy doc exists. I filed three resolved reference docs into assets/outbox/: the calendar-sync scrub note, the tmux copy-mode handoff, and the 2026-05-19 lint follow-up report.
Diffstat (limited to 'todo.org')
-rw-r--r--todo.org8
1 files changed, 2 insertions, 6 deletions
diff --git a/todo.org b/todo.org
index b7925ec..5ca32bc 100644
--- a/todo.org
+++ b/todo.org
@@ -323,8 +323,6 @@ If modifications fail or are incorrect, difficult to recover - should backup fil
** TODO [#B] Implement Testinfra test suite for archsetup
Create comprehensive integration tests using Testinfra (Python + pytest) to validate archsetup installations
-See complete documentation: [[file:docs/testing-strategy.org::*Test Automation Framework][Testing Strategy - Test Automation Framework]]
-
Tests should cover:
- Smoke tests: user created, key packages installed, dotfiles present
- Integration tests: services running, configs valid, X11 starts, apps launch
@@ -335,7 +333,7 @@ Location: scripts/testing/tests/ directory
Integration: Run via pytest against test VMs after archsetup completes
Benefits: Expressive Python tests, excellent reporting, can test interactive scenarios
-The testing-strategy.org document includes:
+A design doc (not yet written) should cover:
- Complete example test suite (test_integration.py)
- Tiered testing strategy (smoke/integration/end-to-end)
- How to run tests and integrate with run-test.sh
@@ -391,8 +389,6 @@ Can remove:
Disk space savings: ~600 MB
-See [[file:docs/firmware-cleanup.org][docs/firmware-cleanup.org]] for full analysis and removal commands.
-
After removal, update archsetup script to install only needed firmware packages.
** TODO [#B] Identify and replace packages no longer in repos
@@ -481,7 +477,7 @@ error-prone — changes must be made in both places. Consider:
The goal is a single place to edit each config, not two.
** TODO [#C] Create Chrome theme with dupre colors
-Create a Chrome browser theme using the dupre color palette. Plan saved in [[file:docs/PLAN-browser-themes.org][docs/PLAN-browser-themes.org]].
+Create a Chrome browser theme using the dupre color palette.
** TODO [#C] Monitor and optimize test execution time
Keep test runs performant as installs and post-install tests grow (target < 2 hours)