Maybe clean tests

[ringabout]

nim-lang#16096 (comment)
nim-lang#16101 (comment)

• https://github.com/nim-lang/Nim/blob/3e7077ac7d2f4867ecabff09b730b6bc9356979d/tests/stdlib/tunidecode.nim#L12

[timotheecour]

• likewise with move tests to testament nim-lang/Nim#16101:

git diff --color-moved --color-moved-ws=ignore-all-space cbc793b^..cbc793b | grep '\binclude\b'

+include parsecsv
+include stats
+include uri

=> use similar technique to transform those into import

[timotheecour]

• another thing would be a giant s/assert/doAssert/ under tests/ ; curious which cases would need to stay as assert, besides maybe a test that actually tests for assert (eg in tests/assert/tassert.nim or such)
  (refs: misc cleanups timotheecour/Nim#64 (comment))

[ringabout]

• clean unittest style

[timotheecour]

clean unittest style

can you clarify what you mean?
eg,

suite "Bacon":
  test ">:)":
    check(foo == bar)

I'd write it as:

block: # Bacon
  check foo == bar

(but not necessarily doAssert foo == bar)

which adhers to the principle of: "only print something if there's something wrong", unlike suite "Bacon": which outputs [suite] Bacon regardless if test pass/failed, and is more informative than doAssert foo == bar when test fails