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
SecTester for .NET is not tied to any specific test runner or testing framework, but we aim to make writing tests easier for everyone using the built-in .NET test runner capabilities.
To achieve this, we plan to provide extensions for popular test frameworks such as xUnit, NUnit, and MSTest, which will include base classes to allow the reuse of SecRunner between tests for better performance and isolation between tests.
Additionally, we will address the output issue (i.e. #145) that currently prevents us from displaying messages in the standard output.
SecTester for .NET is not tied to any specific test runner or testing framework, but we aim to make writing tests easier for everyone using the built-in .NET test runner capabilities.
To achieve this, we plan to provide extensions for popular test frameworks such as xUnit, NUnit, and MSTest, which will include base classes to allow the reuse of
SecRunner
between tests for better performance and isolation between tests.Additionally, we will address the output issue (i.e. #145) that currently prevents us from displaying messages in the standard output.
The text was updated successfully, but these errors were encountered: