mirrors/dotnet-installer
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
dotnet-installer/test/dotnet-test.UnitTests
History
Andrew Stanton-Nurse ef0ca39da1 Memory usage improvements in build (#2626) 
* Use a WorkspaceContext in dotnet-build to cache project data across
multiple compilations in a single build action
* Dramatically reduce string and object duplication by introducing a
"Symbol Table" that shares instances of NuGetVersion, NuGetFramework,
VersionRange and string across multiple lock-file parses

Test Results:
* Testing was done by compiling Microsoft.AspNetCore.Mvc (and it's
dependencies) and taking memory snapshots after each compilation in
dotMemory
* We used to allocate ~3MB and deallocate ~2.5MB on EACH compilation in
a single build action. This has been reduced to ~120KB
allocated/deallocated
* After introducing WorkspaceContext, total memory usage spiked from 6MB
across the whole build action to about 13MB, introducing the symbol
table dropped it back to about 5-6MB.
2016-04-22 15:01:56 -07:00
..
dotnet-test.UnitTests.xproj Revert "Update the .xproj files to reference the "DotNet" targets and props instead of "DNX"." 2016-03-16 11:44:09 -05:00
DotnetTestMessageScenario.cs Modified the protocol to send a the list of tests to run and to invoke the test runner with the wait command flag so that the runner waits for this list. 2016-03-04 17:14:56 -08:00
GivenADiscoverTestsArgumentsBuilder.cs Adding unit tests for the state machine of dotnet test. Starting the implementation of a state machine in dotnet test. Right now we only handle the TestSession:Terminate message. 2016-02-23 11:20:04 -08:00
GivenADotnetTestApp.cs Adding unit tests for the state machine of dotnet test. Starting the implementation of a state machine in dotnet test. Right now we only handle the TestSession:Terminate message. 2016-02-23 11:20:04 -08:00
GivenARunTestsArgumentsBuilder.cs Modified the protocol to send a the list of tests to run and to invoke the test runner with the wait command flag so that the runner waits for this list. 2016-03-04 17:14:56 -08:00
GivenATestCommand.cs t Convert Test Assets to Microsoft.NETCore.App 2016-04-19 11:08:27 -07:00
GivenATestDiscoveryStartMessageHandler.cs Modifying the reporting channels to make the AdapterChannel a client and leave the TestRunnerChannel a server. This will prevent port conflicts between dotnet test and the Adapter (VS) due to race conditions. 2016-03-15 15:13:54 -07:00
GivenATestExecutionGetTestRunnerProcessStartInfoMessageHandler.cs Modifying the reporting channels to make the AdapterChannel a client and leave the TestRunnerChannel a server. This will prevent port conflicts between dotnet test and the Adapter (VS) due to race conditions. 2016-03-15 15:13:54 -07:00
GivenATestRunner.cs We had a bug where the framework for design time runs of dotnet test was hard coded into dnxcore50. Moved some things around so that we will pack the target framework from the project context. 2016-03-02 22:15:02 -08:00
GivenATestRunnerTestCompletedMessageHandler.cs Adding unit tests for the state machine of dotnet test. Starting the implementation of a state machine in dotnet test. Right now we only handle the TestSession:Terminate message. 2016-02-23 11:20:04 -08:00
GivenATestRunnerTestFoundMessageHandler.cs Adding unit tests for the state machine of dotnet test. Starting the implementation of a state machine in dotnet test. Right now we only handle the TestSession:Terminate message. 2016-02-23 11:20:04 -08:00
GivenATestRunnerTestResultMessageHandler.cs Adding unit tests for the state machine of dotnet test. Starting the implementation of a state machine in dotnet test. Right now we only handle the TestSession:Terminate message. 2016-02-23 11:20:04 -08:00
GivenATestRunnerTestStartedMessageHandler.cs Test Runner test started needs to handle messages when dotnet test is in a TestStarted state, as we will receive multiple test started messages. Also, to prevent a crash, when we get a message that terminates the adapter or the runner, we need to stop listening. Unfortunately, this needs to be directly where we read the messages, because if we give a handler a chance to handle that message, the reader will already be trying to read again. 2016-02-25 17:36:13 -08:00
GivenATestRunnerWaitingCommandMessageHandler.cs Modified the protocol to send a the list of tests to run and to invoke the test runner with the wait command flag so that the runner waits for this list. 2016-03-04 17:14:56 -08:00
GivenATestSessionTerminateMessageHandler.cs Adding unit tests for the state machine of dotnet test. Starting the implementation of a state machine in dotnet test. Right now we only handle the TestSession:Terminate message. 2016-02-23 11:20:04 -08:00
GivenAUnknownMessageHandler.cs Adding unit tests for the state machine of dotnet test. Starting the implementation of a state machine in dotnet test. Right now we only handle the TestSession:Terminate message. 2016-02-23 11:20:04 -08:00
GivenAVersionCheckMessageHandler.cs Adding unit tests for the state machine of dotnet test. Starting the implementation of a state machine in dotnet test. Right now we only handle the TestSession:Terminate message. 2016-02-23 11:20:04 -08:00
GivenThatWeWantToDiscoverTests.cs Adding unit tests for the state machine of dotnet test. Starting the implementation of a state machine in dotnet test. Right now we only handle the TestSession:Terminate message. 2016-02-23 11:20:04 -08:00
GivenThatWeWantToParseArgumentsForDotnetTest.cs t Convert Test Assets to Microsoft.NETCore.App 2016-04-19 11:08:27 -07:00
GivenThatWeWantToRunTests.cs Modified the protocol to send a the list of tests to run and to invoke the test runner with the wait command flag so that the runner waits for this list. 2016-03-04 17:14:56 -08:00
project.json Memory usage improvements in build (#2626) 2016-04-22 15:01:56 -07:00