JetBrains.ReSharper.UnitTestFramework

Returns current active session, regardless whether Unit-Test Sessions tool window has focus or even open.

Returns current active session, if and only if is called from within Unit-Test Sessions tool window.

Returns unit-test elements available in selection/under caret within current context. Context can be any tool window.

Returns unit-test tree in context, which can be either a session tree or the explorer.

Returns unit-tests selected in the corresponding unit-test tree. This takes into account any filter that might be applied to the tree.

Returns all unit-tests shown in the corresponding unit-test tree. This takes into account any filter that might be applied to the tree.

Returns describing criterion of in the without taking into account possible criterion of the tree itself, i.e. if the tree represents the session the resulting criterion will not include session's criterion.

Execute all visible unit tests from the current unit test tree. Available in both session and explorer trees. Relevant only for the unit test tool window. For now, it's Rider-only action.

Fake unit test element that can not be run, but can appear in UI, like in gutter menus, for example

Indicates whether it is possible to run the test-case without running other test-cases belonging to the same parent

Unique stable id of the element.

A Project to which the element belongs.

A specific target framework of the for which the element was created.

Provider that created the element.

A string that will be used in UI to present the element.

Gets namespaces for element. If element doesn't have namespace, return empty namespace.

Gets locations of test element.

Gets IProjectFile for element. If there is no, returns null. Should be as fast as possible, used from Unit Test Explorer in UI thread.

Gets IDeclaredElement for element. If there is no, returns null.

Short string describing element kind (test, container, etc.)

Gets list of categories defined on this element. Should not include any inherited categories.

Element's parent element.

Element's children elements.

Element short name, shouldn't be used for presentation.

Exploration type that created the element.

Merges property values from existing and discovered .

A newly discovered test element. An existing, i.e. persisted, test element having the same as the . Context in which the test element was discovered. A value indicating what kind of change was made.

Provides a way to specify merge logic for values of a property of , depending on .

Type implementing

Indicates that an element acts as a namespace. The only known example is NUnit's [SetUpFixture].

A marker interface for all entities that can appear on a gutter. Those include runnable elements and non-runnable elements that have a related runnable elements, e.g. abstract test classes.

Provides list of associated elements to be shown in Alt+Enter menu.

Id of test as generated by the test framework.

Salt to distinguish between elements with the same .

Indicates the source of an entity. The higher the value the more reliable the source is.

Indicates an entity created from source files.

Indicates an entity created based on an artifact.

Indicates an entity created as a result of running tests.

Indicates a dynamically created entity, e.g. tests that are only reported during execution

availability.

Completely unavailable, as if it was not present at all.

Temporarily unavailable, but may become available sometime.

Ready.

Provides format string to be used in action text.

Like , but doesn't has "Unit Tests" suffix or smth else. Leave null or empty to force use of

Used to start a process under profiler/dotmemory/debugger Used to attach to a process with profiler/dotmemory/debugger Created per Used to start a process under profiler/dotmemory/debugger Used to attach to a process with profiler/dotmemory/debugger

It makes sense only on Windows in situations when Mono is available. In this case, we can run .NET Framework tests on CLR or Mono

Optimization: Used to quickly calculate aggregating Status of the element when one of its children changes its status. Contains count of immediate children of an element by UnitTestStatus. Must be reset everytime the element it is calculated for changes.

ES: (HACK) Use this method to replace with a no-op implementation to avoid double-raising and events. Normally I would inject factory into .ctor with a single parameter of , but our IoC does not support it.

Returns the list of UT test adapter assemblies. Should work similar to Microsoft.VisualStudio.TestWindow.Controller.UnitTestExtensionDiscoverer.GetNugetAdapters

This component is trying to resolve the following problem in VS+R#: 1. User opens a .NET Core project with unit tests in VS+R#. 2. User suspends R#. 3. User resumes R#. 4. JetBrains.ReSharper.UnitTestFramework.DotNetCore.DotNetVsTest.DotNetVsTestArtifactExplorer.IsSupported checks that unit tests are supported in this project. It calls NuGetInstalledPackageChecker.IsPackageInstalled which calls NuGetSolutionManager.GetNuGetProject. Next, VsNuGetNetCorePackageReferenceProjectProvider should return the corresponding NuGetProject. However, if NugetModelOwner.NugetModel.IsAvailable is false, the null will be returned. R# will think that it's not an integrated project and that it has zero NuGet dependencies. Next, user will see a BrokenUnitTestElementGutterMark which says that tests can not be executed because we don't have dependencies on the test SDK and adapter. 5. After that NugetModelOwner.NugetModel.IsAvailable becomes true which fire VsNuGetNetCorePackageReferenceProjectProvider.Invalidated which fire NuGetSolutionManager.Invalidated. 6. Finally UnitTestNuGetInvalidator goes on stage. When NuGetSolutionManager.Invalidated, we are invalidating data for all projects in NuGetLockFileTracker and wait until all of the project are processed. 7. Next, UnitTestNuGetInvalidator calls Invalidate methods for IUnitTestArtifactExplorationProcess and IDaemon. 8. BrokenUnitTestElementGutterMarks are replaced by usual unit test gutter marks. 9. User is happy. See also: https://youtrack.jetbrains.com/issue/RSRP-475379

Filters out all type members that are neither method, field nor property

Extension point to add additional items to Unit Test Gutter Mark menu.

Project where tests are being created

Test framework to generate tests in

Path to test file to be created relative to the solution

Namespace to place tests in

Name of the test class to be created

File to be used

An implementation of to be used to generate test methods.

Aggregates of same and to be displayed as a single entry in selector.

Combined test framework name and version.

of this group. Same for all in the group.

Live list of all of the same and detected from different sources.

Describes why is shown, i.e. the project it was detected from or nuget feed it was downloaded from. Depends on currently selected .

Common logger for the entire generation workflow

Class for which tests are being generated

Method for which tests are being generated

Test generation method to be used

Unlike , this function chooses best suited from the given , from which it is possible to reference

Class in which tests are being generated.

Test framework for which tests are being generated.

Returns a task that completes when changes authored by previous steps are processed by project model and psi caches.

Convenience shortcut for creation references from multiple nuget packages.

Project from which the was extracted.

Navigates to a declaration while preserving caret location in the document, if it happens to be within the declaration already.

Test subject is evident when its type is used as generic parameter of the test class

Test subject cannot be extracted from the name of the test class using

Test subject cannot be extracted from the test class using any existing

Could have constructor with parameter ISolution or default constructor.

ID of provider

Provider's name

Replaces IsUnitTestElement, IsUnitTest, IsUnitTestContainer and IsUnitTestStuff methods with single one

Returns true, if given host provider could run tests in the given project

E.g. Nunit supports profiling in C#, but not DNX projects

Marker interface for injecting all unit-testing marshallers

Performed in hierarchical order from child to parent Performed in hierarchical order from parent to child Performed in undefined order

Sorts items in hierarchical order. The result includes all elements that were marked for deletion via explicit call to as well its descendants that should be deleted because cascade-delete is enabled.

Number of times UT.Events.Element.Updated was fired during commit

Total number of elements for which UT.Events.Element.Updated was fired at least once

When running tests, R# will invoke build and subsequent exploration, if necessary. This timeout specified how long test runner will wait for exploration to finish, before giving up and proceeded with tests it has.

Removes nodes from the by physically disconnecting them from the root, instead of removing elements corresponding to the selected nodes from the underlying and handling events raised for . The session is still modified, but the resulting events are suppressed.

Informs the that changes to and will be processes manually and that default change handlers should not be invoked.

Informs the to reject any incoming tasks. Only tasks being added on the same thread will be rejected.

Use this if you are about to perform an action which will modify and you know how to handle the changes faster than the default handler would. You must properly handle changes so that after the cookie is released the structure of tree MUST correspond to the actual . Make sure no unexpected changes to are made while you are holding the cookie. Optimization to prevent UI from evaluating children collection just to find out whether there is any. Node must have children if: - it is a grouping node (like namespace, category, etc), or - it contains more than one test element, or - it has exactly one element AND this element is not the same as the one our node was created for. The last is a valid scenario when parent of an element is not included in the tree explicitly. For example, when a user creates a session for a single test which has a parent.

Need to distinguish groups created by and

Whether can be moved under 'Uncategorized' node.

We can only move to 'Uncategorized' node if it is not in any other category node (including forced).