dotnet-installer/test/dotnet-test.UnitTests
Livar 208a0f31ec Merge pull request #1609 from livarcocc/dotnet_test_xunit_command
Dotnet test creating the command using dotnet-test-xunit
2016-02-27 15:03:14 -08:00
..
dotnet-test.UnitTests.xproj 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
DotnetTestMessageScenario.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
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 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
GivenATestDiscoveryStartMessageHandler.cs Making the reporing channel port discovery and accept incoming connections separate. Before we were hanging when creating the reporting channel and never starting the test runner. 2016-02-24 16:53:16 -08:00
GivenATestExecutionGetTestRunnerProcessStartInfoMessageHandler.cs Making the reporing channel port discovery and accept incoming connections separate. Before we were hanging when creating the reporting channel and never starting the test runner. 2016-02-24 16:53:16 -08:00
GivenATestRunner.cs Adding a new factory that creates the command as is, without adding the dotnet to it. We need it so that the runner can pass dotnet-test-xunit and get back the final corehost command, which is the right one for VS to use and attach to. 2016-02-26 14:34:23 -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
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
GivenThatWeWantToRunTests.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
project.json 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