Skip to content

1049010: Fixed bunit test case failure in release mode. - #40

Closed
Yokesh-SF4393 wants to merge 5 commits into
mainfrom
1049010-bunit
Closed

1049010: Fixed bunit test case failure in release mode.#40
Yokesh-SF4393 wants to merge 5 commits into
mainfrom
1049010-bunit

Conversation

@Yokesh-SF4393

Copy link
Copy Markdown
Collaborator

Bug description

Two BUnit tests fail only in Release builds because chart rendering does not fully reflect updated axis/gridline settings.

Root cause

The renderer uses a cached gridline width value that is not refreshed after certain parameter updates in Release mode.

Solution description

Updated the renderer to read the gridline width directly from the current axis configuration instead of using the cached value.

Code Studio usage(Mandatory)

  • Code Studio used in this PR/MR?

    • Yes
    • No
  • If Yes: Primary use (choose one)

    • Generate new code
    • Refactor/improve existing code
    • Tests
    • Bug fix / debugging help
    • Docs / comments
    • Review assistance (explanations/summaries)
    • Other:
  • Outcome

    • Saved time
    • Neutral
    • Cost time
  • If “Cost time” explain in short (1 or 2 lines):

Impact assessment

  • Low - Affects a single feature with minimal user impact
  • Medium - Affects multiple features or has moderate user impact
  • High - Critical functionality or significant user impact

Reason for not identifying earlier

Provide the reason for not identifying the bug earlier.

Areas tested against this fix

Breaking changes

  • Yes (Tag breaking-issue)
  • No

If yes, provide breaking commit details link and migration guidance.

Regression testing

  • Verified fix doesn't reintroduce previous bugs
  • Checked edge cases and error scenarios

Action taken to prevent recurrence

  • Added/updated unit tests
  • Other (specify): _________________
  • NA

Automation status

  • BUnit (provide PR link: _________________)
  • Playwight (provide PR link: _________________)
  • NA

Cross-platform verification

  • Blazor Server
  • Blazor WASM
  • NA

Related issues

Is this issue present in EJ2 or other components?

  • Resolved in EJ2 (PR link: _________________)
  • Created task for EJ2 (Task link: _________________)
  • Needs attention in other components (tag needs-attention-coreteam)
  • NA

Output screenshots

Post the output screenshots if a UI is affected or added due to this bug.

API changes

  • New API added (API Review task link: _________________)
  • Existing API renamed/modified (API Review task link: _________________)
  • No API changes

Performance verification

  • Verified no memory leaks introduced
  • Verified no performance degradation
  • Not applicable

Reviewer Checklist

  • Reviewed the provided Code Studio usages related information.
  • Code changes follow component guidelines
  • All provided information reviewed and verified
  • Solution addresses the root cause effectively

Base automatically changed from warnings-accessibility to main August 24, 2026 13:15
@Yokesh-SF4393

Copy link
Copy Markdown
Collaborator Author

#44

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.

3 participants