Log inGet started
Package

questKit.package

This package holds more than this page lists. See all of its files in its world.

README.md

questKitTests

Tests over questKit's promises, 38 in all.

21 run in edit mode with progress in memory and no waits longer than a frame: every sample quest loads and every objective kind has one; a broken quest names the field at fault; the README's first example (5 mushrooms, then Ada's conversation completes it, XP and an item handed out); a game's own objective kind; the two-quest chain; all the events; party quests counted once on the deciding machine and copied by members; personal quests never sent; every quest log, tracker board and marker style on desktop and phone screens; and every English catalog key present in Brazilian Portuguese.

17 enter play on the engine's starter player scene and drive real input:

  • the player walks at the very start on keyboard, gamepad and touch;
  • 12 tests, one per quest log style (journal, datapad, panel, cards) and device (keyboard, gamepad, touch): the log is opened and closed the way a player on that device does it, stands walking down while open, gives it back on close, and the player then really moves;
  • a player whose PlayerAvatar link goes missing still walks;
  • 3 tests measure the Quests button against the minimap as navUiKit draws it, on a 1920x1080 desktop, a phone held upright (390x844) and a phone held sideways (844x390), and require a clear gap.

Run with tools.use("tests", "run", { suite = "questKitTests" }) here or in any world that installed questKit.