Closed matt-inteltech closed 5 years ago
This is looking reasonable :-)
What I'm missing, though, are automated tests.
You introduced functionality (finding the proj/sln folder starting from the folder where a .cs/.vb file is located; determining the full path to a config file based on the findings) - but that is intermingled with other functionality.
Such intermingling is unnecessary. There is no real dependency on anything specific to VS extensions in the functionality. Hence it's fairly easy to extract the new functionality into functions/classes of its own - and explicitly test it.
Please add tests for the major green streak in https://github.com/robinsedlaczek/ForceFeedbackProgramming/pull/70/files#diff-3d656f2d20ff518fa5a5cee9a154cd11 Use NUnit or xUnit as your test framework. And add the tests using a new special test project alongside the production code projects.
ok
I understand this test as;
Is this right?
The whole extension is located inside a .sln file. To that .sln file just add a single test project (DLL) which uses NUnit or xUnit. And the test in that project should target the new functionality you added for this issue. Of course in a meaningful way.
I added new functionality and xUnitTest
Give me next work.
can i add 2 hours for xUnitTest?
So far I haven't seen any meaningful unit tests, sorry. Before we talk hours, please answer to my review questions by adding relevant tests.
ok
Please do not (!) add a solution for every test! Just 1 solution for all test is sufficient. Even a single class for all tests of a single class is sufficient.
I updated test.
Sorry, this is insufficient.
Your system-under-test is the Global
class. For its functionality you need to write tests.
can you give me good feedback in upwork? After you read this comment, I will delete.
I think it's better for us all to close this PR now. :)
…config file's path