Skip to content

Test ButtonDarkMode #1724

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Test ButtonDarkMode #1724

wants to merge 3 commits into from

Conversation

hardingjam
Copy link
Contributor

@hardingjam hardingjam commented May 2, 2025

Motivation

Solution

Checks

By submitting this for review, I'm confirming I've done the following:

  • made this PR as small as possible
  • unit-tested any new functionality
  • linked any relevant issues or PRs
  • included screenshots (if this involves a front-end change)

Summary by CodeRabbit

  • Tests
    • Added new tests for the dark mode toggle button to verify correct rendering and toggle behavior between light and dark modes.

@hardingjam hardingjam added the test test code label May 2, 2025
@hardingjam hardingjam added this to the Test coverage, tech debt milestone May 2, 2025
@hardingjam hardingjam self-assigned this May 2, 2025
Copy link
Contributor

coderabbitai bot commented May 2, 2025

"""

Walkthrough

A new test suite has been added for the ButtonDarkMode.svelte component. The tests use Vitest and Svelte Testing Library, and include a mock for the DarkMode component from the flowbite-svelte package. The suite sets up a mock writable store to simulate the color theme state and manages the document's dark class before each test. The tests check rendering of the button and mock component, and verify the correct store updates and DOM class changes when the button is clicked in both light and dark modes.

Changes

File(s) Change Summary
packages/ui-components/src/tests/ButtonDarkMode.test.ts Added a new test suite for ButtonDarkMode.svelte, including rendering, store, and toggle tests.

Sequence Diagram(s)

sequenceDiagram
    participant TestSuite
    participant Document
    participant MockStore
    participant ButtonDarkMode
    participant MockDarkMode

    TestSuite->>Document: Reset 'dark' class
    TestSuite->>MockStore: Initialize colorTheme store
    TestSuite->>ButtonDarkMode: Render component with store
    ButtonDarkMode->>MockDarkMode: Render mocked DarkMode
    TestSuite->>ButtonDarkMode: Simulate button click
    ButtonDarkMode->>Document: Check 'dark' class
    ButtonDarkMode->>MockStore: Update colorTheme ('light' or 'dark')
    TestSuite->>MockStore: Assert updated colorTheme value
Loading

"""


📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between b2335e2 and 0eefe06.

📒 Files selected for processing (1)
  • packages/ui-components/src/__tests__/ButtonDarkMode.test.ts (1 hunks)
🧰 Additional context used
🧠 Learnings (1)
packages/ui-components/src/__tests__/ButtonDarkMode.test.ts (1)
Learnt from: hardingjam
PR: rainlanguage/rain.orderbook#1724
File: packages/ui-components/src/__tests__/ButtonDarkMode.test.ts:1-54
Timestamp: 2025-05-03T10:29:03.985Z
Learning: JSDoc comments are not considered necessary for test files in the rainlanguage/rain.orderbook repository. Test descriptions and assertions are sufficient documentation.
⏰ Context from checks skipped due to timeout of 90000ms (16)
  • GitHub Check: git-clean
  • GitHub Check: test
  • GitHub Check: test
  • GitHub Check: Deploy-Preview
  • GitHub Check: standard-tests (ubuntu-latest, rainix-sol-static)
  • GitHub Check: standard-tests (ubuntu-latest, test-js-bindings)
  • GitHub Check: standard-tests (ubuntu-latest, rainix-sol-legal)
  • GitHub Check: standard-tests (ubuntu-latest, rainix-sol-artifacts)
  • GitHub Check: standard-tests (ubuntu-latest, rainix-wasm-artifacts)
  • GitHub Check: standard-tests (ubuntu-latest, rainix-sol-test)
  • GitHub Check: standard-tests (ubuntu-latest, rainix-wasm-test)
  • GitHub Check: standard-tests (ubuntu-latest, rainix-rs-static)
  • GitHub Check: standard-tests (ubuntu-latest, rainix-rs-artifacts, true)
  • GitHub Check: standard-tests (ubuntu-latest, ob-rs-test, true)
  • GitHub Check: build-tauri (ubuntu-22.04, true)
  • GitHub Check: test
🔇 Additional comments (1)
packages/ui-components/src/__tests__/ButtonDarkMode.test.ts (1)

1-56: Well-structured test suite with comprehensive coverage.

The test implementation looks good with proper isolation through mocking, good test organization, and comprehensive test cases covering both light and dark mode scenarios. The tests verify both the store updates and document class states appropriately.

✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 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.
    • Generate unit testing code for this file.
    • 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 generate unit testing code for this file.
    • @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 generate unit testing code.
    • @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.

@hardingjam hardingjam marked this pull request as ready for review May 2, 2025 14:37
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: 3

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between e02197d and b2335e2.

📒 Files selected for processing (1)
  • packages/ui-components/src/__tests__/ButtonDarkMode.test.ts (1 hunks)
🔇 Additional comments (4)
packages/ui-components/src/__tests__/ButtonDarkMode.test.ts (4)

1-5: LGTM: Good import organization.

The imports are well organized, correctly importing testing utilities, Svelte stores, and the component under test.


6-12: LGTM: Effective mocking approach.

Good practice used for mocking the DarkMode component from flowbite-svelte while preserving the rest of the library's functionality.


14-20: LGTM: Clean test setup.

The test setup correctly initializes a fresh store and resets the document state before each test, ensuring test isolation.


22-27: LGTM: Clear rendering test.

This test effectively verifies that both the button and mocked component render correctly.

Comment on lines 1 to 54
import { render, screen, fireEvent } from '@testing-library/svelte';
import { describe, it, expect, vi, beforeEach } from 'vitest';
import { writable, get, type Writable } from 'svelte/store';
import ButtonDarkMode from '../lib/components/ButtonDarkMode.svelte';

vi.mock('flowbite-svelte', async (importOriginal) => {
const original = await importOriginal<typeof import('flowbite-svelte')>();
return {
...original,
DarkMode: (await import('../lib/__mocks__/MockComponent.svelte')).default
};
});

describe('ButtonDarkMode.svelte', () => {
let mockColorThemeStore: Writable<string | undefined>;

beforeEach(() => {
mockColorThemeStore = writable<string | undefined>(undefined);
document.documentElement.classList.remove('dark');
});

it('renders the button and the DarkMode component', () => {
render(ButtonDarkMode, { props: { colorTheme: mockColorThemeStore } });

expect(screen.getByRole('button')).toBeInTheDocument();
expect(screen.getByTestId('mock-component')).toBeInTheDocument();
});

it('sets colorTheme to "light" when toggled from light mode', async () => {
render(ButtonDarkMode, { props: { colorTheme: mockColorThemeStore } });
const button = screen.getByRole('button');

expect(document.documentElement.classList.contains('dark')).toBe(false);
expect(get(mockColorThemeStore)).toBeUndefined();

await fireEvent.click(button);

expect(get(mockColorThemeStore)).toBe('light');
});

it('sets colorTheme to "dark" when toggled from dark mode', async () => {
document.documentElement.classList.add('dark');

render(ButtonDarkMode, { props: { colorTheme: mockColorThemeStore } });
const button = screen.getByRole('button');

expect(document.documentElement.classList.contains('dark')).toBe(true);
expect(get(mockColorThemeStore)).toBeUndefined();

await fireEvent.click(button);

expect(get(mockColorThemeStore)).toBe('dark');
});
});
Copy link
Contributor

@coderabbitai coderabbitai bot May 2, 2025

Choose a reason for hiding this comment

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

🧹 Nitpick (assertive)

Consider adding JSDoc comments for better test documentation.

The tests are well-structured, but adding JSDoc comments explaining the expected behavior of the ButtonDarkMode component would improve documentation and make it easier for other developers to understand the intended functionality.

+ /**
+  * Tests for ButtonDarkMode.svelte component
+  * 
+  * The ButtonDarkMode component is responsible for toggling between 
+  * light and dark themes by updating a colorTheme store and 
+  * manipulating the dark class on the document element.
+  */
describe('ButtonDarkMode.svelte', () => {
    let mockColorThemeStore: Writable<string | undefined>;
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
import { render, screen, fireEvent } from '@testing-library/svelte';
import { describe, it, expect, vi, beforeEach } from 'vitest';
import { writable, get, type Writable } from 'svelte/store';
import ButtonDarkMode from '../lib/components/ButtonDarkMode.svelte';
vi.mock('flowbite-svelte', async (importOriginal) => {
const original = await importOriginal<typeof import('flowbite-svelte')>();
return {
...original,
DarkMode: (await import('../lib/__mocks__/MockComponent.svelte')).default
};
});
describe('ButtonDarkMode.svelte', () => {
let mockColorThemeStore: Writable<string | undefined>;
beforeEach(() => {
mockColorThemeStore = writable<string | undefined>(undefined);
document.documentElement.classList.remove('dark');
});
it('renders the button and the DarkMode component', () => {
render(ButtonDarkMode, { props: { colorTheme: mockColorThemeStore } });
expect(screen.getByRole('button')).toBeInTheDocument();
expect(screen.getByTestId('mock-component')).toBeInTheDocument();
});
it('sets colorTheme to "light" when toggled from light mode', async () => {
render(ButtonDarkMode, { props: { colorTheme: mockColorThemeStore } });
const button = screen.getByRole('button');
expect(document.documentElement.classList.contains('dark')).toBe(false);
expect(get(mockColorThemeStore)).toBeUndefined();
await fireEvent.click(button);
expect(get(mockColorThemeStore)).toBe('light');
});
it('sets colorTheme to "dark" when toggled from dark mode', async () => {
document.documentElement.classList.add('dark');
render(ButtonDarkMode, { props: { colorTheme: mockColorThemeStore } });
const button = screen.getByRole('button');
expect(document.documentElement.classList.contains('dark')).toBe(true);
expect(get(mockColorThemeStore)).toBeUndefined();
await fireEvent.click(button);
expect(get(mockColorThemeStore)).toBe('dark');
});
});
import { render, screen, fireEvent } from '@testing-library/svelte';
import { describe, it, expect, vi, beforeEach } from 'vitest';
import { writable, get, type Writable } from 'svelte/store';
import ButtonDarkMode from '../lib/components/ButtonDarkMode.svelte';
vi.mock('flowbite-svelte', async (importOriginal) => {
const original = await importOriginal<typeof import('flowbite-svelte')>();
return {
...original,
DarkMode: (await import('../lib/__mocks__/MockComponent.svelte')).default
};
});
+ /**
+ * Tests for ButtonDarkMode.svelte component
+ *
+ * The ButtonDarkMode component is responsible for toggling between
+ * light and dark themes by updating a colorTheme store and
+ * manipulating the dark class on the document element.
+ */
describe('ButtonDarkMode.svelte', () => {
let mockColorThemeStore: Writable<string | undefined>;
beforeEach(() => {
mockColorThemeStore = writable<string | undefined>(undefined);
document.documentElement.classList.remove('dark');
});
it('renders the button and the DarkMode component', () => {
render(ButtonDarkMode, { props: { colorTheme: mockColorThemeStore } });
expect(screen.getByRole('button')).toBeInTheDocument();
expect(screen.getByTestId('mock-component')).toBeInTheDocument();
});
it('sets colorTheme to "light" when toggled from light mode', async () => {
render(ButtonDarkMode, { props: { colorTheme: mockColorThemeStore } });
const button = screen.getByRole('button');
expect(document.documentElement.classList.contains('dark')).toBe(false);
expect(get(mockColorThemeStore)).toBeUndefined();
await fireEvent.click(button);
expect(get(mockColorThemeStore)).toBe('light');
});
it('sets colorTheme to "dark" when toggled from dark mode', async () => {
document.documentElement.classList.add('dark');
render(ButtonDarkMode, { props: { colorTheme: mockColorThemeStore } });
const button = screen.getByRole('button');
expect(document.documentElement.classList.contains('dark')).toBe(true);
expect(get(mockColorThemeStore)).toBeUndefined();
await fireEvent.click(button);
expect(get(mockColorThemeStore)).toBe('dark');
});
});

Copy link
Contributor Author

Choose a reason for hiding this comment

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

not necessary

Copy link
Contributor

Choose a reason for hiding this comment

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

@hardingjam Understood! I'll respect your preference regarding documentation in test files.


✏️ Learnings added
Learnt from: hardingjam
PR: rainlanguage/rain.orderbook#1724
File: packages/ui-components/src/__tests__/ButtonDarkMode.test.ts:1-54
Timestamp: 2025-05-03T10:29:03.985Z
Learning: JSDoc comments are not considered necessary for test files in the rainlanguage/rain.orderbook repository. Test descriptions and assertions are sufficient documentation.

Note: Learnings are effective only in the context of similar code segments. To apply general coding guidelines, please configure review instructions. You can manage existing learnings in the app.

Comment on lines 29 to 39
it('sets colorTheme to "light" when toggled from light mode', async () => {
render(ButtonDarkMode, { props: { colorTheme: mockColorThemeStore } });
const button = screen.getByRole('button');

expect(document.documentElement.classList.contains('dark')).toBe(false);
expect(get(mockColorThemeStore)).toBeUndefined();

await fireEvent.click(button);

expect(get(mockColorThemeStore)).toBe('light');
});
Copy link
Contributor

@coderabbitai coderabbitai bot May 2, 2025

Choose a reason for hiding this comment

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

💡 Verification agent

🧩 Analysis chain

Consider clarifying the toggle logic and adding DOM verification.

The test name suggests toggling "from light mode" but the assertion only verifies the store value changes to "light". This seems counterintuitive - typically toggling from light mode would change to dark mode.

Also, consider verifying DOM class changes after the click to ensure the visual state is updated correctly.


🏁 Script executed:

#!/bin/bash
# Check how ButtonDarkMode.svelte is implemented to understand the expected behavior
cat packages/ui-components/src/lib/components/ButtonDarkMode.svelte

Length of output: 478


Clarify test intent and cover both themes

The ButtonDarkMode toggle simply reads the current document.documentElement theme and writes that value to the store—it doesn’t flip the class itself—so let’s adjust the test names and add a dark-mode scenario.

• Rename the existing test to reflect “clicked in light mode” rather than “toggled from light mode.”
• Add a parallel test for when document.documentElement already has the dark class.
• Since this component only updates the store (and doesn’t mutate the DOM theme), you can drop the post-click DOM assertion here or defer it to an integration test where the store is consumed.

Suggested diff in packages/ui-components/src/__tests__/ButtonDarkMode.test.ts:

-  it('sets colorTheme to "light" when toggled from light mode', async () => {
+  it('sets colorTheme to "light" when clicked in light mode', async () => {
     render(ButtonDarkMode, { props: { colorTheme: mockColorThemeStore } });
     const button = screen.getByRole('button');

     expect(document.documentElement.classList.contains('dark')).toBe(false);
     expect(get(mockColorThemeStore)).toBeUndefined();

     await fireEvent.click(button);

     expect(get(mockColorThemeStore)).toBe('light');
   });

+  it('sets colorTheme to "dark" when clicked in dark mode', async () => {
+    document.documentElement.classList.add('dark');
+    render(ButtonDarkMode, { props: { colorTheme: mockColorThemeStore } });
+    const button = screen.getByRole('button');
+
+    expect(document.documentElement.classList.contains('dark')).toBe(true);
+    expect(get(mockColorThemeStore)).toBeUndefined();
+
+    await fireEvent.click(button);
+
+    expect(get(mockColorThemeStore)).toBe('dark');
+  });
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
it('sets colorTheme to "light" when toggled from light mode', async () => {
render(ButtonDarkMode, { props: { colorTheme: mockColorThemeStore } });
const button = screen.getByRole('button');
expect(document.documentElement.classList.contains('dark')).toBe(false);
expect(get(mockColorThemeStore)).toBeUndefined();
await fireEvent.click(button);
expect(get(mockColorThemeStore)).toBe('light');
});
it('sets colorTheme to "light" when clicked in light mode', async () => {
render(ButtonDarkMode, { props: { colorTheme: mockColorThemeStore } });
const button = screen.getByRole('button');
expect(document.documentElement.classList.contains('dark')).toBe(false);
expect(get(mockColorThemeStore)).toBeUndefined();
await fireEvent.click(button);
expect(get(mockColorThemeStore)).toBe('light');
});
it('sets colorTheme to "dark" when clicked in dark mode', async () => {
document.documentElement.classList.add('dark');
render(ButtonDarkMode, { props: { colorTheme: mockColorThemeStore } });
const button = screen.getByRole('button');
expect(document.documentElement.classList.contains('dark')).toBe(true);
expect(get(mockColorThemeStore)).toBeUndefined();
await fireEvent.click(button);
expect(get(mockColorThemeStore)).toBe('dark');
});

Copy link
Contributor Author

Choose a reason for hiding this comment

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

done

Copy link
Contributor

Choose a reason for hiding this comment

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

@hardingjam Thank you for implementing the changes! The tests now properly verify behavior in both light and dark modes. This provides complete coverage for the component's functionality.

(_/)
(•ᴗ•)
/ >👍


If you found this review helpful, would you consider giving us a shout-out on X?

Thank you for using CodeRabbit!

@hardingjam hardingjam requested a review from hardyjosh May 3, 2025 10:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
test test code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant