From ca0be8ab8aa788b2358d9d46e986ab72bf5300cd Mon Sep 17 00:00:00 2001 From: Stefan Kangas Date: Sun, 9 Mar 2025 19:34:00 +0100 Subject: [PATCH] Rewrite ERT manual introduction * doc/misc/ert.texi (Top): Rewrite for clarity. Don't give such prominent mention to to TDD or JUnit, references which now seem dated. (cherry picked from commit 7d0d61d8549904f460c5711b93ed359f853fb4c3) --- doc/misc/ert.texi | 20 +++++++++++--------- 1 file changed, 11 insertions(+), 9 deletions(-) diff --git a/doc/misc/ert.texi b/doc/misc/ert.texi index 93f4a58de86..f6a90931812 100644 --- a/doc/misc/ert.texi +++ b/doc/misc/ert.texi @@ -46,15 +46,17 @@ modify this GNU manual.'' @insertcopying ERT is a tool for automated testing in Emacs Lisp. Its main features -are facilities for defining tests, running them and reporting the -results, and for debugging test failures interactively. - -ERT is similar to tools for other environments such as JUnit, but has -unique features that take advantage of the dynamic and interactive -nature of Emacs. Despite its name, it works well both for test-driven -development (see -@url{https://en.wikipedia.org/wiki/Test-driven_development}) and for -traditional software development methods. +are facilities for defining and running tests, reporting results, and +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 has unique features that take advantage of the dynamic and +interactive nature of Emacs. It is unopinionated about when or how +tests are written: you can use it to verify newly written code, +reproduce known bugs, prevent regressions, or explore the behavior of +complex systems. It can be used for both unit tests and larger +integration tests. @menu * Introduction:: A simple example of an ERT test. -- 2.39.5