Files
Vijay Janapa Reddi b9ee88ca70 docs(readmes): stretch HTML tables to full width
Add `width="100%"` to every HTML content and contributor table across all
project READMEs so they render full-width on GitHub instead of collapsing
to natural content width. Cell-level `width="X%"` percentages were already
in place but only take effect once the table itself has an explicit width.

Also update the contributor-sync scripts so the auto-generated tables stay
consistent on the next bot run:
  - .github/workflows/contributors/generate_main_readme.py
  - .github/workflows/contributors/generate_readme_tables.py

Scope: 27 files, 85 tables. Sub-project READMEs that already use the
"card" pattern (labs/, kits/ content sections with <table width="98%">
wrappers) are intentionally untouched.
2026-04-22 16:01:54 -04:00

2.8 KiB

Capstone Integration Tests - Module 20

Comprehensive integration tests that validate the ENTIRE TinyTorch learning journey.

Overview

The capstone tests verify that all 19 previous modules work together to build production-ready ML systems.

Test Coverage

Priority 1: Complete ML Pipeline

  • test_complete_ml_pipeline_end_to_end: Full data → model → training → evaluation
  • Validates: Modules 01-08 integration

Priority 2: Model Architecture

  • test_mlp_architecture_integration: Multi-layer perceptron
  • test_cnn_architecture_integration: CNN with Conv2d, pooling, flatten
  • test_transformer_architecture_integration: Attention, embeddings, positional encoding

Priority 3: Training Convergence

  • test_xor_convergence: Classic XOR problem
  • test_binary_classification_convergence: Real binary classification

Priority 4: Optimization & Deployment

  • test_quantization_pipeline: INT8 quantization
  • test_pruning_pipeline: Weight pruning
  • test_combined_optimization_deployment: Quantization + pruning together

Priority 5: Gradient Flow & Performance

  • test_deep_network_gradient_flow: Gradients through all layer types
  • test_memory_efficiency: Reasonable memory usage
  • test_training_performance: Training speed meets expectations

Running Tests

# Run all capstone tests
pytest tests/20_capstone/ -v

# Run specific test class
pytest tests/20_capstone/test_capstone_core.py::TestCompleteMLPipeline -v

Test Philosophy

Tests follow production ML workflow patterns:

  1. Data Creation → Representative datasets
  2. Model Building → Real architectures (MLP, CNN, Transformer)
  3. Training → Actual convergence (loss decreases, accuracy improves)
  4. Evaluation → Real metrics
  5. Optimization → Production techniques (quantization, pruning)

Success Criteria

For capstone tests to pass, students must have:

  1. Built all 19 modules correctly
  2. Integrated modules properly
  3. Implemented autograd correctly (gradients flow everywhere)
  4. Created working optimizers
  5. Validated on real tasks (models actually learn)

What This Tests That Unit Tests Don't

Aspect Unit Tests Capstone Tests
ScopeSingle moduleAll 19 modules together
IntegrationModule isolationCross-module integration
Real workflowsSynthetic checksProduction ML pipelines
LearningCorrectness onlyModels must converge
DeploymentNot testedQuantization, pruning tested