feat: server tests

eschizoid · eschizoid · commit b61e6b688f4c · 2025-05-21T20:07:34.000-05:00
diff --git a/src/main/kotlin/mcp/code/analysis/server/Server.kt b/src/main/kotlin/mcp/code/analysis/server/Server.kt
@@ -12,7 +12,6 @@ import io.ktor.util.collections.*
 import io.modelcontextprotocol.kotlin.sdk.*
 import io.modelcontextprotocol.kotlin.sdk.server.*
 import io.modelcontextprotocol.kotlin.sdk.server.Server as SdkServer
-import kotlin.text.get
 import kotlinx.coroutines.Job
 import kotlinx.coroutines.delay
 import kotlinx.coroutines.launch
@@ -31,7 +30,7 @@ import org.slf4j.LoggerFactory
  * Server for analyzing GitHub repositories using the Model Context Protocol (MCP). Provides functionalities for
  * analyzing GitHub repositories and checking analysis status.
  */
-open class Server(
+class Server(
   private val repositoryAnalysisService: RepositoryAnalysisService = RepositoryAnalysisService(),
   private val logger: Logger = LoggerFactory.getLogger(Server::class.java),
   private val implementation: Implementation =
@@ -70,7 +69,7 @@ open class Server(
    *
    * @param port The port number on which the SSE MCP server will listen for client connections.
    */
-  open fun runSseMcpServerWithPlainConfiguration(port: Int): Unit = runBlocking {
+  fun runSseMcpServerWithPlainConfiguration(port: Int): Unit = runBlocking {
     val servers = ConcurrentMap<String, SdkServer>()
     logger.info("Starting SSE server on port $port.")
     logger.info("Use inspector to connect to the http://localhost:$port/sse")
@@ -132,7 +131,7 @@ open class Server(
    *
    * @param port The port number on which the SSE MCP server will listen for client connections.
    */
-  open fun runSseMcpServerUsingKtorPlugin(port: Int): Unit = runBlocking {
+  fun runSseMcpServerUsingKtorPlugin(port: Int): Unit = runBlocking {
     logger.debug("Starting SSE server on port $port")
     logger.debug("Use inspector to connect to http://localhost:$port/sse")
 
@@ -149,7 +148,7 @@ open class Server(
    *
    * @return The configured MCP server instance.
    */
-  open fun configureServer(): SdkServer {
+  fun configureServer(): SdkServer {
     val server = SdkServer(implementation, serverOptions)
 
     server.addTool(
diff --git a/src/main/kotlin/mcp/code/analysis/service/ModelContextService.kt b/src/main/kotlin/mcp/code/analysis/service/ModelContextService.kt
@@ -87,9 +87,9 @@ data class ModelContextService(
    * @return A structured prompt for the model
    */
   fun buildInsightsPrompt(codeSnippets: List<String>, readme: String) =
-    """|You are analyzing a software codebase that includes a README file and source code files. Your task is to extract a structured summary of the codebase’s architecture, components, and relationships.
+    """|You are analyzing a software codebase that includes a README file and source code files. Your task is to extract a structured, file-by-file analysis of the codebase's architecture, components, and interconnections.
        |
-       |Use the information provided below.
+       |Use only the information provided below.
        |
        |----------------------
        |README Content:
@@ -104,14 +104,14 @@ data class ModelContextService(
        |${codeSnippets.joinToString("\n\n")}
        |----------------------
        |
-       |For each file:
-       |- File name and language
-       |- Main classes, functions, or data structures
-       |- Purpose of the file (based on comments, function names, etc.)
-       |- Key public interfaces (functions, methods, classes)
-       |- If applicable, how this file connects to other parts of the codebase (e.g. imports, API usage, function calls)
+       |For each file, extract the following:
+       |- File path and programming language
+       |- Main classes, functions, or data structures defined
+       |- Purpose of the file (what it does and why it exists)
+       |- Key public interfaces (classes, methods, functions)
+       |- Dependencies and relationships (e.g., imports, API usage, method calls across files)
        |
-       |Use this format:
+       |Output using this format:
        |
        |### File: path/to/file.ext (Language: X)
        |- **Purpose**: ...
@@ -120,8 +120,11 @@ data class ModelContextService(
        |- **Relationships**:
        |  - ...
        |
-       |Repeat this for all files. Avoid speculation. Be concise and grounded in the content above.
-       |"""
+       |Important:
+       |- Be specific and factual; avoid speculation.
+       |- Use information from comments, function names, or obvious patterns.
+       |- Summarize concisely; no fluff.
+    """
       .trimMargin()
 
   /**
@@ -131,40 +134,40 @@ data class ModelContextService(
    * @return A structured prompt for the model
    */
   fun buildSummaryPrompt(insights: String): String =
-    """|You are writing a high-level but technically accurate summary of a software codebase for a developer unfamiliar with the project.
+    """|You are writing a high-level, technically accurate summary of a software codebase. The reader is a developer unfamiliar with the project, so your explanation should clarify the purpose, structure, and important technical details.
        |
-       |Use the extracted structural analysis below to build the summary.
+       |Use the structured analysis below to guide your summary.
        |
        |----------------------
-       |
        |Structural Analysis:
        |
        |${parseInsights(insights)}
        |----------------------
        |
-       |You must include:
+       |Include the following in your output:
        |
-       |1. **Main Purpose** – what the software does, who might use it.
-       |2. **Architecture Overview** – main components and how they interact.
-       |3. **Technologies and Languages** – what languages, frameworks, or tools are used.
-       |4. **Key Workflows** – example flow of data, processing, or control (e.g., "HTTP request -> router -> controller -> database").
-       |5. **Strengths and Weaknesses** – any observed complexity, tight coupling, lack of documentation, or reusable design patterns.
+       |1. **Main Purpose** – What the software does, the problem it solves, and who uses it.
+       |2. **Architecture Overview** – Key components or layers and how they interact. Describe patterns if evident (e.g., microservices, event-driven, layered architecture).
+       |3. **Technologies and Languages** – List the programming language(s), major frameworks/libraries, and any notable tools.
+       |4. **Key Workflows** – Show how data or control flows through the system. Prefer concrete examples (e.g., "Kafka -> Consumer -> Metrics tracker -> Monitoring system").
+       |5. **Strengths and Weaknesses** – Mention any strengths (modularity, patterns, scalability) and issues (tight coupling, complexity, missing docs).
        |
-       |Where helpful, include:
-       |- Short code snippets or function/method names (language-agnostic).
-       |- Architecture patterns if detected (e.g., MVC, pub/sub, monolith, microservice).
+       |Also consider:
+       |- Noteworthy classes, functions, or modules
+       |- Signs of testability, extensibility, or maintainability
+       |- Use of design patterns (Builder, Observer, etc.)
        |
-       |Format the output using Markdown. Be concise and insightful.
-    """
+       |Write the output in well-structured **Markdown**. Be concise, insightful, and avoid guessing.
+       |"""
       .trimMargin()
 
   private suspend fun sendRequest(url: String, request: ChatRequest): HttpResponse {
     return httpClient.post(url) {
       contentType(ContentType.Application.Json)
       setBody(request)
       timeout {
-        requestTimeoutMillis = 10.minutes.inWholeMilliseconds
-        socketTimeoutMillis = 10.minutes.inWholeMilliseconds
+        requestTimeoutMillis = 60.minutes.inWholeMilliseconds
+        socketTimeoutMillis = 60.minutes.inWholeMilliseconds
         connectTimeoutMillis = 120_000
       }
     }
diff --git a/src/test/kotlin/mcp/code/analysis/server/ServerTest.kt b/src/test/kotlin/mcp/code/analysis/server/ServerTest.kt
