This basically is a bunch of C# components that call directly the tests inside UI_Test.dll. Since those return a TestResult it is easy to do a few explodes to get exactly the data you want out of it.
no issue raised yet but given the errors we get from the TestResults, it is pretty clear they are mainly due to one issue with ref/out parameters not being handle properly on all levels:
Expression of type 'Microsoft.CodeAnalysis.SyntaxTokenList' cannot be used for return type 'System.Object'
Expression of type 'Microsoft.CodeAnalysis.SyntaxTriviaList' cannot be used for return type 'System.Object'
The type 'BH.oM.Base.IFragment&' may not be used as a type argument.
The type 'BH.oM.Graphics.RenderMesh&' may not be used as a type argument.
The type 'System.Collections.Generic.List`1[BH.oM.UI.ParamInfo]&' may not be used as a type argument.
The type 'System.Double&' may not be used as a type argument.
The type 'System.Guid&' may not be used as a type argument.
The type 'System.Int32&' may not be used as a type argument.
The type 'System.Management.Automation.WildcardPattern&' may not be used as a type argument.
The type 'System.String&' may not be used as a type argument.
The type 'System.Text.RegularExpressions.Regex&' may not be used as a type argument.
(not too sure what's going on with first two though). I will look into those next week but this is proof that those tests are doing their job. So I am happy with this PR 😄
Issues addressed by this PR
Closes #363
As per title. also mirror the changes that were made on the script testing BHoM_UI
Test files
You can simply call
.\TestRunner.exe UI
but I find there is still a few too many errors for this to be easily readable at the moment. So I used this as well: https://burohappold.sharepoint.com/:u:/r/sites/BHoM/02_Current/12_Scripts/02_Pull%20Request/BHoM/BHoM_UI/CICD-%23363-AlignToTestToolkitChanges/TestRunner_UI.gh?csf=1&web=1&e=yRqvAlThis basically is a bunch of C# components that call directly the tests inside UI_Test.dll. Since those return a
TestResult
it is easy to do a few explodes to get exactly the data you want out of it.Additional comments
Right now, here's the errors that I have.
SetItem
Issue was already raised for those
Copy (without items from above)
Issue was already raised for that one too
Run (without items from above)
no issue raised yet but given the errors we get from the TestResults, it is pretty clear they are mainly due to one issue with ref/out parameters not being handle properly on all levels:
(not too sure what's going on with first two though). I will look into those next week but this is proof that those tests are doing their job. So I am happy with this PR 😄