) {
            assertHasNoError()
            assertHasWarnings(
                "Method com.example.Source.foo(java.lang.String): Return nullability changed from null-unmarked to non-nullable",
                "Method com.example.Source.baz(java.lang.String): Return nullability changed from null-unmarked to non-nullable",
            )
            assertHasNoInformation()
        }
    }

    @Test

        // Execute
        String result = pingSearchEngineJob.execute();

        // Assert
        assertEquals("Status of test-cluster is changed to GREEN.", result);
    }

    // Test normal operation with YELLOW status and no state change
    @Test
    public void test_execute_yellowStatusNoChange() {
        // Setup mock components
        SearchEngineClient searchEngineClient = new SearchEngineClient() {

    public void test_changePassword_success() {
        // Test successful password change when LDAP admin sync is disabled
        testLdapManager.changePasswordResult = true;
        testFessConfig.ldapAdminSyncPassword = false;

        boolean result = ldapChain.changePassword("testuser", "newpassword");

        assertFalse(result); // returns !changed || syncPassword = !true || false = false

ppc64 require // 16 byte alignment of the data. To avoid that // requirement, data is loaded using LXVD2X and // STXVD2X with VPERM to reorder bytes correctly. // I have identified some areas where I believe // changes would be needed to make this work for big // endian; however additional changes beyond what I // have noted are most likely needed to make it work. // - The string used with VPERM to swap the byte order // for loads and stores. // - The constants that are loaded from CPOOL. // // The following...

	}

	// Code not changed, price should not change
	DB.Model(&product).Updates(map[string]interface{}{"Name": "Product New"})

	if product.Name != "Product New" || product.Price != 160 || product.Code != "L1212" {
		t.Errorf("invalid data after update, got %+v", product)
	}

	// Code changed, but not selected, price should not change

Pydantic has an official [Migration Guide](https://docs.pydantic.dev/latest/migration/) from v1 to v2.

It also includes what has changed, how validations are now more correct and strict, possible caveats, etc.

You can read it to understand better what has changed.

## Tests { #tests }

Make sure you have [tests](../tutorial/testing.md) for your app and you run them on continuous integration (CI).

- Root credentials can now be changed easily. Before, a two-step process was required to
   change the cluster root credentials since they were used to en/decrypt the IAM data.
   So, both - the old and new credentials - had to be present at the same time during a rotation
   and the old credentials had to be removed once the rotation completed. This process is now gone.
   The root credentials can now be changed easily.

        if (!(member instanceof JApiClass)) {
            return null
        }

        if (!changed(member)) {
            return null
        }

        Optional<CtClass> oldClass = member.oldClass
        Optional<CtClass> newClass = member.newClass
        if (!oldClass.isPresent() || !newClass.isPresent()) {
            // breaking change would be reported
            return null
        }

    }

    // Test expiry setter with zero value (should not change)
    @Test
    public void test_expiry_zeroValue() {
        long originalExpiry = purgeThumbnailJob.getExpiry();
        PurgeThumbnailJob result = purgeThumbnailJob.expiry(0);

        // Test method chaining
        assertSame(purgeThumbnailJob, result);
        // Test value was not changed
        assertEquals(originalExpiry, purgeThumbnailJob.getExpiry());

          <name>configuration</name>
          <description>The place and syntax used to change the value of this expression.</description>
          <type>String</type>
        </field>
        <field>
          <version>1.0.0</version>
          <name>cliOptions</name>
          <description>The command-line switches used to change the value of this expression.</description>
          <type>Properties</type>