Mirror of forum.nim-lang.org

7544 :: Can't give testament compiler switches when running a pattern

• halloleo (orginal) [2021-02-22T07:00:22+01:00] view original

  I'm starting out with testament.

  (1) At the beginning I got always reNimcCrash errros and from Testament failure with reNimcCrash - Nim forum I learned that I need to enable verbosity (whioch I have set to 0 in my user nim config). So now I do:

  
  $ testament  r test_wordCrunch.nim --verbosity:1
  Run

  This works. :-) However when trying the same with a pattern:

  
  $ testament pat "tests/test*.nim" --verbosity:1
  Run

  I get a no tests were found for pattern: verbosity error message.

  So, how can I specify the verbosity for tests given by pattern?

  ---

  (2) Also, I tried

  
  testament all ...
  Run

  but this seem to run completely different tests (maybe for the compiler?). How can I tell etstament that all etsts mean my tests? %-)

---

• Clonk (orginal) [2021-02-22T08:43:35+01:00] view original

  I recommend creatings a config.nims file in the folder tests that contains

  
  when defined(testing) :
     # your testament option here
    switch("verbosity", "1")
    switch("hints", "on")
  Run

  It's just more practical than having to remember all the command line parameters.

---

• Araq (orginal) [2021-02-22T15:06:30+01:00] view original

  You raise good points and we'll improve testament further.

---

• halloleo (orginal) [2021-02-23T07:01:59+01:00] view original

  Makes sense. But who is reading the config.nims file?

  Looking at Configuration Files in the Nim User Guide I only find config files like nim.cfg and myfile.nim.cfg.

  Is it something testament specific?

---

• shirleyquirk (orginal) [2021-02-23T08:29:27+01:00] view original

  it's documented here but you're right that should be mentioned under configuration files too

---