Skip to content

Conversation

@jgebal
Copy link
Member

@jgebal jgebal commented Dec 29, 2019

Now the validation is executed at runtime, when the tests is executed.

This resolves issues related to the fact that some package constants may not exist or be valid at suite parse time.
In such scenario, the annotations continued to be ignored despite the fact that package constants were valid at test runtime.

With this change, tests can now have --throws annotations referencing constants that are undefined at compile time.
Resolves #1033
Resolves #721

Now the validation is executed at runtime, when the tests is executed.

This resolves issues related to the fact that some package constants may not exist or be valid at suite parse time.
In such scenario, the annotations continued to be ignored despite the fact that package constants were valid at test runtime.

With this change, tests can now have `--throws` annotations referencing constants that are undefined at compile time.
Resolves #1033
@jgebal jgebal merged commit 4dea559 into develop Jan 3, 2020
@jgebal jgebal deleted the bugfix/throws_exceptions_list_parsing branch January 3, 2020 05:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Invalid parameter value [constant_name] for "--%throws" annotation Move validation of throws annotation parameters to ut_executable_test

3 participants