Timeline for run a single ERT test programmatically
Current License: CC BY-SA 3.0
7 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jun 22, 2016 at 18:03 | comment | added | mutbuerger | You're welcome. IIRC the ert-modeline package got me inspired to look into ERT. In addition, source code is always enlightening. | |
Jun 22, 2016 at 17:54 | comment | added | Kevin |
Sorry, our comments were out of sync. You are exactly right, (ert-test-passed-p ...) was exactly what I was looking for. Thank you again. I wonder why I couldn't find any of this in the manuals or online doc... Did I miss something obvious, or did you find out this info by working with the source code or something?
|
|
Jun 22, 2016 at 16:37 | comment | added | Kevin |
The (ert--stats-passed-expected (ert-run-tests 'my-deftest ..listener)) syntax was closest to answering my question, I think. I can work with it. But I find it quite odd that in order to do something "so simple" as running a single test programmatically, I must call one of the "don't call functions with double hyphens in the name" functions. Thank you again.
|
|
Jun 22, 2016 at 16:35 | comment | added | mutbuerger |
(ert-test-passed-p (ert-run-test (ert-get-test 'ert-test-record-backtrace))) is what you're looking for.
|
|
Jun 22, 2016 at 16:34 | vote | accept | Kevin | ||
Jun 22, 2016 at 16:29 | comment | added | Kevin |
Thank you for your help. With apropos-internal I can see my deftest names, but they are not test objects, since ert-run-test rejects them with wrong type argument errors. I will go an experiment with listeners now, since I've never used them either.
|
|
Jun 22, 2016 at 16:18 | history | answered | mutbuerger | CC BY-SA 3.0 |