)]}' { "commit": "78bf8b9008519a00f5bb2c226f049eb2f245a28c", "tree": "4b359dc7708d46256f04fc6025c5e96653d4eb59", "parents": [ "a12f4478252a02f44c4b15be0a5824407597e0a1" ], "author": { "name": "Daniel Latypov", "email": "dlatypov@google.com", "time": "Wed Apr 07 13:59:02 2021 -0700" }, "committer": { "name": "Daniel Latypov", "email": "dlatypov@google.com", "time": "Thu Aug 05 16:37:18 2021 -0700" }, "message": "mocking.rst: add start of write-up on mocking + function redirection\n\nNote: this isn\u0027t so much about mocking as it is about redirecting\nfunction calls (potentially to a mock). But kunit.dev/mocking will\nprobably be more memorable and match more what people search for.\n\nIn [1], a doc was presented on stream but couldn\u0027t be made publicly\navailable.\n\nThis is the start of the process of making it available.\n\nUnlike that doc, this page has a different audience and is intended to\nalso try and give a basic feel for what mocking is and why you\nwould/would not want to use it.\n\nThis first patch includes the description of fakes vs mocks and a\nskeleton for the rest (the doc\u0027s overview of the different kinds of\napproaches to adding indirection).\n\n[1] https://events.linuxfoundation.org/mentorship-session-kunit-testing-strategies/\n\nChange-Id: I54899388cc2ca07b1ba5d41dc7add4363cab2223\nSigned-off-by: Daniel Latypov \u003cdlatypov@google.com\u003e\n", "tree_diff": [ { "type": "modify", "old_id": "12194d6507bd1c6e8672562245ac55c6b60f8e4d", "old_mode": 33188, "old_path": "index.rst", "new_id": "2936d33191e4e9acff9b154d7c0aff29061a254a", "new_mode": 33188, "new_path": "index.rst" }, { "type": "add", "old_id": "0000000000000000000000000000000000000000", "old_mode": 0, "old_path": "/dev/null", "new_id": "b84bbe192d9da7d6a8b9532d63eee8f3b13e2989", "new_mode": 33188, "new_path": "mocking.rst" } ] }