unittest: use defines instead of env vars (#16165)

* unittest: use defines instead of env vars

* use defines in testament

* fixup

Co-authored-by: Andreas Rumpf <rumpf_a@web.de>
This commit is contained in:
Timothee Cour 2020-12-09 15:57:52 -08:00 • committed by GitHub
commit 82bb4db4b7
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
6 changed files with 61 additions and 57 deletions

View file

@ -8,4 +8,9 @@ switch("path", "$lib/../testament/lib")
switch("colors", "off")
switch("listFullPaths", "off")
switch("excessiveStackTrace", "off")
# for std/unittest
switch("define", "nimUnittestOutputLevel:PRINT_FAILURES")
switch("define", "nimUnittestColor:off")
switch("define", "nimLegacyTypeMismatch")

View file

@ -1,13 +0,0 @@
discard """
output: '''
[Suite] Bacon
[OK] >:)
'''
"""
import unittest
suite "Bacon":
test ">:)":
check(true == true)

View file

@ -7,12 +7,6 @@ import times, strutils, unittest
when not defined(js):
import os
# Normally testament configures unittest with environment variables,
# but that doesn't work for the JS target. So instead we must set the correct
# settings here.
addOutputFormatter(
newConsoleOutputFormatter(PRINT_FAILURES, colorOutput = false))
proc staticTz(hours, minutes, seconds: int = 0): Timezone {.noSideEffect.} =
let offset = hours * 3600 + minutes * 60 + seconds

View file

@ -19,6 +19,7 @@ discard """
[Suite] test name filtering
'''
targets: "c js"
"""
import unittest, sequtils