Logical error conditions

[cspray]

It is possible that you could wind up setting up Attributes or a configuration in such a way that errors or unrecoverable ambiguities could occur. This is a list of those possibilities so that in future version we can check for them and handle them appropriately. This list will continue to be updated until the project is ready to address this kind of static analysis.

• Multiple #[DefaultTestSuite] are defined. By definition you can only have 1 default TestSuite. If multiple implementations are defined as default an error should be thrown during compilation.
• A #[TestSuite] is defined on a TestCase that does not exist. This should result in an error during compilation.
• A #[TestSuite] is defined on a TestCase that does not extend TestSuite. This should result in an error during compilation.
• A #[DataProvider] is defined on a method that is not also a #[Test]. This should result in an error during compilation.
• A #[DataProvider] defines a method that cannot be invoked on the TestCase. This should preferably throw an error during compilation but could resort to runtime error if difficult to achieve.
• A #[Test] could be specified on a protected or static method. This should result in an error during compilation.
• An element from a #[DataProvider] method might not return an array with the correct format or the incorrect number of elements. The test for this data set should result in a failure.