Golang Testing

Usually no — not directly in the loop body.

Why: if you call `assert` inside a plain `for` loop, failures are harder to attribute to a specific case, and one bad case can make the output less clear. In Go, the cleaner pattern is table-driven tests with `t.Run(...)` subtests, then do assertions inside each subtest.

Better:

```go
func TestSomething(t *testing.T) {
    tests := []struct {
        name string
        input int
        want  int
    }{
        {"one", 1, 2},
        {"two", 2, 3},
    }

    for _, tt := range tests {
        tt := tt
        t.Run(tt.name, func(t *testing.T) {
            t.Parallel()
            got := doThing(tt.input)
            assert.Equal(t, tt.want, got)
        })
    }
}
```

This gives you:

- isolated failures per case
- better test output
- easier debugging
- optional parallel execution per case

If the loop is not iterating test cases, and you intentionally want multiple soft checks in one test, `assert` can still work — but for table-driven tests, subtests are the preferred approach.