Closed pawelbaran closed 1 year ago
Thanks @FraserGreenroyd for having a look.
Regarding the addition of RunTests
that takes a collection of strings, please note I kept the overload with a single assembly path input, but added the ability to specify classes to test. Hopefully this will not break the bot, and if it does, then happy to bring the original setup back.
When it comes to serialisation, the code on develop
struggles on deserialisation of collections in my cases, so I simply made it work. I have absolutely zero opinion on the design of the code here, my only need is to pass the information from XML to test result, so happy for you to take over the steering wheel. But probs best through it together - will schedule a call in the coming days 👍
I also don't like the changing of the XML Properties around
Settings
andProperties
I have reviewed this with @pawelbaran today and gone through some more tests, I now understand better why this change came in, and am happy with the change being made/kept as it does better support our workflows. Thanks @pawelbaran for being patient and working with me on this 😄
I think we are ready for re-review @FraserGreenroyd 👍
@BHoMBot check required
@FraserGreenroyd, there are some compliance checks failing, but none of the failures got introduced by this PR I think - are you fine with dispensating?
@FraserGreenroyd, there are some compliance checks failing, but none of the failures got introduced by this PR I think - are you fine with dispensating?
Ordinarily I would agree, however, the project-compliance failures are new following our change from C:/ProgramData
to $(ProgramData)
and are only being picked up on a PR by PR basis - you can use the bot to fix the project file and that should resolve those suitably.
For the documentation compliance - it is that you have an input attribute that doesn't match any input parameters (filePath
instead of the param filePaths
) so I would suggest we resolve that one.
@BHoMBot check project compliance
For the documentation compliance - it is that you have an input attribute that doesn't match any input parameters (
filePath
instead of the paramfilePaths
) so I would suggest we resolve that one.
Yeah ofc. Not sure how did I read the test results 🤦 Thanks @FraserGreenroyd
@BHoMBot check project-compliance
@BHoMBot fix project file ref. 13751724291
@BHoMBot check compliance
@BHoMBot check required
Issues addressed by this PR
Closes #435 Closes #436
Test files
To be added.
Changelog
Additional comments
Not ideal to mix bug + feature, but this is a result of a wider exploration. Happy to split into separate PRs before merging along with targeted test scripts being added.