|
55 | 55 | <meta itemprop="description" content="Introduction It is likely you experienced the painful situation of deploying to production only to find out that an API service you integrate with has broken the contract. How can we effectively ensure this does not happen?
|
56 | 56 | Microcks offers mocks but can also be used for Contract conformance testing of API or services being under development. You spend a lot of time describing request/response pairs and matching rules: it would be a shame not to use this sample as test cases once the development is on its way!"><meta itemprop="datePublished" content="2019-09-01T00:00:00+00:00" />
|
57 | 57 | <meta itemprop="dateModified" content="2023-06-07T00:00:00+00:00" />
|
58 |
| -<meta itemprop="wordCount" content="1520"> |
| 58 | +<meta itemprop="wordCount" content="1544"> |
59 | 59 | <meta itemprop="keywords" content="" /><meta name="twitter:card" content="summary"/>
|
60 | 60 | <meta name="twitter:title" content="Testing with Microcks"/>
|
61 | 61 | <meta name="twitter:description" content="Introduction It is likely you experienced the painful situation of deploying to production only to find out that an API service you integrate with has broken the contract. How can we effectively ensure this does not happen?
|
@@ -336,9 +336,17 @@ <h5 id="kafka">Kafka</h5>
|
336 | 336 | <td><code>registryAuthCredSource</code></td>
|
337 | 337 | <td>The source for authentication credentials if any. Valid values are just <code>USER_INFO</code>.</td>
|
338 | 338 | </tr>
|
| 339 | +<tr> |
| 340 | +<td><code>startOffset</code></td> |
| 341 | +<td>The topic offset we start consuming mesages at (since version <code>1.8.0</code>)</td> |
| 342 | +</tr> |
| 343 | +<tr> |
| 344 | +<td><code>endOffset</code></td> |
| 345 | +<td>The topic offset we end consuming messages at (since version <code>1.8.0</code>)</td> |
| 346 | +</tr> |
339 | 347 | </tbody>
|
340 | 348 | </table>
|
341 |
| -<p>As an example, you may have this kind of Test Endpoint value: <code>kafka://mybroker.example.com:443/test-topic?registryUrl=https://schema-registry.example.com&registryUsername=fred:letmein&registryAuthCredSource=USER_INFO</code></p> |
| 349 | +<p>As an example, you may have this kind of Test Endpoint value: <code>kafka://mybroker.example.com:443/test-topic?registryUrl=https://schema-registry.example.com&registryUsername=fred:letmein&registryAuthCredSource=USER_INFO&startOffset=28&endOffset=30</code></p> |
342 | 350 | <h5 id="mqtt">MQTT</h5>
|
343 | 351 | <p>MQTT Test Endpoint have the following form with no optional parameters:</p>
|
344 | 352 | <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-sh" data-lang="sh">mqtt://<span class="o">{</span>mqtt.broker.url:port<span class="o">}</span>/<span class="o">{</span>mqtt.topic.name<span class="o">}</span>
|
|
0 commit comments