# Community Testing Framework

**URL:** <https://forums.unrealengine.com/t/community-testing-framework/2762610>\
**Category:** Roadmap\
**Tags:** scale-perform, unreal-editor-for-fortnite, fortnite-creative, fortnite\
**Created:** [September 4, 2026, 3:00pm UTC](https://forums.unrealengine.com/t/community-testing-framework/2762610 "2026-09-04T15:00:00Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ThomasC\_Epic](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/thomasc_epic/32/1203341_2.png) [@ThomasC\_Epic](https://forums.unrealengine.com/u/ThomasC_Epic)\
**Post date:** [September 4, 2026, 3:00pm UTC](https://forums.unrealengine.com/t/community-testing-framework/2762610/1 "2026-09-04T15:00:00Z")

</div>

### **Status**

None

**The testing framework records a play session and replays it against a later build, so a regression shows up in a rerun rather than in manual playtesting**.

A test is authored by playing the experience: a run is recorded, then replayed later so its outcome can be compared with what the recording produced. Replaying a run faithfully means reproducing physics, networking, and recorded input, which is what the framework is built around. It’s for developers who check for regressions by playtesting each build by hand.

---

<div class="post-metadata">

**Author:** ![FragileNucleusGames](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/fragilenucleusgames/32/1103901_2.png) [@FragileNucleusGames](https://forums.unrealengine.com/u/FragileNucleusGames)\
**Post date:** [September 4, 2026, 6:17pm UTC](https://forums.unrealengine.com/t/community-testing-framework/2762610/2 "2026-09-04T18:17:07Z")

</div>

Not having to manually run through my test level to verify that everything still works after each update is going to save a lot of time for me. If this lands, a test run of the main level may actually become feasible.
