git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [RFC PATCH 0/1] Unit tests for khash.h

From
Taylor Blau <me@ttaylorr.com>
Date
May 31, 2023, 22:35 UTC
Message-ID
<ZHfLwpX7nNVjBvE5@nand.local>
In-Reply-To
<20230531155142.3359886-1-siddhartth@google.com>
Hi Siddharth,
On Wed, May 31, 2023 at 05:51:41PM +0200, Siddharth Singh wrote:
> This RFC patch adds unit tests for khash.h. It uses the C TAP harness
> to illustrate the test cases [1]. This is not intended to be a
> complete implementation. The purpose of this patch to get your
> thoughts on the unit test content, not the test framework itself.

Thanks for working on this, and for opening the discussion up. I took only a brief look through the actual changes. But I think the much more interesting discussion is on the approach, so I'll refrain from commenting on the tests themselves.

I am somewhat skeptical of this as a productive direction, primarily because khash already has tests [1] that exercise its functionality. I'm not necessarily opposed to (light) testing of oid_set, oid_map, and oid_pos, which are khash structures, but declared by Git.

Even still, I don't think that we are testing much in that case, since the boundary between Git and khash is limited to the KHASH_INIT macro.

So... I dunno. I'm not strongly opposed here, but I think this is probably not the most productive place to start adding tests.

Thanks, Taylor

[1]: https://github.com/attractivechaos/klib/blob/master/test/khash_test.c
Previous: Siddharth SinghNext: Junio C Hamano
Message 3 of 12 in “Unit tests for khash.h”
  1. 0/1 Unit tests for khash.hSiddharth Singh, May 31, 2023
  2. 1/1 khash_test.c: add unit testsSiddharth Singh, May 31, 2023
  3. Taylor BlauMay 31, 2023
  4. Junio C HamanoJun 1, 2023
  5. Phillip WoodJun 1, 2023
  6. Eric WongMay 31, 2023
  7. Phillip WoodJun 1, 2023
  8. khash_test.c : add unit testsSiddharth Singh, Jun 27, 2023
  9. Glen ChooJun 30, 2023
  10. Siddharth SinghJul 7, 2023
  11. Glen ChooJul 7, 2023
  12. Glen ChooJun 30, 2023

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.