tdl-client-dotnet
Project contains submodules as mentioned in the .gitmodules
file:
- broker
- tdl/client-spec (gets cloned into features)
- wiremock
Use the below command to update the submodules of the project:
git submodule update --init
Dotnet client to connect to the central kata server.
nuget restore tdl.sln
Need to run the below commands:
msbuild tdl.sln /p:buildmode=debug /p:TargetFrameworkVersion=v4.5
msbuild tdl.sln /p:buildmode=debug /p:TargetFrameworkVersion=v4.5 # <=== second time
Yes need to run that command twice in order to have a successful build.
All test require the ActiveMQ broker to be started. The following commands are available for the broker.
python ./broker/activemq-wrapper.py start
python wiremock/wiremock-wrapper.py start 41375
python wiremock/wiremock-wrapper.py start 8222
Start and stop the wiremocks and broker services with the below:
./startExternalDependencies.sh
./stopExternalDependencies.sh
mono ./packages/NUnit.ConsoleRunner.3.8.0/tools/nunit3-console.exe \
--result=test-report.xml \
./test/specs/bin/Debug/TDL.Test.Specs.dll
Stop external dependencies
python ./broker/activemq-wrapper.py stop
python wiremock/wiremock-wrapper.py stop 41375
python wiremock/wiremock-wrapper.py stop 8222
or run the below script
./stopExternalDependencies.sh
Run
./release.sh
- I had to place FSharp.Core into the GAC
For some reasons, mono was not finding FSharp.Core.dll.
I have used gacutils
to add the library into the General Assembly Cache.
- SpecFlow generateAll task fails with
msbuild
When you first run msbuild tdl.sln
the SpecFlow task will fail. The .cs files are still generated correctly but the results is not reported back to msbuild.
This means that you have to run msbuild tdl.sln
twice.
- RestSharp sometimes return a status code of 0
One test always fails on OSX with Mono. RestSharp fails to read the request body correctly. The same test passess on the CI system. The test seems to be related to the fact that we have received an errorStatus code with a body.