As indicated in the question title, what is the best way to pre-test modules in an application that behaves differently depending on which user is currently logged in?
Also, for applications that support internal state information, what is the best way to perform testing and manage all tests?
If you mean a system user, for example. windows login - then for unit testing it is best to separate your code from this dependency.
, , . , .
(, , , , , , .. - ), . , .
( ). , , , , .
, () .
, - , , " " " , ".
, , .
, .
: , . .
, unit test .
, , , [ n ; n - ].
, [ n * m; n - , m - ].
Source: https://habr.com/ru/post/1706383/More articles:Ado.Net Entity: Object does not display related members (foreign keys) - c #How do you handle the event raised in your class inside your own class? - event-handlingWCF array serialization - xmlHow to protect against password attacks without forwarding? - passwordsWPF rendering is ugly and blurry in Vista - windows-xpC # Help convert this code from VB.NET to C # - c #Can you send a fax through ASP.NET without proprietary software? - vb.netWhere can I find the double dollar syntax link? - syntaxSending a fax using .NET. - c #How to set host name on G1 phone - androidAll Articles