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 don't use the nunit.analyzers.integrationtests and nunit.analyzers.playground projects, so I think we should remove them (nunit.analyzers.integrationtests are not even part of the solution).
The only things that perhaps should be moved from integrationtests are tests of functionality when we use "using static directive" (using static NUnit.Framework.Assert;) or aliasing (using NF = NUnit.Framework;). Also integrationtests have tests of optional parameters and params that we might lack in the tests project.
The text was updated successfully, but these errors were encountered:
Currently, we don't use the
nunit.analyzers.integrationtests
andnunit.analyzers.playground
projects, so I think we should remove them (nunit.analyzers.integrationtests
are not even part of the solution).The only things that perhaps should be moved from integrationtests are tests of functionality when we use "using static directive" (
using static NUnit.Framework.Assert;
) or aliasing (using NF = NUnit.Framework;
). Also integrationtests have tests of optional parameters and params that we might lack in the tests project.The text was updated successfully, but these errors were encountered: