Nanguan Lin 7cdbe65a2c Add tests for db indexer in indexer_test.go (#27087) ... As described in the title. Some points: 1. Why need those tests? Because `buildIssueOverview` is not well tested, there are several continuous bugs in the issue overview webpage. 2. Why in indexer_test.go? It's hard to put those tests in `./modules/indexer/issue/db/db_test.go` because those tests need 'real' data in db mocked by fixtures instead of random data in `./modules/indexer/issue/internal/tests`. When using 'real' data(`unittest.PrepareTestDatabase`), `InitIssueIndexer` and the package `init()` function of `indexer` are required to init indexer. 3. Why only db? The other three indexer engines are well tested by random data and it's okay to also test them with 'real' data in db mocked by fixtures. Any follow-up PR is welcome. 4. Those tests are really basic, any more complicated tests are welcome. 5. I think it's also necessary to add tests in `TestAPISearchIssues` in`api_test_issue.go` and `TestIssues` in `home_test.go`		2023-09-16 11:15:21 +08:00
..
code	Update status and code index after changing the default branch (#27018)	2023-09-13 04:43:31 +00:00
internal	Refactor and enhance issue indexer to support both searching, filtering and paging (#26012)	2023-07-31 06:28:53 +00:00
issues	Add tests for db indexer in indexer_test.go (#27087)	2023-09-16 11:15:21 +08:00
stats	move repository deletion to service layer (#26948)	2023-09-08 04:51:15 +00:00