Log inGet started
Package

fantasyMaterials.testSuite

Newest version

README.md

fantasyMaterials tests

A quick suite that checks Rune and Ember through materialLibraryKit's own API and checks:

  • all 24 materials are registered with the library under the fantasy collection, in order (runeStoneBlue first), fully tagged (fantasy, kind, style as realistic / hand-painted / toon, tile size, finish, metalness, glowing, animated and what moves, see-through, texture count and cost, search words) and found by the library's filters;
  • Checks.budget passes for all 24 (at most 9 sampled textures), each textureKB matches the measured memory, and the collection stays under 64 MB;
  • every colour a material sets reaches its shader, every glow peaks well above a lit white surface (its white-hot core between 2.5 and 40), see-through materials draw without sorting (ectoplasm additive with no depth write; crystal a solid refracting body that writes depth, drawn before blended things; the window opaque), own textures are bound by asset id;
  • green-up normals proved on a synthetic dome;
  • Checks.seams on one material per shader path, held still, every one passing on the render and on every texture's edges;
  • apply, swap and clear by name on a shared object; reference pictures, gallery boards and shrine meshes; all 24 on one gallery ring; the README in step with the version, every material and the known engine issues.

It leaves alone what one engine cannot see: a second player (the library's own suite covers sync through its loopback), the browser frame rate, and the side-by-side look against the reference pictures (recorded in the package README). Each test runs inside Sync.isolate(), so nothing it does reaches other players. It holds the gallery's watchdog off while each test runs; once the run ends, FantasyShowcase repairs whatever the run released (walls, floor tiles, plaques, trim) within a few seconds, in edit mode as well as in play. It passes 14 of 14 in the authoring world and in a fresh world that installed the package from its published release. Run it with asset.resolve("fantasyMaterials.tests.fantasyMaterials", "testSuite"):run().