diff options
Diffstat (limited to '2023/talks/test.md')
| -rw-r--r-- | 2023/talks/test.md | 20 |
1 files changed, 10 insertions, 10 deletions
diff --git a/2023/talks/test.md b/2023/talks/test.md index af254a62..1510d167 100644 --- a/2023/talks/test.md +++ b/2023/talks/test.md @@ -38,13 +38,13 @@ I have learned by doing that. makes it become more tests. Codewise you could collect similar tests to one ert-deftest making the name of the test point out some group or collection of functions, but I - don\'t do that! - - I have not studied other packages so I don\'t know how our - test coverage compares to other packages. In fact I don\'t + don't do that! + - I have not studied other packages so I don't know how our + test coverage compares to other packages. In fact I don't know what code coverage we have. That is another thing to look into. -- Q: One small suggestion, to me \'should\' means optional, whereas - \'shall\' or \'must\' means required. Not sure if it is too late to +- Q: One small suggestion, to me 'should' means optional, whereas + 'shall' or 'must' means required. Not sure if it is too late to make a major grammar change like that :) Very nice presentation. (I see :)) - A: The assertions come from the ert package so any changes would @@ -55,7 +55,7 @@ I have learned by doing that. menu: <https://github.com/alphapapa/makem.sh> It also works on remote CI. - A: Thanks for the suggestion. I did have a look at makem.sh but - a long time ago so I don\'t remember why we did not try to apply + a long time ago so I don't remember why we did not try to apply it. I might give it another look now when I have used plain ert more. - Q: Is it easy to run ad hoc tests inside of an Emacs session, given @@ -64,7 +64,7 @@ I have learned by doing that. run them right away? - A: - Yes, in principle you just load your tests and run them all - using \`ert\` and give it the test selector \`t\`. That runs + using `ert` and give it the test selector `t`. That runs all loaded tests. - If you want to modify a test you can do that. You change it, evaluate it, and run it again. Just as you change any @@ -82,12 +82,12 @@ I have learned by doing that. This has not been applied but is something I have been thinking about. With side effects I here mean things like adding or modifying text in buffers. -- Q: What\'s the craziest bug you found when writing these tests? +- Q: What's the craziest bug you found when writing these tests? - A: This is not a bug but I always assumed giving a prefix argument to a cursor movement would give the same result as hitting the key the same amount of times. So like C-u 2 C-f would be the same as hitting the C-f key twise. It is not! When - moving over a hidden area, the three dots \'\...\' at the end of + moving over a hidden area, the three dots '...' at the end of folded line in org-mode or outline-mode, you get different behavior. Trying to write a test case for the kotl-mode and its folded behavior teached me that. @@ -99,7 +99,7 @@ I have learned by doing that. this with cl-letf means the definition becomes longer and more complicated. Sort of blurs the picture. el-mock is more to the point. - - BUT since cl-letf does allow you do define a \"new\" + - BUT since cl-letf does allow you do define a "new" function it is more powerful and it can be the only option in cases where el-mock is too limited. So it is good to know of this possibility with cl-letf when el-mock does not |