Documentation and refactoring for plugins and wrong code coverage – part 12
I realized that will be no documentation for plugins – until I create one .
Figured also that each plugin should have a name -to understand from where he grabs data – so some code involved code.
Asking when and if the plugins are copied to the application – not found yet an answer…
Now the user can choose what bank he wants to see data ? We could do this for the console application – and I think that is the moment to play with Icaza Gui Terminal https://github.com/migueldeicaza/gui.cs – Created buttons to display plugins (NBR and ECB ). Will not work if many plugins will come – but it is ok for the moment.
Discovered the window for code coverage – read https://github.com/tonerdo/coverlet/blob/master/Documentation/VSTestIntegration.md
Some error when writing the .runsettings file – discovered from command line ( GUI does not show)
Reading the docs , https://docs.microsoft.com/en-us/visualstudio/test/using-code-coverage-to-determine-how-much-code-is-being-tested?view=vs-2019#analyze-code-coverage , it says that is not available for community…
Back to square 1 after 1 hour- just made documentation.
Infovalutar
And one hour passes...(This is the result of 1 hour per day auto-challenge as a full cycle developer for an exchange rates application)
( You can see the sources at https://github.com/ignatandrei/InfoValutar/ )
Leave a Reply