EUnit best practices?

[Ryan Zezeski]

Is it a code smell to write a test function that has the following form?

test_foo() ->
  Stuff = make_stuff(),
  {ok, ...} = Stuff, % match some stuff
  ?assert(...),
  ?assert(...),
  ...
  ?assert(...).

Specifically, I'm curious if it's non-idiomatic to call multiple asserts in
a "simple test function?"  Should I be using a "test generating function?"
 If so, why?  What advantages does it offer me over the above?

-Ryan