Skip to content

GitLab

  • Menu
    • Projects Groups Snippets
      Help
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • L lab06
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1
    • Issues 1
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • cs2-22wi
  • lab06
  • Issues
  • #1

Something went wrong while setting issue due date.
Closed
Open
Created 3 years ago by James C Bowden@jbowdenOwner
  • New issue

  • Report abuse

  • New issue

  • Report abuse

getMoves() tests don't catch everything

Open

getMoves() tests don't catch everything

A lot of people neglect the case where there are multiple heaps of a certain size that need to get copied over, or else the heap we are splitting has more than one of the same size - none of the tests check for this

also, https://gitlab.caltech.edu/cs2-22wi/lab06-hypno/-/commit/f188b7ddb1f02506b2e8a727d40ae675052b0649#3b4132cb9338d3cb77f0712f8a2f5a5c5979cf6d_25_39

Linked issues
0


  • You're only seeing other activity in the feed. To add a comment, switch to one of the following options.
Please register or sign in to reply
0 Assignees
None
Assign to
Milestone
No milestone
None
None
Time tracking
No estimate or time spent
Due date
None
None
Labels
0
None
0
None
    Assign labels
  • Manage project labels

Confidentiality
Not confidential
Not confidential

You are going to turn on confidentiality. Only team members with at least Reporter access will be able to see and leave comments on the issue.

Lock issue
Unlocked
0
0 participants
Reference:

Menu

Projects Groups Snippets
Help