The benefit of a dedicated project for these tests are:
- `qa` projects are dedicated two specific usecases and easier to maintain
- It keeps the specific test logic separated from the common test logic.
- You can run those tests in parallel to other projects of the build.

#### Using test fixtures

Sometimes we want to share test fixtures to setup the code under test across multiple projects. There are basically two ways doing so.

minversion = "9.0"
addopts = [
  "--strict-config",
  "--strict-markers",
  "--ignore=docs_src",
]
strict_xfail = true
filterwarnings = [
    "error",
]
timeout = "20"

[tool.coverage.run]
parallel = true
data_file = "coverage/.coverage"
source = [
    "docs_src",
    "tests",
    "fastapi"
]
relative_files = true
context = '${CONTEXT}'
omit = [
    "tests/benchmarks/*",

## Recap { #recap }

You can use multiple worker processes with the `--workers` CLI option with the `fastapi` or `uvicorn` commands to take advantage of **multi-core CPUs**, to run **multiple processes in parallel**.

You could use these tools and ideas if you are setting up **your own deployment system** while taking care of the other deployment concepts yourself.

  annotations: {{- toYaml .Values.additionalAnnotations | nindent 4 }}
  {{- end }}
spec:
  updateStrategy:
    type: {{ .Values.statefulSetUpdate.updateStrategy }}
  podManagementPolicy: "Parallel"
  serviceName: {{ template "minio.fullname" . }}-svc
  replicas: {{ $replicas }}
  selector:
    matchLabels:
      app: {{ template "minio.name" . }}
      release: {{ .Release.Name }}
  template:
    metadata:

            final long elapsed = System.currentTimeMillis() - startTime;

            assertNotNull(results);
            // Verify it doesn't take too long (parallel execution should help)
            assertTrue("Search took too long: " + elapsed + "ms", elapsed < 5000);
        }
    }

    /**
     * Searcher that throws an exception during search.
     */

Since HTTP requests frequently happen in parallel, connection pooling must be thread-safe.

These are the primary classes involved with establishing, sharing, and terminating connections:

      public boolean isDirected() {
        return AbstractBaseGraph.this.isDirected();
      }

      @Override
      public boolean allowsParallelEdges() {
        return false; // Graph doesn't allow parallel edges
      }

      @Override
      public boolean allowsSelfLoops() {
        return AbstractBaseGraph.this.allowsSelfLoops();
      }

      @Override
      public ElementOrder<N> nodeOrder() {

    }

    /**
     * @return True if the <code>Mojo</code> is thread-safe and can be run safely in parallel
     * @since 3.0-beta-2
     */
    public boolean isThreadSafe() {
        return threadSafe;
    }

    /**
     * @param threadSafe indicates that the mojo is thread-safe and can be run safely in parallel
     * @since 3.0-beta-2
     */
    public void setThreadSafe(boolean threadSafe) {

 * their build lifecycle, ensuring thread-safety and proper state management.
 * All implementations must be thread-safe as they may be accessed concurrently
 * during parallel builds.
 *
 * @since 4.0.0
 * @see org.apache.maven.api.services.ProjectBuilder
 * @see Project
 */
@Experimental
public interface ProjectManager extends Service {
    /**

                    ),
                functionalTests =
                    listOf(
                        TestCoverage(
                            7,
                            TestType.PARALLEL,
                            Os.LINUX,
                            JvmCategory.MAX_LTS_VERSION,
                            DEFAULT_LINUX_FUNCTIONAL_TEST_BUCKET_SIZE,
                        ),