How Should You Test Branches and Endings in Novelez Before Sharing?

You finish editing a visual novel in Novelez, press Preview, choose the route you already know, and reach an ending without trouble. That feels like a successful test. It is only proof that one familiar path worked once.

A branching story needs a different kind of pass. You have to separate three questions that are easy to blur together: Does the route map make sense? Does each scene look and sound right when it runs? Can a player actually travel from the real opening to every intended ending? Novelez puts the flow view, block-level preview, and browser player close together, but each answers a different question.

The useful test order is map, segment, full run. Starting with the map saves you from repeatedly playing a route whose structure is already wrong. Segment previews make local repairs fast. Full runs come last because they are the only ones that prove the route works as a player will encounter it.

First, can you name the routes you intend to ship?

Before opening Preview, make a tiny route sheet outside the story. It does not need to be a formal test document. Write the opening point, every choice that changes the destination, and the endings you expect to reach. If two choices change only a line or reaction before returning to the same scene, record them as variations, not separate routes.

This list prevents a common mistake: testing whatever path happens to be easiest and assuming the rest resembles it. A three-ending story needs at least three complete route records. If one ending requires a particular sequence of choices, write that sequence down. The test is complete when the expected destination and the observed destination match, not when the story simply stops somewhere.

Keep the sheet small enough to use. For each route, record the choice sequence, intended ending, actual ending, and first point where the result diverged. You do not need a bug-tracking system to discover that two endings both receive the same route. You need a repeatable path.

What should you inspect in the flow view?

Use Novelez's visual flow view before you play. Begin at the real starting block and trace every choice forward with your eyes. Each branch should either reach an ending or reconnect at a scene you can identify. If a path simply stops, jumps somewhere unexpected, or enters a section that has no way back to the planned route, mark it before you touch the player.

Look at convergence points with extra care. Two branches can rejoin the same scene while arriving with different knowledge. A character may refer to a secret that only one route revealed. A prop can appear even though the player skipped the scene where it was found. The graph can show that the blocks connect, but it cannot decide whether the shared scene still makes sense from both directions.

Also count endings from the map and compare that count with your route sheet. An ending block that exists but has no incoming path is not a hidden reward. It is unreachable content. A choice that leaves the main route and quietly falls into the next nearby block may look playable while ignoring the destination you intended. Structural inspection catches that class of problem earlier than a polished screen does.

When is a selected-block preview the right tool?

After the map is coherent, use short previews for local questions. In Novelez, selecting a block before opening Preview can start the player from that point. That is useful when the problem sits late in the story: a missing expression, a background that changes one line too soon, music that fails to stop, or a choice whose wording no longer matches the following scene.

Test one claim at a time. If you changed the portrait in a confession scene, start near that scene and check the portrait. If you repaired a jump, preview the choice and its immediate destination. Short loops keep a two-minute correction from becoming a twenty-minute replay.

There is one limit worth writing in large letters: starting from a later block does not prove that a player can reach it. The local scene may run perfectly even when an earlier choice points somewhere else. It may also depend on information or state that a normal route establishes before arrival. Treat the segment preview as a rehearsal, not a route certificate.

When a local problem is fixed, note the route that contains it. That route must still be included in the full pass. Otherwise the fastest testing tool can accidentally erase the only test that matters.

How do you run the complete route pass?

Return to the actual opening and follow the first sequence on your route sheet. Do not skip an awkward choice because you know what it was supposed to do. Read the choice, make the recorded selection, and watch the first line after the transition. Many branch errors reveal themselves there: the wrong speaker is still on screen, the background belongs to the other route, or the next line assumes an event the player never saw.

Continue until an ending screen appears. Record which ending you reached and whether the route remained understandable. Then restart from the opening and test the next distinct sequence. A branch that reconverges quickly still deserves one pass through the join, because continuity errors live at the seam.

During these runs, watch more than navigation. Check that speaker names, portraits, backgrounds, and audio change with the scene. Let dialogue boxes fill naturally instead of clicking through at maximum speed. Confirm that every choice is readable and that the ending feels like the consequence of the route the player took. A technically reachable ending can still be narratively wrong.

Fix one failed route, then run that same route from the opening again. Do not repair three different paths and test only the last one. A shared block may affect several routes, and the second pass tells you whether the correction solved the reported path without moving the problem elsewhere.

What should happen before you use Share?

Novelez's Share action is publication, not a private preview link. It places the work in the gallery and creates a URL other people can open. That makes the browser preview the right place for your private author pass. Share after the planned routes reach their intended endings and the title, category, description, menu image, audio, and credits are ready for public viewing.

Then open the published URL as a player would. Run at least one complete route there, including the ending. The editor preview proves the current project can play inside your working session. The public check proves the shared page opens and delivers the assets and interactions a visitor will receive.

If you are not ready for discovery, keep the project unpublished. You can switch a shared project back to private in settings, but that is a visibility control, not a substitute for the test pass you skipped before publishing.

The smallest useful routine is straightforward: route sheet, flow inspection, focused segment previews, full runs from the opening, and one public check after sharing. Which part of your current Novelez project is hardest to verify from the start: a choice sequence, a reconverging scene, or an ending that sometimes receives the wrong route?