You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we log that a test failed, but don't log the exception. This is problematic if you're running the tests in an environment where the exception isn't captured and logged (E.G. AzureDevops will automatically log exceptions to a build or release log.) Might be worth it to log the exception before throwing.
Logging to-do's:
Log test case exceptions instead of just throwing
Make sure logging from ExecuteTestCase is at a uniform level (prefer Debug as much as possible)
Update logging around serializing JSON
The text was updated successfully, but these errors were encountered:
Also need to update how test block inputs and outputs are logged. Noticed at a client that one is as Info one is as Debug. Probably want most or all "automatic" logging to go to Debug outside of errors and maybe the test case name.
Also need better messaging around when an item can't be serialized to JSON. E.G. if we don't have a [JsonIgnore] property on a property that mucks around with Selenium before the site is launched, it will fail with a selenium exception. Need to gracefully log instead.
Currently we log that a test failed, but don't log the exception. This is problematic if you're running the tests in an environment where the exception isn't captured and logged (E.G. AzureDevops will automatically log exceptions to a build or release log.) Might be worth it to log the exception before throwing.
Logging to-do's:
The text was updated successfully, but these errors were encountered: