[#213]: tests methods of MessageTypeDetails

[xieyuschen]

Notes for Reviewer

Pre-Review Checklist for the PR Author

1. Add sensible notes for the reviewer
2. PR title is short, expressive and meaningful
3. Relevant issues are linked in the References section
4. Every source code file has a copyright header with SPDX-License-Identifier: Apache-2.0 OR MIT
5. Branch follows the naming format (iox2-123-introduce-posix-ipc-example)
6. Commits messages are according to this guideline
   • Commit messages have the issue ID ([#123] Add posix ipc example)
   • [] Commit author matches Eclipse Contributor Agreement (and ECA is signed)
7. Tests follow the best practice for testing
8. Changelog updated in the unreleased section including API breaking changes
9. Assign PR to reviewer
10. All checks have passed (except task-list-completed)

Checklist for the PR Reviewer

• Commits are properly organized and messages are according to the guideline
• Unit tests have been written for new behavior
• Public API is documented
• PR title describes the changes

Post-review Checklist for the PR Author

1. All open points are addressed and tracked via issues

References

Updates #213

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 79.18%. Comparing base (ca22976) to head (88aba3d).
Report is 4 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #455      +/-   ##
==========================================
+ Coverage   78.94%   79.18%   +0.23%     
==========================================
  Files         196      196              
  Lines       23373    23540     +167     
==========================================
+ Hits        18451    18639     +188     
+ Misses       4922     4901      -21     

Files with missing lines	Coverage Δ
.../src/service/static_config/message_type_details.rs	100.00% <100.00%> (ø)
...yx2/src/service/static_config/messaging_pattern.rs	92.30% <100.00%> (+18.39%)	⬆️

... and 7 files with indirect coverage changes

[xieyuschen]

@elfenpiff @elBoberido i don't have the permission to assign the reviewer:( so at you directly

[elfenpiff]

Just split the one test case up into several ones and we are good to merge!

[xieyuschen]

Just split the one test case up into several ones and we are good to merge!

cheers! @elfenpiff

[orecham]

@xieyuschen Could you add [#213] to the commit message split the big test_is_compatible_to into small tests

Not sure why the preflight-check didn't catch this 🤔

[xieyuschen]

@xieyuschen Could you add [#213] to the commit message split the big test_is_compatible_to into small tests

Not sure why the preflight-check didn't catch this 🤔

done, thanks for reminding.

added on at 21:29: not sure why the pipeline failed so gamend and pushed it again to make the pipeline happy.

[xieyuschen]

@elfenpiff @orecham looks like the macos pipeline is a bit unstable and it failed to setup rust. The other pipelines passed.

[elfenpiff]

@xieyuschen again, thanks for the work you have done here.

[elfenpiff]

@xieyuschen The next iceoryx community meetup is online on the 5th of November: https://github.com/eclipse-iceoryx/iceoryx/wiki/2024-11-05-Eclipse-iceoryx-developer-meetup

It would be nice to get to know you there. I know it is still a while, but you already committed some great contributions so it would be a pleasure to get to know you in person if you like. Also we could discuss if you would be interested in driving a feature from our roadmap - something that might interest you or you always wanted to try.

Great to have you on board!

[xieyuschen]

@xieyuschen The next iceoryx community meetup is online on the 5th of November: https://github.com/eclipse-iceoryx/iceoryx/wiki/2024-11-05-Eclipse-iceoryx-developer-meetup

It would be nice to get to know you there. I know it is still a while, but you already committed some great contributions so it would be a pleasure to get to know you in person if you like. Also we could discuss if you would be interested in driving a feature from our roadmap - something that might interest you or you always wanted to try.

Great to have you on board!

cool, I'm looking forward to meeting you guys in the meeting and learning more about future plans.