studio/marathon
2
0
Fork 0
Code Issues 121 Pull Requests Actions Packages Projects Releases Wiki Activity

Smoke test: Verify rendering still works after vendoring #11

New Issue
Open
opened 2025-12-17 01:41:41 +00:00 by siennathesane · 0 comments
siennathesane commented 2025-12-17 01:41:41 +00:00 (Migrated from github.com)
Copy Link

Comprehensive smoke test to verify existing rendering functionality works after vendoring.

Test Coverage:

  • Desktop (macOS) renders correctly
  • iOS builds and renders
  • PBR materials display properly
  • Lighting works (point, directional, spot)
  • Shadows render
  • No visual regressions

Notes:
This is a GO/NO-GO gate for Phase 2. If tests fail, stop and debug before proceeding.

Comprehensive smoke test to verify existing rendering functionality works after vendoring. **Test Coverage:** - [ ] Desktop (macOS) renders correctly - [ ] iOS builds and renders - [ ] PBR materials display properly - [ ] Lighting works (point, directional, spot) - [ ] Shadows render - [ ] No visual regressions **Notes:** This is a GO/NO-GO gate for Phase 2. If tests fail, stop and debug before proceeding.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/audio
Spatial audio engine, sound playback, audio mixing, music systems, 3D audio positioning
 area/content
Art assets, models, textures, audio files, dialogue trees, narrative content, game data
 area/core
Foundation systems, memory management, math libraries, data structures, core utilities
 area/docs
Documentation, technical specs, RFCs, architecture decisions, API docs, tutorials, guides
 area/infrastructure
Deployment pipelines, hosting, cloud services, monitoring, logging, DevOps, releases
 area/networking
iroh P2P, CRDT sync, gossip protocol, network replication, connection management
 area/platform
iOS/macOS platform code, cross-platform abstractions, input handling, OS integration
 area/rendering
Graphics pipeline, Bevy rendering, shaders, materials, lighting, cameras, meshes, textures
 area/rfc
RFC proposals, design discussions, architecture planning, feature specifications
 area/simulation
Agent systems, NPC behaviors, AI, game mechanics, interactions, simulation logic
 area/tooling
Build systems, CI/CD pipelines, development tools, code generation, testing infrastructure
 area/ui-ux
User interface, menus, HUD elements, input feedback, screen layouts, navigation
 dependencies
Pull requests that update a dependency file
 epic
Large body of work spanning multiple features
 rust
Pull requests that update rust code
No Label area/rendering
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
gitea_admin siennathesane
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: studio/marathon#11
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?