Thanks for the quick answers. It's good to know that sage does have a distinction between classical doctests and unit tests. Is there a deeper reason than tradition that the latter is implemented as doc tests using TESTS, instead of more conventional approaches using pytest or nose? Refs https://trac.sagemath.org/ticket/28936
On Friday, September 4, 2020 at 7:30:53 PM UTC+2 Matthias Koeppe wrote: > On Friday, September 4, 2020 at 7:02:27 AM UTC-7, tobia...@gmx.de wrote: > >> I noticed that there are a lot of doctests in the existing code that test >> rather elementary things. These are often not utterly important for a user >> of the method, but are rather unit tests that verify the correct behavior >> in some edge case. [...] >> > > Just a quick note that in addition to the doctests, Sage also uses > _test... methods, which are defined in abstract base classes to test that > subclasses implement the protocol correctly. > > https://doc.sagemath.org/html/en/reference/misc/sage/misc/sage_unittest.html > > > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/c3e02a0b-65fc-4d87-85a3-ad50551c70afn%40googlegroups.com.
