RRepoGEO

REPOGEO REPORT · LITE

cweill/gotests

Default branch develop · commit 2a672c52 · scanned 5/13/2026, 4:46:41 AM

GitHub: 5,302 stars · 350 forks

AI VISIBILITY SCORE
78 /100
Needs work
Category recall
2 / 2
Avg rank #2.0 when recommended
Rule findings
1 pass · 1 warn · 0 fail
Objective metadata checks
AI knows your name
2 / 3
Direct prompts that named your repo
HOW TO READ THIS REPORT

Action plan is what to do next — copy-pasteable changes prioritized by impact. Category visibility is the real GEO test: when a user asks an AI a brand-free question that should surface cweill/gotests, does the AI actually recommend you — or your competitors? Objective checks verify the metadata signals AI engines weight first. Self-mention check detects whether AI even knows you exist by name.

Action plan — copy-paste fixes

3 prioritized changes generated by gemini-2.5-flash. Mark items done after you ship the fix.

OVERALL DIRECTION
  • highreadme#1
    Clarify core differentiator in README's opening paragraph

    Why:

    CURRENT
    gotests is a powerful Go test generator that automatically creates table-driven tests from your source code. It analyzes function and method signatures to generate comprehensive test scaffolding, saving you time and ensuring consistency across your test suite.
    COPY-PASTE FIX
    gotests is a powerful Go test *boilerplate generator* that automatically creates comprehensive, idiomatic table-driven tests from your source code. Unlike general testing frameworks or IDE features, gotests specializes in providing the full boilerplate structure for a given function, method, or interface, analyzing signatures to generate complete test scaffolding and ensuring consistency across your test suite.
  • mediumhomepage#2
    Add a homepage URL to the repository settings

    Why:

    COPY-PASTE FIX
    https://cweill.github.io/gotests/
  • lowreadme#3
    Add a 'Comparison' or 'Why gotests?' section to the README

    Why:

    COPY-PASTE FIX
    ## Comparison / Why gotests?
    
    gotests is a specialized tool focused solely on *generating* Go test boilerplate, particularly for table-driven tests. It complements, rather than replaces, testing frameworks like `testify` or `ginkgo`, which provide assertion libraries and test organization structures. Unlike IDE features (e.g., GoLand, VS Code Go Extension) that might offer basic test stub creation, gotests deeply analyzes function signatures to produce comprehensive, idiomatic Go test structures, saving significant manual effort and ensuring consistency. It's also distinct from the `go test` command, which is for *running* tests, not generating them.

Category GEO backends resolved for this scan: google/gemini-2.5-flash, deepseek/deepseek-v4-flash

Category visibility — the real GEO test

Brand-free queries asked to google/gemini-2.5-flash. Did AI recommend you, or someone else?

Same questions for every model — switch tabs to compare answers and rankings.

Recall
2 / 2
100% of queries surface cweill/gotests
Avg rank
#2.0
Lower is better. #1 = top recommendation.
Share of voice
22%
Of all named tools, what % are you?
Top rival
GoLand
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. GoLand · recommended 2×
  2. VS Code Go Extension · recommended 1×
  3. go test · recommended 1×
  4. stretchr/testify · recommended 1×
  5. ginkgo · recommended 1×
  • CATEGORY QUERY
    How to quickly create Go test files and boilerplate for existing functions?
    you: #2
    AI recommended (in order):
    1. GoLand
    2. gotests (cweill/gotests) ← you
    3. VS Code Go Extension
    4. go test
    Show full AI answer
  • CATEGORY QUERY
    What Go tools help automate the creation of table-driven test cases?
    you: #2
    AI recommended (in order):
    1. GoLand
    2. gotests ← you
    3. testify/suite (stretchr/testify)
    4. ginkgo
    5. text/template
    Show full AI answer

Objective checks

Rule-based audits of metadata signals AI engines weight most.

  • Metadata completeness
    warn

    Suggestion:

  • README presence
    pass

Self-mention check

Does AI even know your repo exists when asked about it directly?

  • Compared to common alternatives in this category, what is the core differentiator of cweill/gotests?
    pass
    AI did not name cweill/gotests — likely talking about a different project

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

  • If a team adopts cweill/gotests in production, what risks or prerequisites should they evaluate first?
    pass
    AI named cweill/gotests explicitly

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

  • In one sentence, what problem does the repo cweill/gotests solve, and who is the primary audience?
    pass
    AI named cweill/gotests explicitly

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

Embed your GEO score

Drop this badge into the README of cweill/gotests. It auto-updates whenever the report is rescanned and links back to the latest report — easy public proof that you care about AI discoverability.

RepoGEO badge previewLive preview
MARKDOWN (README)
[![RepoGEO](https://repogeo.com/badge/cweill/gotests.svg)](https://repogeo.com/en/r/cweill/gotests)
HTML
<a href="https://repogeo.com/en/r/cweill/gotests"><img src="https://repogeo.com/badge/cweill/gotests.svg" alt="RepoGEO" /></a>
Pro

Subscribe to Pro for deep diagnoses

cweill/gotests — Lite scans stay free; this card itemizes Pro deep limits vs Lite.

  • Deep reports10 / month
  • Brand-free category queries5 vs 2 in Lite
  • Prioritized action items8 vs 3 in Lite