or run

npx @tessl/cli init
Log in

Version

Files

tile.json

rubric.jsonevals/scenario-5/

{
  "context": "This evaluation assesses how well an engineer uses karma-qunit's autostart control capabilities to implement a test runner controller. The focus is on proper usage of configuration options, timing control mechanisms, and manual start functionality that karma-qunit provides for managing test execution flow.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Autostart Configuration",
      "description": "Implements an autostart configuration option (boolean parameter) that controls automatic vs manual test execution. When true, tests start automatically; when false, tests wait for manual start() call. This mirrors karma-qunit's client.qunit.autostart configuration behavior.",
      "max_score": 25
    },
    {
      "name": "Timeout-Based Delay",
      "description": "Uses setTimeout() to implement a configurable delay (in milliseconds) before test execution begins. The delay should apply after initialization when autostart is true, reflecting karma-qunit's timeout-based start mechanism for async loading scenarios.",
      "max_score": 25
    },
    {
      "name": "Manual Start Method",
      "description": "Provides a start() method that manually triggers test execution when autostart is false. The method should initiate the test runner only when explicitly called, mirroring the QUnit.start() manual trigger pattern that karma-qunit supports.",
      "max_score": 25
    },
    {
      "name": "Running State Query",
      "description": "Implements an isRunning() method that returns boolean true/false indicating whether tests have started. Prevents multiple starts and provides clear state visibility, similar to how karma-qunit tracks test execution state.",
      "max_score": 15
    },
    {
      "name": "Start Event Promise",
      "description": "Provides an onStart() method returning a Promise that resolves when test execution begins. Enables async coordination with the test start event, demonstrating understanding of promise-based timing patterns in test adapters.",
      "max_score": 10
    }
  ]
}