procyberian/emacs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Rewrite ERT manual introduction

Browse source 
* doc/misc/ert.texi (Top): Rewrite for clarity.  Don't give such
prominent mention to to TDD or JUnit, references which now seem dated.
This commit is contained in:
Stefan Kangas 2025-03-09 19:34:00 +01:00
parent b2f124f2a8
commit 7d0d61d854
1 changed files with 10 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

18
doc/misc/ert.texi
View file

@ -46,15 +46,17 @@ modify this GNU manual.''
@insertcopying @insertcopying
ERT is a tool for automated testing in Emacs Lisp. Its main features ERT is a tool for automated testing in Emacs Lisp. Its main features
are facilities for defining tests, running them and reporting the are facilities for defining and running tests, reporting results, and
results, and for debugging test failures interactively. debugging test failures interactively. Tests are written in Emacs Lisp,
just like the code under test, making it easy to write expressive and
concise test cases.
ERT is similar to tools for other environments such as JUnit, but has ERT has unique features that take advantage of the dynamic and
unique features that take advantage of the dynamic and interactive interactive nature of Emacs. It is unopinionated about when or how
nature of Emacs. Despite its name, it works well both for test-driven tests are written: you can use it to verify newly written code,
development (see reproduce known bugs, prevent regressions, or explore the behavior of
@url{https://en.wikipedia.org/wiki/Test-driven_development}) and for complex systems. It can be used for both unit tests and larger
traditional software development methods. integration tests.
@menu @menu
* Introduction:: A simple example of an ERT test. * Introduction:: A simple example of an ERT test.