Skip to content

Conversation

@TimMurphy
Copy link

πŸ€” What's changed?

New dependency plugin design.

⚑️ What's your motivation?

Implements


🏷️ What kind of change is this?

  • πŸ’₯ Breaking change (incompatible changes to the API)

πŸ“‹ Checklist:

  • I've changed the behaviour of the code
    • I have added/updated tests to cover my changes.
  • My change requires a change to the documentation.
    • I have updated the documentation accordingly.
  • Users should know about my change
    • I have added an entry to the "[vNext]" section of the CHANGELOG, linking to this pull request & included my GitHub handle to the release contributors list.

Refactored the `TestFormatter` class to use inline constructor syntax, simplifying the code by removing the separate constructor definition.

Updated the `ConsumedMessages` property to use the shorthand `[]` for initializing an empty list, improving code readability and conciseness.
@TimMurphy
Copy link
Author

Progress report

  • Successfully created fork and branch new-dependency-plugin-design
  • Built the project without issue in Visual Studio and dotnet build
  • Corrected to build warnings. Simple sytax change, no change in functionality

Tests

Started running tests in Visual Studio. Running all tests is time consuming :-) Aborted testing in Visual Studio to run them from the command line. Tests have been running for approximately 5 minutes now.

My goal is the get all tests passing before I start implementation. I'll attempt to acheive this over the weekend.

@gasparnagy
Copy link
Contributor

Test execution gets slightly faster for the second run due to some caching. Do not run the "specs" tests locally - those are generally redundant and legacy. The others run for a few minutes for me after the caches are in place.

Updated the `RuntimePluginLocatorTests` to explicitly order the
`foundPlugins` collection alphabetically using `.OrderBy(p => p)`.
Reordered the expected plugin list to match the new ordering logic.

These changes improve debugging if the test fails.
Updated the list of expected plugin DLLs in the `RuntimePluginLocatorTests` test file to include new generator-related plugins:
- Added `Reqnroll.MSTest.Generator.ReqnrollPlugin.dll`
- Added `Reqnroll.NUnit.Generator.ReqnrollPlugin.dll`

These changes reflect the introduction of generator plugins and ensure the test expectations align with the updated plugin structure.
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.

2 participants