Thank you Freyo for this explanation & step-by-step instructions. I could follow till point # 7. After that I am lost. 1). Point # 8 mentions "Copy the test suite apk into MyRepository/testcases." Where is this test suite apk located? 2). How do I generate the AndroidTest.apk file. 3). Where do I get the host_config.xml file from? Thank you in advance. Angie.

I got HTTP status 406 even with explicit Accept header like this: curl -x localhost:8088 -H 'Accept: application/jso... The root cause was that I forgot to include Jackson JSON lib in the dependencies. Solution: add this to pom.xml <dependency> <groupId>org.codehaus.jackson</gr...

You can use the runOrder parameter to control the test execution order for Maven surefire tests: <build> <plugins> <plugin> ... Other options are: Option Meaning alphabetical Alphabetical reversealphabetical Reverse Alphabetical random Randomized hourly alphabetical on even hours, reverse alphabetical on odd hours failedfirst Failed first will run tests that failed on previous run first, as well as new tests for this run. balanced Balanced is only relevant with parallel=classes, and will try to optimize the run-order of the tests to make all tests complete at the same time, reducing the overall execution time. filesystem This is the default. I guess this is the order returned by the file system: uncontrolled but deterministic.

Junit does not support specifying execution order of tests until 4.11. The methods were simply invoked in the order returned by the reflection API. So, the tests are executed in a unspecified but deterministic order, i.e., you have no control over the order of execution, but if you repeat the tests, they are run in the same sequence each time. For version 4.11, you can specify the order with the FixMethodOrder annotation: import org.junit.runners.MethodSorters; imp... From the release notes : Test execution order By design, JUnit does not specify the execution order of test method invocations. Until now, the methods were simply invoked in the order returned by the reflection API. However, using the JVM order is unwise since the Java platform does not specify...

This snippet sets system properties from Maven surefire test plugin. This is useful when you want to set logging (for example, log4j) properties based on Maven project properties. Example that sets system property testlog.dir : <plugins> <plugin> <groupId>org.apach... Example log4j.xml that uses system property testlog.dir : <?xml version="1.0" encoding="UTF-8"?> <!DOCTYP...

This is a Maven POM that prints out some built-in project properties: <project xmlns="http://maven.apache.org/PO... Output: $ mvn validate [INFO] Scanning for projects.....

First, the test command that sleeps random number of seconds ( sleeper.sh ): #!/bin/bash stime=$[$RANDOM % 20] sleep $sti... As comparison, synchronous pipe code: #include <sys/wait.h> #include <stdio.h> #in... Asynchronous pipe code: #include <sys/wait.h> #include <stdio.h> #in...

test

Here is a list of the most useful targets that the GNU Coding Standards specify (from automake manual ). make all Build programs, libraries, documentation, etc. (same as make). make install Install what needs to be installed, copying the files from the package's tree to system-wide directories. make install-strip Same as make install, then strip debugging symbols. Some users like to trade space for useful bug reports... make uninstall The opposite of make install: erase the installed files. (This needs to be run from the same build tree that was installed.) make clean Erase from the build tree the files built by make all. make distclean Additionally erase anything ./configure created. make check Run the test suite, if any. make installcheck Check the installed programs...

From bind man page: SYNOPSIS #include <sys/types.h> ... The bind call assigns an address and a port to a socket. That's it. There's no mention of client or server, so it can be used on a client socket or a server socket. But it's necessary for a server socket, otherwise clients do not know how to contact the server. For a client socket, the call is optional. When a client connects to a server or sends a message for the first time, a dynamic port is assigned to the client if there's no port assigned to it. If a port is bind beforehand, there's no dynamic assignment. Test code: int print_sock_info(int sockfd) { struct so... Prints: Local addr: 0.0.0.0, port: 0 Local addr: 0.0.0....