}

func TestParseLegalHoldStatus(t *testing.T) {
	tests := []struct {
		value          string
		expectedStatus LegalHoldStatus
	}{
		{
			value:          "ON",
			expectedStatus: LegalHoldOn,
		},
		{
			value:          "Off",
			expectedStatus: LegalHoldOff,
		},
		{
			value:          "x",
			expectedStatus: "",
		},
	}

	for _, tt := range tests {
		actualStatus := parseLegalHoldStatus(tt.value)

#!/bin/bash -e

dialects=("sqlite" "mysql" "postgres" "gaussdb" "sqlserver" "tidb")

if [[ $(pwd) == *"gorm/tests"* ]]; then
  cd ..
fi

if [ -d tests ]
then
  cd tests
  go get -u -t ./...
  go mod download
  go mod tidy
  cd ..
fi

# SqlServer for Mac M1
if [[ -z $GITHUB_ACTION && -d tests ]]; then
  cd tests
  if [[ $(uname -a) == *" arm64" ]]; then

check: test
test: verifiers build ## builds minio, runs linters, tests
	@echo "Running unit tests"
	@MINIO_API_REQUESTS_MAX=10000 CGO_ENABLED=0 go test -v -tags kqueue,dev ./...

test-root-disable: install-race
	@echo "Running minio root lockdown tests"
	@env bash $(PWD)/buildscripts/disable-root.sh

test-ilm: install-race
	@echo "Running ILM tests"
	@env bash $(PWD)/docs/bucket/replication/setup_ilm_expiry_replication.sh

///

/// tip

If you want to call `async` functions in your tests apart from sending requests to your FastAPI application (e.g. asynchronous database functions), have a look at the [Async Tests](../advanced/async-tests.md) in the advanced tutorial.

///

## Separating tests { #separating-tests }

In a real application, you probably would have your tests in a different file.

import org.junit.jupiter.api.Test;

/**
 * Tests <code>FarthestConflictResolver</code>.
 *
 * @see FarthestConflictResolver
 */
@Deprecated
class FarthestConflictResolverTest extends AbstractConflictResolverTest {
    // constructors -----------------------------------------------------------

    FarthestConflictResolverTest() throws Exception {
        super("farthest");
    }

import org.junit.jupiter.api.Test;

/**
 * Tests <code>NearestConflictResolver</code>.
 *
 * @see NearestConflictResolver
 */
@Deprecated
class NearestConflictResolverTest extends AbstractConflictResolverTest {
    // constructors -----------------------------------------------------------

    NearestConflictResolverTest() throws Exception {
        super("nearest");
    }

import org.junit.jupiter.api.Test;

/**
 * Tests <code>OldestConflictResolver</code>.
 *
 * @see OldestConflictResolver
 */
@Deprecated
class OldestConflictResolverTest extends AbstractConflictResolverTest {
    // constructors -----------------------------------------------------------

    OldestConflictResolverTest() throws Exception {
        super("oldest");
    }

  might have multiple nodes.
* **`ESRestTestCase`**: An integration tests that interacts with an external
  cluster via the REST API. This is used for Java based REST tests.
* **`ESClientYamlSuiteTestCase` **: A subclass of `ESRestTestCase` used to run
  YAML based REST tests.

=== Good practices

==== What kind of tests should I write?

Unit tests are the preferred way to test some functionality: most of the time

    }

    /**
     * Tests the constructor of {@link TransTransactNamedPipeResponse}.
     */
    @Test
    void testConstructor() {
        // The constructor is called in setUp(), so we just verify the result.
        assertNotNull(response, "The response object should not be null.");
    }

    /**
     * Tests the writeSetupWireFormat method.
     */
    @Test

		{"00000000000000001", 0, "http chunk length too large"}, // could accept if we wanted
	}
	for i := uint64(0); i <= 1234; i++ {
		tests = append(tests, testCase{in: fmt.Sprintf("%x", i), want: i})
	}
	for _, tt := range tests {
		got, err := parseHexUint([]byte(tt.in))
		if tt.wantErr != "" {
			if err != nil && !strings.Contains(err.Error(), tt.wantErr) {