Xcode 4 Unit Testing using Command Line - iphone

Xcode 4 supports running unit tests using the test build option, however I can't find a way to run the tests through the command line.
Simply running xcodebuild on the Unit Tests target does not run the tests (I have the run after build option turned on).
Any ideas?

I wasn't able to find any such option. The closest I have gotten so far is the ability to run logic tests only (running xcode 4 unit tests from the command line) and that's not very satisfying. I'll update my answer in Xcode 4: Run tests from the command line (xcodebuild)? if I find a better solution.

Related

Jodconverter: Fails randomly when running tests with libreoffice (docker)

While running conversions in test suites using jodconverter, it was randomly crashing and tests failed.
We are using Libreoffice with jodconverter running tests in docker. Took too much time to figure this out, so created this question.
Solution :
Use -PuseLibreOffice with the test command to signal jodconverter to use libs for libreoffice. Default is open office.
./gradlew test -PuseLibreOffice

How to run only xUnit tests with specific name through console/powershell?

I am currently running tests through Visual Studio interface, and that provides easy option to run only certain test. I want to do same, but through console / powershell.
Right now if I do dotnet test that will run all discovered tests. Is it possible to do something similar like dotnet test MyTest which would only run specific test?
Command dotnet test has switch --filter that allows you to filter tests and get only those that you want to run. So you can do:
dotnet test -t
To see full list of tests available, and then in order to just run specific ones you can do:
dotnet test --filter "FullyQualifiedName~ShouldInterconnect"
Which will execute only the tests containing ShouldInterconnect in the name.

Can't run specific test specs based on namespace using sbt at the shell

I'm trying to run my specs2 tests from the shell as part of my CI build. When I run the following command on my local windows machine it runs the appropriate specs: specs defined in the Unit namespace.
sbt test:compile "test-only Unit.*"
However, on my build machine (ubuntu) it appears to ignore the namespace parameter to test-only and as a result runs all the tests. Single quotes don't seem to make a difference. When I enter the sbt console and then execute the command (test-only Unit.*) it works as expected.
Any suggestions would be appreciated.

How to show the xcodebuild command line from xcode?

I'm trying to build a working simulator build from xcodebuild. Compilation works but the final product won't run on the simulator when installed via WaxSim. If I build through the Xcode GUI then the final product installs without issue from WaxSim.
My question is, how can I see the exact xcodebuild command line that xcode is using to build a working simulator build. I just need to copy that into my shell script but it's proving elusive. I did a find in the build logs from xcode but there's no mention of xcodebuild there.
You can't. Xcode itself doesn't invoke xcodebuild during the build process. This post has more information on executing xcodebuild to build for the simulator.

How to further automate Teamcity

I have successfully configured my project for build in TeamCity. Going a step more, I want to run a deployment script once a build completes successfully. The deployment script is a simple bash command. To make the question more simpler, how would I invoke a shell command once a build successfully completes in Teamcity.
Please help
TeamCity 6.0 has a new feature called Multiple Build Steps:
Multiple Build Steps: Now any build configuration can be comprised of unlimited number of build steps, where each step is represented by a build runner. Don’t limit yourself, and combine as many build runners into one configuration as you need. Feel free to call a NAnt script before compiling VS solutions, run inspections and duplicates finder after your ANT build, add NUnit tests after your Rake build, and so on.
So you can add a new build step with the command line runner which will execute your shell script.