expanded_policy_count=$(./mc admin policy list myminio/ | wc -l)

if [ $user_count -ne $expanded_user_count ]; then
	echo "BUG: original user count differs from expanded setup"
	exit 1
fi

if [ $policy_count -ne $expanded_policy_count ]; then
	echo "BUG: original policy count  differs from expanded setup"
	exit 1
fi

./mc version info myminio/versioned | grep -q "versioning is enabled"
ret=$?
if [ $ret -ne 0 ]; then

 * <p>
 * This class is immutable and thread-safe, suitable for use in concurrent operations.
 *
 * @param <REQ> The type of the request
 * @param <REP> The type of the response, which must extend {@code Result<REQ>}
 * @param request The original request that was processed
 * @param result The result of the request, if successful; may be null if an error occurred

used to test the individual components in the lifecycle with data that has expected characteristics
and can be asserted as desired.

You can change/extend these stubs, and tests should not be breaking too much, since most tests
assert using expected values from the stubs. Normally, when you try to use data from the stubs that

	VPAND X11, X9, X11                      // c44131dbdb
	VPAND (BX), Y15, Y2                     // c4e105db13 or c585db13
	VPAND (R11), Y15, Y2                    // c4c105db13
	VPAND Y2, Y15, Y2                       // c4e105dbd2 or c585dbd2
	VPAND Y11, Y15, Y2                      // c4c105dbd3
	VPAND (BX), Y15, Y11                    // c46105db1b or c505db1b

 * }</pre>
 *
 * <h2>Extension Points</h2>
 *
 * <p>To add new upgrade strategies:</p>
 * <ol>
 *   <li>Implement {@link org.apache.maven.cling.invoker.mvnup.goals.UpgradeStrategy}</li>
 *   <li>Optionally extend {@link org.apache.maven.cling.invoker.mvnup.goals.AbstractUpgradeStrategy}</li>
 *   <li>Annotate with {@code @Named} and {@code @Singleton}</li>
 *   <li>Use {@code @Priority} to control execution order</li>
 * </ol>
 *

expanded_policy_count=$(./mc admin policy list myminio/ | wc -l)

if [ "$user_count" -ne "$expanded_user_count" ]; then
	echo "BUG: original user count differs from expanded setup"
	exit 1
fi

if [ "$policy_count" -ne "$expanded_policy_count" ]; then
	echo "BUG: original policy count  differs from expanded setup"
	exit 1
fi

./mc version info myminio/versioned | grep -q "versioning is enabled"
ret=$?
if [ $ret -ne 0 ]; then

{* ../../docs_src/app_testing/app_a_py39/test_main.py hl[3] *}


...and have the code for the tests just like before.

## Testing: extended example { #testing-extended-example }

Now let's extend this example and add more details to see how to test different parts.

### Extended **FastAPI** app file { #extended-fastapi-app-file }

Let's continue with the same file structure as before:

```
.

 * specific language governing permissions and limitations
 * under the License.
 */
package org.apache.maven.repository.internal.artifact;

/**
 * The keys for Maven specific properties of artifacts. These properties "extend" (or supplement) the Resolver
 * core properties defined in {@link org.eclipse.aether.artifact.ArtifactProperties}.
 *
 * @see org.eclipse.aether.artifact.ArtifactProperties
 * @since 4.0.0

            // The actual logic is tested in AbstractUpgradeGoalTest
            // Here we just verify that Check is properly configured as a subclass
            assertTrue(checkGoal instanceof AbstractUpgradeGoal, "Check should extend AbstractUpgradeGoal");
            assertFalse(checkGoal.shouldSaveModifications(), "Check should not save modifications unlike Apply goal");
        }
    }

	Include                               // included file started here
	BuildComment                          // //go:build or +build comment
	macroName                             // name of macro that should not be expanded
)

// IsRegisterShift reports whether the token is one of the ARM register shift operators.
func IsRegisterShift(r ScanToken) bool {
	return ROT <= r && r <= LSH // Order looks backwards because these are negative.
}