Unit Tests for a Windows Form using Treenodes

This is a very complex project and requires a person with substantial knowledge of Windows Forms and MSTests and Events and Mocking Events and methods in order to be successful.

Create manual tests for a Windows Forms app to Mock event behavior on the main Windows form for manipulating and changing nodes or node behavior.

Ensure all basic operations are unit-teste on the UI. Follow sa imilar pattern used with the LeftRight control unit tests.

Create a new unit test class and methods under the class using MSTests.

You will only make classes and mocks in unit tests to test and validate or assert behavior of Treenode which is alot like a Linked List. This Treenode is the base class of pNode which has additional properties.

Mock adding a new UI using the events, context menu events. Note: all logic working with nodes will eventually be in the pWordLib library. This project is the step before moving all logic to the pWordLib. It tests the functionality of all the events used in the main pWord Windows Form and establishes a baseline of testing before the pWordLib library is touched. Updating the pWordLib is another project down the road.

What is NOT in this project: If it saves a file that should stay in the Windows Forms c# code for now and no Unit Tests are needed, or if it Serializes or Deserializes from a file that should also stay within the form c# code. Eventually, a File library will be utilized to save stuff to and from a file, export to and from a file, or import to and from a file. A separate project will be devised to handle that aspect of this project.

Also, there are no changes to anything but the Unit Tests in this project. Do not change anything in the main project. Others may make minor changes in the main project; your code is expected to keep up, and please ask questions if needed.
What this project entails is this: *Testing* the following behavior: Adding, nodes, deleting nodes, adding attributes, deleting attributes, adding namespaces, deleting namespaces, adding operations, and deleting operations. Adding namespace prefixes, deleting namespace prefixes, adding namespace suffixes, removing namespace suffixes.

However, you can also test the library part to make sure the node portion is also working correctly but do not change the library in any way. Eventually, all TreeNode or pNode operations will be moved into the pWordLibrary.

When the Form first loads the first time it always starts on the very first master node and the first node in unexpanded mode. To test, you would have a start test button that initializes the tests. Also, add the mode using #ifdef Debug #endif precompiler directives if possible for testing purposes can be utilized.

The main form also includes two text boxes and a button to add content on certain nodes or in certain nodes. That is part of the unit testing for this project

The GitHub website is open source. All changes should be made on https://github.com/marcnoon/OpNode on the master node on your own feature branch based on this master or main node. You will commit your changes to the OpNode branch once your work is completed.

Do not add any new dlls or nuget packages.

Rename unit tests to match the functionality being tests. In this case something to do with testing behavior of the windows Forms app dealing with TreeNode or pNodes.