import java.util.stream.Stream;

import org.apache.maven.api.Lifecycle;
import org.apache.maven.api.annotations.Nonnull;
import org.apache.maven.api.annotations.Nullable;
import org.apache.maven.plugin.MojoExecution;
import org.apache.maven.project.MavenProject;

public class BuildStep {
    public static final int CREATED = 0;
    public static final int PLANNING = 1;
    public static final int SCHEDULED = 2;

Veamos cómo podemos hacer que esto funcione.

## pytest.mark.anyio { #pytest-mark-anyio }

Si queremos llamar funciones asíncronas en nuestros tests, nuestras funciones de test tienen que ser asíncronas. AnyIO proporciona un plugin útil para esto, que nos permite especificar que algunas funciones de test deben ser llamadas de manera asíncrona.

## HTTPX { #httpx }

* Fix issue where on re-registration of device plugin, `allocatable` was not getting updated. This issue makes devices invisible to the Kubelet if device plugin restarts. Only work-around, if this fix is not there, is to restart the kubelet and then start device plugin. ([#63118](https://github.com/kubernetes/kubernetes/pull/63118), [@vikaschoudhary16](https://github.com/vikaschoudhary16))

	}

	_, err := s.adm.SetConfigKV(ctx, strings.Join(configCmds, " "))
	if err != nil {
		c.Fatalf("unable to setup access management plugin for tests: %v", err)
	}

	s.RestartIAMSuite(c)
}

// TestIAM_AMPInternalIDPServerSuite - tests for access management plugin
func TestIAM_AMPInternalIDPServerSuite(t *testing.T) {
	for i, testCase := range iamTestSuites {
		t.Run(

  xml.schemaLocation="https://maven.apache.org/xsd/lifecycle-${version}.xsd">
  <id>lifecycle</id>
  <name>Lifecycle</name>
  <description>
    Configuration of custom lifecycle mappings for the plugin, as generally stored in
    {@code META-INF/maven/lifecycle.xml} in a plugin's jar artifact.
  </description>
  <classes>
    <class rootElement="true" xml.tagName="lifecycles" xsd.compositor="sequence">

Schauen wir uns an, wie wir das machen können.

## pytest.mark.anyio { #pytest-mark-anyio }

Wenn wir in unseren Tests asynchrone Funktionen aufrufen möchten, müssen unsere Testfunktionen asynchron sein. AnyIO stellt hierfür ein nettes Plugin zur Verfügung, mit dem wir festlegen können, dass einige Testfunktionen asynchron aufgerufen werden sollen.

## HTTPX { #httpx }

Let's look at how we can make that work.

## pytest.mark.anyio { #pytest-mark-anyio }

If we want to call asynchronous functions in our tests, our test functions have to be asynchronous. AnyIO provides a neat plugin for this, that allows us to specify that some test functions are to be called asynchronously.

## HTTPX { #httpx }

success.reindex_started=Started re-indexing.
success.bulk_process_started=Started a bulk process.
success.print_thread_dump=Printed a thread dump to a log file.
success.install_plugin=Installing plugin {0}.
success.delete_plugin=Deleting plugin {0}.
success.upload_file_to_storage=Uploaded {0}.
success.sso_logout=You have been logged out.
success.update_storage_tags=Updated tags of {0}.

success.crud_create_crud_table = Created the data.

success.reindex_started=Started re-indexing.
success.bulk_process_started=Started a bulk process.
success.print_thread_dump=Printed a thread dump to a log file.
success.install_plugin=Installing plugin {0}.
success.delete_plugin=Deleting plugin {0}.
success.upload_file_to_storage=Uploaded {0}.
success.sso_logout=You have been logged out.
success.update_storage_tags=Updated tags of {0}.

success.crud_create_crud_table = Created the data.

dependency on elasticsearch will be substituted with the local elasticsearch
build. To add your plugin, create a directory called elasticsearch-extra as
a sibling of elasticsearch. Checkout your plugin underneath elasticsearch-extra
and the build will automatically pick it up. You can verify the plugin is
included as part of the build by checking the projects of the build.