## Tests

There is a script that you can run locally to test all the code and generate coverage reports in HTML:

<div class="termy">

```console
$ bash scripts/test-cov-html.sh
```

</div>

This command generates a directory `./htmlcov/`, if you open the file `./htmlcov/index.html` in your browser, you can explore interactively the regions of code that are covered by the tests, and notice if there is any region missing.

## Docs

            "The TID specified was invalid.", "The handle is invalid.", "The network name cannot be found.",
            "Not enough storage is available to process this command.", "The media is write protected.", "The device is not ready.",
            "A device attached to the system is not functioning.", "A device attached to the system is not functioning.",

		return "float constant"
	case scanner.Char:
		return "rune constant"
	case scanner.String:
		return "string constant"
	case scanner.RawString:
		return "raw string constant"
	case scanner.Comment:
		return "comment"
	default:
		return fmt.Sprintf("%q", rune(t))
	}
}

// NewLexer returns a lexer for the named file and the given link context.
func NewLexer(name string) TokenReader {
	input := NewInput(name)

    }

    @Test
    public void test_constructor() {
        // Test that constructor creates a valid instance
        MatchAllQueryCommand command = new MatchAllQueryCommand();
        assertNotNull(command);
    }

    @Test
    public void test_execute_logOutput() {
        // Test that execute method logs debug output when debug is enabled

import org.codelibs.fess.util.ComponentUtil;
import org.lastaflute.core.message.UserMessages;
import org.opensearch.index.query.QueryBuilder;
import org.opensearch.index.query.QueryBuilders;

/**
 * Query command for handling wildcard queries.
 * Converts Lucene WildcardQuery objects to OpenSearch QueryBuilder objects,
 * supporting wildcard pattern matching with configurable case sensitivity.
 */

         */
        SYSTEM_PROPERTIES,
        /**
         * Maven user properties. These are properties that users configure through various means such as
         * maven-user.properties files, maven.config files, command line parameters (-D flags), settings.xml,
         * or environment variables. They are evaluated during the build process and represent the primary
         * way for users to customize Maven's behavior at runtime.
         */

 */

package com.google.common.util.concurrent;

import static com.google.common.truth.Truth.assertThat;
import static com.google.common.util.concurrent.MoreExecutors.directExecutor;
import static java.util.concurrent.TimeUnit.MILLISECONDS;
import static org.junit.Assert.assertThrows;

import com.google.common.annotations.GwtIncompatible;
import com.google.common.annotations.J2ktIncompatible;
import java.util.ArrayList;

    /**
     * Gets the user properties to use for interpolation and profile activation. The user properties have been
     * configured directly by the user on his discretion, e.g. via the {@code -Dkey=value} parameter on the command
     * line.
     *
     * @return The user properties, never {@code null}.
     */
    Properties getUserProperties();

    /**

      {{- end }}
      containers:
        - name: {{ .Chart.Name }}
          image: "{{ .Values.image.repository }}:{{ .Values.image.tag }}"
          imagePullPolicy: {{ .Values.image.pullPolicy }}
          command:
            - "/bin/sh"
            - "-ce"

Transition tiers can be added to MinIO using `mc admin tier add` command to associate a `gcs`, `s3` or `azure` bucket or prefix path on a bucket to the tier name.