Unit testing || debugging windows form
Budget: $8 – $15 USD
1. Create a fork from the master branch of this GitHub repo: https://github.com/marcnoon/OpNode
1a. Try to keep your fork synched with my project so there are not too many merge conflicts.
2. Find the main form: public class pWord : System.Windows.Forms.Form
3. Create a MSTest class with Test Methods that test basic operations of this windows form using event in the context menu.
a. Such as when you right click on a node and click on "Add To".
b. Mimick that behavior in the MSTest Unit Test using Moq.
c. Use the test UnitTest_LeftRight_UserControl.cs as a guide to create unit tests for testing Add To, Edit, Insert, Copy, Attribute -> Add, Namespace -> Set Prefix, Namespace -> Set Suffix, continue all the way down to Export Node and Import Node. The test method should be there for all the basic operations.
d. If the test is nonfunctional or not currently working just make sure the test fails or is red.
e. if the test is functional and working as expected it should succeed and turn green for that test. The assertion or verify should pass.
e. I may create a new project to complete each test that fails and is non functional for the basic operations.
f. There is no pressure to make the tests all succeed and be functional, only all tests for the basic operations need to be completed and should be marked as to whether they fail or succeed. Should try to get at least one or more tests to succeed.
g. You may need to create a testable version of Windows form class: public class pWord : System.Windows.Forms.Form. To do this just create a new public class pWordTestable : pWord which is just a sub class of pWord and add any public methods or properties if there are any inaccessible properties or methods in pWord there are not accessible from the Unit Test test methods you create.
The worst-case scenario for me is you create a bunch of unit tests, and they all fail and are non-functional and I'll have to find someone else to make the tests functional and succeed. But this is the minimum amount of work required for me to sign off and complete this project.
The best-case scenario which would be amazing is if you can complete all the tests for basic operations which I mentioned above and that would make me very happy that this was completed successfully.
1a. Try to keep your fork synched with my project so there are not too many merge conflicts.
2. Find the main form: public class pWord : System.Windows.Forms.Form
3. Create a MSTest class with Test Methods that test basic operations of this windows form using event in the context menu.
a. Such as when you right click on a node and click on "Add To".
b. Mimick that behavior in the MSTest Unit Test using Moq.
c. Use the test UnitTest_LeftRight_UserControl.cs as a guide to create unit tests for testing Add To, Edit, Insert, Copy, Attribute -> Add, Namespace -> Set Prefix, Namespace -> Set Suffix, continue all the way down to Export Node and Import Node. The test method should be there for all the basic operations.
d. If the test is nonfunctional or not currently working just make sure the test fails or is red.
e. if the test is functional and working as expected it should succeed and turn green for that test. The assertion or verify should pass.
e. I may create a new project to complete each test that fails and is non functional for the basic operations.
f. There is no pressure to make the tests all succeed and be functional, only all tests for the basic operations need to be completed and should be marked as to whether they fail or succeed. Should try to get at least one or more tests to succeed.
g. You may need to create a testable version of Windows form class: public class pWord : System.Windows.Forms.Form. To do this just create a new public class pWordTestable : pWord which is just a sub class of pWord and add any public methods or properties if there are any inaccessible properties or methods in pWord there are not accessible from the Unit Test test methods you create.
The worst-case scenario for me is you create a bunch of unit tests, and they all fail and are non-functional and I'll have to find someone else to make the tests functional and succeed. But this is the minimum amount of work required for me to sign off and complete this project.
The best-case scenario which would be amazing is if you can complete all the tests for basic operations which I mentioned above and that would make me very happy that this was completed successfully.