- **Base class**: Extend `PlainTestCase` from UTFlute
- **Test Resources**: `src/test/resources/`
- **Coverage Goal**: >80% line coverage

### Contributing

1. Fork repo, create feature branch
2. Make focused commits with tests
3. Format code (`mvn formatter:format && mvn license:format`)
4. Run tests (`mvn test`)
5. Open Pull Request

---

## Quick Reference

### Key File Locations

   *       to make such changes to our serialized forms, and we have made them before, usually
   *       without trouble. In this case, my guess is that our chosen approach is even less likely
   *       to lead to trouble than an incompatible change would be.
   *   <li>We could make {@link #countMap} no longer be {@code final}. Then we could write to it

   * AnnotatedElement}, which {@code TypeVariable} began to extend only in Java 8. Those methods
   * refer only to types present under Android, so we could implement them in {@code
   * TypeVariableImpl} today. (We could probably then make {@code TypeVariableImpl} implement {@code
   * AnnotatedElement} so that we get partial compile-time checking.)
   *
   * <p>This workaround should be removed at a distant future time when <a

        assertTrue(options.plugins().get(), "Long form --plugins option should be true");
    }

    @Test
    void testInvalidCombinationStillParses() throws ParseException {
        // Even if the combination doesn't make logical sense, the CLI should parse it
        String[] args = {"apply", "--all", "--plugins", "--infer"};
        CommonsCliUpgradeOptions options = CommonsCliUpgradeOptions.parse(args);

		t.Fatalf("Count should be 3, but got count: %v err %v", count10, err)
	}

	var count11 int64
	sameUsers := make([]*User, 0)
	for i := 0; i < 3; i++ {
		sameUsers = append(sameUsers, GetUser("count-4", Config{}))
	}
	DB.Create(sameUsers)

# Query Parameters and String Validations { #query-parameters-and-string-validations }

**FastAPI** allows you to declare additional information and validation for your parameters.

Let's take this application as example:

{* ../../docs_src/query_params_str_validations/tutorial001_py310.py hl[7] *}

//
// Very similar to TF_OperationDescription with some differences:
// (1) TF_Output or TFE_TensorHandle* as arguments to TF_AddInput,
//     TF_AddInputList
// (2) TF_ColocateWith, TF_AddControlInput etc. do not make sense.
// (3) Implementation detail: Avoid use of NodeBuilder/NodeDefBuilder since
//     the additional sanity checks there seem unnecessary;
typedef struct TFE_Op TFE_Op;

{* ../../docs_src/body/tutorial001_py310.py hl[5:9] *}


The same as when declaring query parameters, when a model attribute has a default value, it is not required. Otherwise, it is required. Use `None` to make it just optional.

For example, this model above declares a JSON "`object`" (or Python `dict`) like:

```JSON
{
    "name": "Foo",
    "description": "An optional description",
    "price": 45.2,
    "tax": 3.5

echo ""

# Check if the script exists
if [[ ! -f "${GENERATE_THUMBNAIL}" ]]; then
    echo -e "${RED}ERROR: generate-thumbnail script not found at ${GENERATE_THUMBNAIL}${NC}"
    exit 1
fi

# Make sure the script is executable
chmod +x "${GENERATE_THUMBNAIL}"

echo "--- Basic argument tests ---"

# Test: No arguments
run_test "no arguments" 1 "${GENERATE_THUMBNAIL}"

# Test: Empty command type

   *     class under test.
   */
  protected abstract Map<K, V> makeEmptyMap() throws UnsupportedOperationException;

  /**
   * Creates a new, non-empty instance of the class under test.
   *
   * @return a new, non-empty map instance.
   * @throws UnsupportedOperationException if it's not possible to make a non-empty instance of the
   *     class under test.