-
Notifications
You must be signed in to change notification settings - Fork 0
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
Rule out test assemblies from versioning test sets #487
base: main
Are you sure you want to change the base?
Rule out test assemblies from versioning test sets #487
Conversation
For now handled via a hard-coded list of assembly names. Happy for this to be changed to something smarter. Open for ideas @adecler @pawelbaran
@adecler after doing this I had another thought. Could potentially make use of the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense in general, just one thought for an alternative: filtering by assembly method that would take:
- a collection of types/methods
- a collection of strings correspondent to assembly names
- bool ignore vs include
...could be helpful in other places as well. But just a thought, please feel free to ignore 😉
/**** Private Fields ****/ | ||
/***************************************************/ | ||
|
||
private static HashSet<string> m_testToolkitAssemblyNames = new HashSet<string> { "CodeComplianceTest_Engine", "CodeComplianceTest_oM", "InteroperabilityTest_Engine", "InteroperabilityTest_oM", "NUnit_Engine", "NUnit_oM", "Test_Engine", "TestRunner", "UnitTest_Engine", "UnitTest_oM" }; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would consider splitting the collection with line breaks for readability
Start of milestone changes for 8.1
These method are to following BHoM Compliance and have either been added to handle Different versions of revit, or should be removed. Either way, these methods should not be part of the general versioning
…nput to allow for ruling out specific adapter types
…enericImmutableDummyObjects Correctly set concrete generic type for immutable objects
…OrderReducedToWarning Reduce status from error to warning for attributes in order check
…omVersioningTestSets
NOTE: Depends on
Issues addressed by this PR
Closes #486
Explicitly rule out any type or method from a Test_Toolkit assembly from being included in test sets.
Test files
Ensure no test_Toolkit method is part of the included methods/types
GenerateLegacyDataset.zip
Changelog
Additional comments