"We expected the release transformation and got " + tms.get(0));

        assertTrue(
                tms.get(1) instanceof LatestArtifactTransformation,
                "We expected the latest transformation and got " + tms.get(1));

        assertTrue(
                tms.get(2) instanceof SnapshotTransformation,
                "We expected the snapshot transformation and got " + tms.get(2));
    }

        }

        @Test
        @DisplayName("DcerpcBind should have access to parent class methods")
        void testParentClassMethods() {
            // When/Then
            assertDoesNotThrow(() -> {
                bind.getPtype();
                bind.getFlags();
            }, "Should have access to parent class methods");
        }

        @Test

# スキーマの追加 - 例

JSON Schemaに追加する情報を定義することができます。

一般的なユースケースはこのドキュメントで示されているように`example`を追加することです。

JSON Schemaの追加情報を宣言する方法はいくつかあります。

## Pydanticの`schema_extra`

<a href="https://docs.pydantic.dev/latest/concepts/json_schema/#schema-customization" class="external-link" target="_blank">Pydanticのドキュメント: スキーマのカスタマイズ</a>で説明されているように、`Config`と`schema_extra`を使ってPydanticモデルの例を宣言することができます:

If you can use the **latest versions of Python**, use the examples for the latest version, those will have the **best and simplest syntax**, for example, "**Python 3.10+**".

#### List { #list }

For example, let's define a variable to be a `list` of `str`.

        assertEquals("GET", data.getMethod());

        data.setMethod("POST");
        assertEquals("POST", data.getMethod());
    }

    public void test_parentUrlGetterSetter() {
        // Test parent URL getter/setter
        ResponseData data = new ResponseData();

        String parentUrl = "https://example.com";
        data.setParentUrl(parentUrl);
        assertEquals(parentUrl, data.getParentUrl());
    }

        void testAsServerMessageBlock2Response() {
            // Verify inheritance
            assertTrue(response instanceof ServerMessageBlock2);

            // Verify command can be retrieved from parent
            assertEquals(0, response.getCommand());
        }

        @Test
        @DisplayName("Should work with different buffer sizes")

    <class>
      <name>Activation</name>
      <version>1.0.0</version>
      <description><![CDATA[
        The conditions within the build runtime environment which will trigger
        the automatic inclusion of the parent build profile.
      ]]></description>
      <fields>
        <field>
          <name>activeByDefault</name>
          <version>1.0.0</version>
          <type>boolean</type>

                    session,
                    pluginArtifact,
                    "Plugin should declare Maven artifacts in `provided` scope. If the plugin already declares them in `provided` scope, update the maven-plugin-plugin to latest version. Artifacts found with wrong scope: "
                            + mavenArtifacts);
        }
    }

     * Returns an empty list if no crawling information is found for the session.
     *
     * @param sessionId the session identifier to find the latest crawling parameters for
     * @return a list of CrawlingInfoParam entities from the latest session, or empty list if none found
     */
    public List<CrawlingInfoParam> getLastCrawlingInfoParamList(final String sessionId) {

	exit 1
fi

## Check if latest updated rules get replicated to all sites post re-enable of ILM expiry rules replication
sleep 30s
count1=$(./mc ilm rule list sitea/bucket --json | jq '.config.Rules[0].Expiration.Days')
count2=$(./mc ilm rule list siteb/bucket --json | jq '.config.Rules[0].Expiration.Days')
if [ $count1 -ne 888 ]; then
	echo "BUG: Latest expiration days not updated on 'sitea'"
	exit 1
fi