void ensureDFSResolvedDelegates() throws Exception {
        // Confirms DFS resolution is delegated with the correct locator
        // Act
        handle.ensureDFSResolved();
        // Assert & interaction verify
        verify(treeConnection).ensureDFSResolved(resourceLoc);
    }

    @Test
    @DisplayName("hasCapability delegates and propagates exceptions")
    void hasCapabilityDelegates() throws Exception {

![Swagger UI interaction](https://fastapi.tiangolo.com/img/index/index-04-swagger-03.png)

- তারপরে "Execute" বাটনে চাপুন, ব্যবহারকারীর ইন্টারফেস আপনার API এর সাথে যোগাযোগ করবে, পেরামিটার পাঠাবে, ফলাফলগুলি পাবে এবং সেগুলি পর্রদায় দেখাবে:

![Swagger UI interaction](https://fastapi.tiangolo.com/img/index/index-05-swagger-04.png)

### বিকল্প API নির্দেশিকা নথি আপগ্রেড

    // Attribute
    // =========
    /** The search helper for performing search operations. */
    @Resource
    protected SearchHelper searchHelper;

    /** The search engine client for interacting with OpenSearch. */
    @Resource
    protected SearchEngineClient searchEngineClient;

    // ===================================================================================

- "Try it out"ボタンをクリックしてください。パラメータを入力して API と直接やりとりすることができます:

![Swagger UI interaction](https://fastapi.tiangolo.com/img/index/index-04-swagger-03.png)

- それから、"Execute" ボタンをクリックしてください。 ユーザーインターフェースは API と通信し、パラメータを送信し、結果を取得して画面に表示します:

![Swagger UI interaction](https://fastapi.tiangolo.com/img/index/index-05-swagger-04.png)

### 代替の API ドキュメントのアップグレード

```

## Testing Strategy

### Unit Tests
- Individual component testing for each feature
- Mock-based testing for protocol interactions
- State machine validation

### Integration Tests
- Feature interaction testing
- Network failure simulation
- Performance benchmarking
- Compatibility testing with Windows Server 2016/2019/2022

### Test Infrastructure Requirements
- Windows Server test environment with:

    * Générant automatiquement des **erreurs** renvoyées au client quand la donnée est invalide.
* **Documenter** l'API avec OpenAPI :
    * ce qui ensuite utilisé par les interfaces utilisateur automatiques de documentation interactive.

Tout cela peut paraître bien abstrait, mais ne vous inquiétez pas, vous verrez tout ça en pratique dans [Tutoriel - Guide utilisateur](tutorial/index.md){.internal-link target=_blank}.

// Use of this source code is governed by a BSD-style
// license that can be found in the LICENSE file.

// This file encapsulates some of the odd characteristics of the ARM64
// instruction set, to minimize its interaction with the core of the
// assembler.

package arch

import (
	"cmd/internal/obj"
	"cmd/internal/obj/arm64"
	"errors"
)

var arm64LS = map[string]uint8{
	"P": arm64.C_XPOST,
	"W": arm64.C_XPRE,

}
```

/// tip

To declare a query parameter with a type of `list`, like in the example above, you need to explicitly use `Query`, otherwise it would be interpreted as a request body.

///

The interactive API docs will update accordingly, to allow multiple values:

<img src="/img/tutorial/query-params-str-validations/image02.png">

When you see the automatic docs, you can check that the input model and output model will both have their own JSON Schema:

<img src="/img/tutorial/response-model/image01.png">

And both models will be used for the interactive API documentation:

<img src="/img/tutorial/response-model/image02.png">

## Other Return Type Annotations { #other-return-type-annotations }

        assertEquals("Domain Users", s2.getAccountName());
        assertEquals("TESTDOM", s2.getDomainName());
        assertEquals(jcifs.SID.SID_TYPE_DOM_GRP, s2.getType());

        // Interaction: sendrecv invoked exactly once
        verify(handle, times(1)).sendrecv(any(jcifs.dcerpc.msrpc.MsrpcLookupSids.class));
    }

    @ParameterizedTest