Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
L
LIGO
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 155
    • Issues 155
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Jira
    • Jira
  • Merge Requests 45
    • Merge Requests 45
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ligolang
  • LIGO
  • Issues
  • #1078

Closed
Open
Opened Dec 18, 2020 by Suzanne Soy@ligo.suzanne.soyMaintainer

tests in test_heuristic_break_ctor (in branch origin/prototype-typer-test-heuristic-break-ctor currently) should randomize the order of the tests in the db

e.g.

  (*create a state :)
    state = [
      (constraint 1L a = int)
      (constraint 2L b = record { x = a ; y = a })
      (constraint 3L c = map(a, b))
      (constraint 4L d = poly ∀ a, a -> int -> map(a,int) )
    ] *)
  (* pass a new constraint to the selector:
      (constraint 5L c = map(f, g))
  *)
  (* check that the selector returns a list containing the pair of constraints (3L, 5L) or (5L, 3L) *)

The test should randomize the order, above the order is (1,2,3,4)+5 → {3,5}. Any order where the "new constraint" is 3 or 5 (i.e. one of the two constraints being returned) is valid, and the results should be identical (modulo the order in the result pair, i.e. result should always be (3,5) or (5,3)).

Edited Dec 18, 2020 by Suzanne Soy
Assignee
Assign to
Typer: Prototype MVP
Milestone
Typer: Prototype MVP
Assign milestone
Time tracking
None
Due date
None
Reference: ligolang/ligo#1078