Skip to content

Conversation

@tisnik
Copy link
Contributor

@tisnik tisnik commented Jul 17, 2025

Description

LCORE-304: Info about tests

Type of change

  • Refactor
  • New feature
  • Bug fix
  • CVE fix
  • Optimization
  • Documentation Update
  • Configuration Update
  • Bump-up service version
  • Bump-up dependent library
  • Bump-up library or tool used for development (does not change the final image)
  • CI configuration change
  • Konflux configuration change
  • Unit tests improvement
  • Integration tests improvement
  • End to end tests improvement

Related Tickets & Documents

  • Related Issue #LCORE-304

Summary by CodeRabbit

  • Documentation
    • Updated instructions to use "uv" instead of "pdm" for development setup.
    • Reorganized and enhanced the README structure, including improved table of contents and new sections for OpenAPI specification and Testing.
    • Moved and clarified the "Integration with Llama Stack" section with an illustrative image.
    • Added a dedicated testing guide detailing testing layers, frameworks, and best practices.
    • Introduced a minimal README for GitHub Pages documentation.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jul 17, 2025

Walkthrough

Documentation was reorganized and updated: references to the Python tool "pdm" were replaced with "uv" in contributing instructions, the testing section was moved from CONTRIBUTING.md to a new docs/testing.md file, and the README.md table of contents and sections were restructured. A minimal docs/README.md was introduced for GitHub Pages.

Changes

File(s) Change Summary
CONTRIBUTING.md Replaced "pdm" with "uv" for Python environment setup; removed the entire testing section.
README.md Reorganized table of contents, moved "Integration with Llama Stack" under "Configuration", added "Testing" section referencing external guide.
docs/testing.md Added new, detailed testing documentation covering test types, running tests, frameworks, and tips.
docs/README.md Added minimal file with "GitHub pages" text for documentation site.

Poem

In docs we hop, with uv we run,
Testing tips now neatly spun.
Table of contents, shuffled anew,
Llama Stack finds a cozy view.
GitHub Pages gets a tiny cheer—
Rabbits love when docs are clear!
🐇📚✨


🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (7)
docs/README.md (1)

1-2: Placeholder is too thin – add at least a short intro or redirect

docs/README.md shows only the H-1 header. GitHub Pages will render a near-empty page, which looks broken.

-# GitHub pages
+# Lightspeed-Stack Documentation
+
+Welcome 👋 – this directory is published via GitHub Pages.  
+See the full documentation at [`../README.md`](../README.md) or browse sub-pages in `docs/`.
docs/testing.md (3)

5-8: Fix list numbering / indentation (MD007)

The three bullets render as a single paragraph because each line starts with 1. without a blank line after the heading. Either insert blank lines or use proper ordered-list syntax:

-1. Unit Tests
-1. Integration Tests
-1. End to end Tests
+1. **Unit tests**
+2. **Integration tests**
+3. **End-to-end tests**

160-169: Add language specifiers to fenced code blocks (MD040)

Two blocks (stdout capture & log capture) miss a language tag, breaking syntax highlighting and some linters. Prefix them with python:

-```
+```python
 def test_foobar(capsys):
     ...

60-69: Mixed list markers trigger MD004 – unify to asterisks or dashes

Lines showing the directory tree switch from * to -. Pick one style (project uses * elsewhere) for consistency.

README.md (1)

14-35: Run the TOC generator – anchors/indentation are out of sync

After moving “Integration with Llama Stack” and adding “Testing”, the manual list no longer matches automatic anchors (indent depth, alphabetical order).
Please execute :UpdateToc (or make toc) so the generated TOC stays reliable.

CONTRIBUTING.md (2)

6-23: TOC still lists the removed Testing subsection

Rows 18-22 point to headings that no longer exist. Regenerate the TOC to avoid 404-style jumps.


37-43: Typo: “Prerequisities” → “Prerequisites”

Small spelling fix improves searchability.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 75b4f4f and 32eaa20.

📒 Files selected for processing (4)
  • CONTRIBUTING.md (2 hunks)
  • README.md (3 hunks)
  • docs/README.md (1 hunks)
  • docs/testing.md (1 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
docs/testing.md

18-18: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)


19-19: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)


20-20: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)


21-21: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)


23-23: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)


24-24: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)


26-26: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)


27-27: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)


28-28: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)


30-30: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)


31-31: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)


32-32: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)


37-37: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)


38-38: Unordered list indentation
Expected: 4; Actual: 8

(MD007, ul-indent)


39-39: Unordered list indentation
Expected: 4; Actual: 8

(MD007, ul-indent)


40-40: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)


41-41: Unordered list indentation
Expected: 4; Actual: 8

(MD007, ul-indent)


42-42: Unordered list indentation
Expected: 4; Actual: 8

(MD007, ul-indent)


43-43: Unordered list indentation
Expected: 4; Actual: 8

(MD007, ul-indent)


60-60: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


60-60: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)


61-61: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


61-61: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)


68-68: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


69-69: Unordered list style
Expected: asterisk; Actual: dash

(MD004, ul-style)


160-160: Fenced code blocks should have a language specified

(MD040, fenced-code-language)


175-175: Fenced code blocks should have a language specified

(MD040, fenced-code-language)

🔇 Additional comments (2)
docs/testing.md (1)

31-35: Paragraph refers to “integration” coverage inside “Unit tests” section

The wording is confusing:

“Currently code coverage threshold for integration tests is set to 60%”

This sentence lives inside the Unit tests chapter. Either move it to the Integration tests chapter or change “integration” → “unit”.

CONTRIBUTING.md (1)

63-70: Make target names don’t match actual Makefile

Docs now say:

make unit-tests
make integration-tests

The repository (and newly added docs/testing.md) uses make test-unit / make test-integration.

-make unit-tests
-make integration-tests
+make test-unit
+make test-integration

@tisnik tisnik merged commit cf8147c into lightspeed-core:main Jul 17, 2025
17 checks passed
@are-ces are-ces mentioned this pull request Jul 17, 2025
18 tasks
@coderabbitai coderabbitai bot mentioned this pull request Jul 21, 2025
15 tasks
@coderabbitai coderabbitai bot mentioned this pull request Sep 12, 2025
15 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant