Skip to content

[Feature]: PractRand/Smarter Random Correctness Testing Strategy #286

Description

Feature Description

Random numbers are a core part of this toolkit, we should utilize even more intelligent verification strategies. If they are too expensive, or non-deterministic, we can move them to nightly style jobs, with auto-issue opening and regression checks.

Use Case / Motivation

Make randoms more correct

Proposed Solution

Research practrand techniques and current state of the art verification methodologies

Alternatives Considered

Don't do that and maybe have bad randoms.

Unity Version

None

Package Version

None

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions