# Test formatting

Use the `--output-comments=<value>` argument to select basic formatting options for tests written by Cover CLI (define the use of the `// Arrange`, `// Act`, and `// Assert` sections and comments).

**Usage:** `--output-comments=<value>`

**Example:** `--output-comments=false`

**Default:** `true`

### Brief

Using `--output-comments=false`, Cover CLI will create tests in a more condensed format - the `// Arrange`, `// Act`, and `// Assert` comments are removed and the sections are inlined:

```java
  @Test
  public void testHasItem() {
    assertFalse((new Order()).hasItem());
  }
```

### Standard

Using `--output-comments=true` (or not specifying the argument at all), the `Arrange`, `Act`, and `Assert` sections will be labelled, but may still be combined together by inlining if they're small, for example:

```java
@Test
public void testHasItem() throws Exception {
  // Arrange and Act
  boolean actual = (new Order()).hasItem();

  // Assert
  assertEquals(false, actual);
}
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://cover-docs-preview.diffblue.com/features/cover-cli/writing-tests/test-formatting.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.