)]}'
{
  "commit": "be1a5f4469d2947b4a00cf07c143d7552f00fd8c",
  "tree": "6dbc45f1c899bdf56f63a805a56f3186e907593c",
  "parents": [
    "f20186298a025a4f0cb562e12f0071669af2079e"
  ],
  "author": {
    "name": "Scott Todd",
    "email": "scott.todd0@gmail.com",
    "time": "Thu Apr 04 14:31:36 2024 -0700"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Thu Apr 04 14:31:36 2024 -0700"
  },
  "message": "Document testing policy and external test suite. (#16982)\n\nHaving a documented \"test policy\" is one of the checkboxes for\r\nhttps://www.bestpractices.dev/en :\r\n\r\n\u003e The project MUST have a general policy (formal or not) that as major\r\nnew functionality is added to the software produced by the project,\r\ntests of that functionality should be added to an automated test suite.\r\nAs long as a policy is in place, even by word of mouth, that says\r\ndevelopers should add tests to the automated test suite for major new\r\nfunctionality, select \"Met.\"\r\n\r\nWe\u0027ve had an informal policy, but this makes it more explicit.\r\n\r\n---\r\n\r\nWhile touching testing docs, I also added a section for\r\nhttps://github.com/nod-ai/SHARK-TestSuite/ and how that is integrated\r\ninto this repo.",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "2b83f06c8cd7492340df2bbac2c180af2d74e5a9",
      "old_mode": 33188,
      "old_path": "docs/website/docs/developers/general/contributing.md",
      "new_id": "ef4d62940576870971d9694b58d5ce85f8b1eaff",
      "new_mode": 33188,
      "new_path": "docs/website/docs/developers/general/contributing.md"
    },
    {
      "type": "modify",
      "old_id": "0f36eebc58ff207781d9a3a98963b0c5a3645409",
      "old_mode": 33188,
      "old_path": "docs/website/docs/developers/general/testing-guide.md",
      "new_id": "ad1f4b95e8e164596d747977fb26fa523ed35997",
      "new_mode": 33188,
      "new_path": "docs/website/docs/developers/general/testing-guide.md"
    }
  ]
}