Page MenuHomePhabricator

Goldilocks: Runner
Closed, CompletedPublic

Description

Objective

Runner functions for running Tests, Suites, and (eventually) executing benchmarks. Must be able to run a test multiple times, and will be responsible for storing and return the results...once we know what that looks like.

Dependencies and Tools

  • C++
  • IOSqueak
  • PawLIB (headers only)

Tips

Don't worry about the benchmarker part yet. Just get tests running.

Consider: Should a single runner be able to run multiple objects (tests, suites), or should one runner run one object, and create other runners for each sub-unit (e.g. each suite or test contained in the suite).

References

Tests
Runner
Workflow

Details

Task Type
Feature
Proposed Urgency
Established
Gravity
Triage Gravity
Friction
Triage Friction
Relativity
Triage Relativity
Volatility (Caught At)
Not a Bug
Origin
Not a Bug/Unknown

Event Timeline

jcmcdonald triaged this task as p4: Now priority.Mar 16 2020, 2:53 PM
jcmcdonald created this task.
jcmcdonald lowered the priority of this task from p4: Now to p3: Next.Apr 13 2020, 5:14 PM
jcmcdonald moved this task from Backlog to Restricted Project Column on the Goldilocks [Project] board.Apr 13 2020, 5:19 PM
jcmcdonald edited projects, added Unknown Object (Project); removed Goldilocks [Project].
jcmcdonald raised the priority of this task from p3: Next to p4: Now.
jcmcdonald updated the task description. (Show Details)

You should associate your Differential with this. At right, select Edit Related Objects...Edit Revisions and select the related Differential.

Also, be sure to close this when the task is done. If it isn't finished, make subtasks as appropriate.

jcmcdonald edited projects, added Goldilocks [Project]; removed Unknown Object (Project).Jun 19 2021, 10:14 AM