Currently, most of our tests are organized so that for each class under test, there is a test class, and that test class has nested classes for each method or property under test.
It would be better, I think, to not use nested classes and instead use namespaces for the same purpose. The hierarchy would have the same structure, but with a namespace instead of a class. There might be some cases where we have shared data at the test class level, which would need to be moved to a helper class or something like that.
This change is beneficial because we can split the test classes for each method into separate files, and because it might bypass the issue in #45. Or maybe not
Currently, most of our tests are organized so that for each class under test, there is a test class, and that test class has nested classes for each method or property under test.
It would be better, I think, to not use nested classes and instead use namespaces for the same purpose. The hierarchy would have the same structure, but with a namespace instead of a class. There might be some cases where we have shared data at the test class level, which would need to be moved to a helper class or something like that.
This change is beneficial because we can split the test classes for each method into separate files, and because it might bypass the issue in #45. Or maybe not