Modified unit tests to use Unittest tester

[caleb-sitton-inl]

---

Pull Request Description

What issue does this change request address? (Use "#" before the issue to link it, i.e., #42.)

What are the significant changes in functionality due to this change request?

This updates the unit tests in FORCE to use the new Unittest tester that was added in RAVEN.

---

For Change Control Board: Change Request Review

The following review must be completed by an authorized member of the Change Control Board.

• 1. Review all computer code.
• 2. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details.
• 3. Automated Tests should pass, including run_tests, pylint, and manual building tests.
• 4. If significant functionality is added, there must be tests added to check this. Tests should cover all possible options. Multiple short tests are preferred over one large test.
• 5. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change. The requirements and the requirements test shall be in sync.
• 6. The merge request must reference an issue. If the issue is closed, the issue close checklist shall be done.

[caleb-sitton-inl]

The unit tests are not being run, probably because the submodule of RAVEN does not include the Unittest tester. I believe this should be solved when the next version of RAVEN is released and includes the Unittest tester.

[dylanjm]

Changes are good to merge.

[dylanjm]

@caleb-sitton-inl I think we can update the RAVEN submodule here in FORCE to get the changes into our repo.