When writing tests using the Java API, it would be nice to let Moco choose a port that is free on the OS and then provide a mechanism for querying that port. This would make tests written using Moco more robust when run on different environments.

I think it would be useful for Moco to allow multiple config files to be loaded into a single instance, each with a different namespace.

This would avoid needing to spin up multiple instances of Moco when you want to run a few different stubs at the same time (for example during a build pipeline).

Here's a rough example of how this could work:

Runner runner = new NamespacedRunner(8080);
runner.addConfig("myApp1", "/path/to/myConfig1.json");
runner.addConfig("myApp2", "/path/to/myConfig2.json");
runner.run()

After doing this, the matchers in myConfig1.json will all be implicitly prepended with the path myApp1.

E.g if myConfig1.json defines a matcher to catch all GET requests, it will catch requests to localhost:8080/myApp1**, but not localhost:8080/somethingElse.

Do you agree that this would be a useful feature? I would be happy to help in implementation.

Thanks, Garrett

What steps will reproduce the problem?

1. Prepare a large json response file
2. Simulate a test suite execution by running the following test (I wrote this in MocoTest class):

@Test
    public void should_return_expected_response_from_a_large_file_and_run_a_new_server_without_exceptions() throws Exception {
        server.response(file("src/test/resources/large.response"));

        running(server, new Runnable() {
            @Override
            public void run() throws IOException {
                assertThat(helper.get(root()), Matchers.notNullValue());
            }
        });
        server = httpserver(port());
        running(server, new Runnable() {
            @Override
            public void run() throws IOException {
                assertThat(helper.get(root()), Matchers.notNullValue());
            }
        });
    }

What is the expected output? What do you see instead? Moco will fail to start on the second attempt

What version of the product are you using? On what operating system? Moco 0.9, Windows

Workaround: We used Awaitility and wrote such piece of code that seems to wait until a port is free and we call after each running method:

await().until(mocoShutsDownCompletelyAtPort(PORT));

private Callable<Boolean> mocoShutsDownCompletelyAtPort(final int port) {
        return new Callable<Boolean>() {
            @Override
            public Boolean call() throws Exception {
                System.out.println("Waiting until port is available");
                String url = "http://localhost:"+ port;

                try {                   
                    final URLConnection connection = new URL(url).openConnection();
                    connection.connect();
                    return true;
                } catch (final MalformedURLException e) {
                    throw new IllegalStateException("Bad URL: " + url, e);
                } catch (final IOException e) {
                    e.printStackTrace();
                    return false;
                } 
            }
        };
    }   

Please provide any additional information below. We have this issue when starting moco server when junit executes a test method in which we start a new Moco server. The problem is such that when we want to start a new server some big portion of data "blocks" still blocks closing of the previous server. We are working also with CXF and we are sending a lot of data so sometimes we see that the connection to Moco has been suddenly shutdown and we have errors like "Unexpected end of file" or sth like "error writting request body".

Currently, when using a file as the source of a request or response, the files are obtained via the java.io.File constructor.

It would be useful if files could be loaded from the classpath to simplify the paths that go into configs. This could be implemented as a new static method on Moco which attempts to load a file using the ClassLoader.

In some scenarios, we need changing the response of an API in runtime. I think there are 2 ways to achieve it.

1. Config response as an array and iterate it
2. Provide an API to toggle it manually

I see below feature on plan page, does it mean the same thing?

• Runtime configuration change

Together with @kurlenda we created a bash script that allows to configure and run Moco server through Groovy script. In addition it downloads groovy if one doesn't have GDK already installed on his drive.

Hi, I really enjoy using Moco, however on my current project we needed HTTPS support, so I tried to put something together. Please let me know, if you think it's good enough to be merged in. If not, I'm happy to change it as necessary.

Thanks!

Hi,

first of all I want to say thaks for such a great tool! We need that in our mock responses are dates for specific periods (for example wee need date in the response which is 2 months from today or 4 months from today), so I have added 2 variable to the templates - "now" and "dateUtils" which can be used in such cases.

Result are with latest version 0.10.1

Why does a HEAD request yield a body?

[
    {
        "request": {
            "uri": {
                "startsWith": "/prefix"
            }
        },
        "response": {
            "text": {
                "template": "${req}"
            },
            "headers": {
                "header": "1.0",
                "Date": "Mon, 02 Mar 2015 21:27:38 GMT"
            }
        }
    }
]

↳ curl -i -X HEAD http://localhost:5001/prefix
HTTP/1.1 200 OK
Date: Mon, 02 Mar 2015 21:27:38 GMT
Content-Length: 165
header: 1.0
Content-Type: text/plain; charset=UTF-8

HTTP Request{uri=/prefix, version=HTTP/1.1, method=HEAD, queries={}, headers={User-Agent=curl/7.37.1, Host=localhost:5001, Accept=*/*, Content-Length=0}, content=}%

Adds a call to get method of Future task so the threads are closed in sync. Resolves issue #71. I have not developed any test because stop method is called several times in tests.

Is it possible to use URL parameters in path and insert them in the response template, as URL queries?

For some mocks, I see the need to insert values coming from the URL path.

For example:

• URI: /v1/test/.*/example
• Request: GET /v1/test/dummy/example
• Response: dummy

Maybe something like the following:

    {
        "request": {
            "uri": {
                "match": "/v1/test/.*/example"
            },
            "method": "get",
        },
        "response": {
            "status": 200,
            "text": {
                "template": "{$req.uri.param[0]}"
            },
            "headers": {
                "Content-Type": "application/json"
            }
        }
    },

Thanks.