test(frontend): add ConflictingFileModalContentComponent unit tests#5594
test(frontend): add ConflictingFileModalContentComponent unit tests#5594Roshan3580 wants to merge 1 commit into
Conversation
|
👋 Thanks for your first contribution to Texera, @Roshan3580! You can drive common housekeeping tasks just by leaving a comment. Type the command on its own line. On issues
To find unclaimed work, search Linking sub-issues
You can write references as On pull requests (author only)
You can mention teams as
For the full contribution flow, see CONTRIBUTING.md. |
|
@Roshan3580 please use our PR template. Please feel free to reopen once it is ready. Thanks! |
|
@Yicong-Huang I've updated the PR description to follow the Texera PR template. I don't appear to have permission to reopen the PR from my side. Could a maintainer please reopen it for review? Thank you. |
|
@Roshan3580, can you please make sure the template matches this layout: |
|
Hi @Roshan3580, the PR description is still not following our template. I'd be happy to reopen it once you update that. thanks. |
Purpose of the PR
Closes #5465
This PR adds frontend unit tests for
ConflictingFileModalContentComponentto improve test coverage and verify correct handling of injected modal data.Summary of Changes
conflicting-file-modal-content.component.spec.tsNZ_MODAL_DATApayloadDesign Proposal
N/A — this PR only adds unit tests for existing functionality and does not introduce behavioral changes.
Technical Design Diagram/Description
The tests validate that the component initializes correctly and that modal data provided through Angular dependency injection is exposed as expected by the component.
GIFs/Screenshots
N/A — test-only change.
Testing
Executed locally:
Both commands completed successfully.