Asset a specific message when multiple messages flowing through the brokers or topics

Created from #220

2. When testing in real environment, there will be multiple messages flowing through the brokers/topics. How can zerocode validate/asset a specific response? Ans: Use Json Path to look for a perticular message or a record key or value. Very easy! e.g.

When you have consume multiple records from a topic, that means you receive an array of records as the response. Then you can assert this way explained in the readme-file.

Where is this JSON path is applied ? In JUNIT or within Zerocode JSON config ?

For example, my test below keeps on failing. In the log, instead of just consuming the messages with the ids I have specified below. It consumes the whole array of 10 messages.

{
    "scenarioName": "consume a JSON message with id_5 & id_9 out of 10 messages produced on topic_A",
    "steps": [

        {
            "name": "consume_step",
            "url": "kafka-topic:topic_A",
            "operation": "consume",
            "request": {
                "consumerLocalConfigs": {
                    "recordType": "JSON",
                    "commitSync": true,
                    "showRecordsConsumed": true,
                    "maxNoOfRetryPollsOrTimeouts": 3
                }
            },
            "assertions": {
                "records": [
                    {
                        "key": "id_5",
                        "value": {

                            "TEST": "Test Val0"
                        }
                    },
                    {
                        "key": "id_9",
                        "value": {

                            "TEST": "Test Val9"
                        }
                    }
                ]
            }
        }
    ]
}

[tghani93]

@authorjapps , very grateful for your responses and pointers. Will have keep you posted on the blog! 😃

[authorjapps]

Yes secure APIs as you mentioned and in general as well 😃 I am planning on doing a blog about Zerocode also, so wanted to obtain a deeper understanding as well.

That sounds cool. 👍

• For Oauth2 one of our contributor(and user) has shared a very short and precise blog in the DZone Security Zone. I am tagging him(@santhoshTpixler ) here in case you need more details on this.

• For Corporate Proxy configuration, you can follow the README section here

  • This is for any Http api invocation, for instance REST, SOAP etc

• SAML/JWT are very straight forward - working examples are here - HelloWorld repo

• If tokens are dynamic, it’s still easy to inject them into header in runtime.

  • @santhoshTpixler has explained in his blog

• If you use OpenAM or RedHat SSO or Simple Basic Auth

  • You can refer the examples in readme-file here
  • You can manually use per test-case wise or embed it to the HttpClient which is oneoff( and less maintenance overhead)

• Zerocode’s Http Client supports Http and Https connections anyways.

  • But you can override and add/remove security features to match your project requirement.
  • See example here - in HelloWorld

    @Override
    public CloseableHttpClient createHttpClient() throws NoSuchAlgorithmException, KeyManagementException, KeyStoreException {
        LOGGER.info("###Used SSL Enabled Http Client for http/https/TLS connections");

       // Add your own security flavour and return the client, 
       // then all test-cases will start using this client.
       // That's it really!

        return HttpClients.custom()
                .setSSLContext(sslContext)
                .setSSLHostnameVerifier(new NoopHostnameVerifier())
                .setDefaultCookieStore(cookieStore)
                .build();
    }

• Then it’s very simple and straight forward to use like below-

Just annotate your test class or suite class.

@UseHttpClient(CustomHttpClient.class)

• In similar fashion, you can inject any custom headers you need. Explained here e.g.

    @Override
    public Map<String, Object> amendRequestHeaders(Map<String, Object> headers) {
        // ----------------------------------------------------
        // Add your custom headers here(if any).
        // e.g. Your auth tokens, client_id or client_secret etc
        // ----------------------------------------------------
        if (headers != null) {
            addCustomHeaders(headers);
        } else {
            headers = new HashMap<>();
            addCustomHeaders(headers);
        }

        return headers;
    }