> There is no place for tests that cannot be automatically run somehow > in our test suite.
O_o Since when? Says who? Surely you care about the pedagogical of doctests? This graph [1] is a counterexample to a conjecture. It was expected to be hamiltonian, and it is not. In the doctest, I says that 'g.is_hamiltonian()' returns False. That's one of the most interesting things that there is to say about this graph, and Sage can solve it. In less than a second with CPLEX, and in >2minutes (still running) with GLPK. > Absolutely any instance of this whatsoever is a > shortcoming in our test suite that we should *plan* to find a way to > address. (I'm of course not saying we should delete/change everything > right now.) > > If you have tests that take too long, then we need another tag "# really > long". > If there are tests that create git branches or have other "undesirable > side effects", then get better at writing tests that properly run in a > sandbox that addresses such side effects. 'get better'?.... I think you need to remember that all of us here are free workers. You are CEO of SageMath, but that's another company. If you are not satisfied with the doctesting framework, come show us that you still know how to write python code. Nathann [1] http://doc.sagemath.org/html/en/reference/graphs/sage/graphs/graph_generators.html#sage.graphs.graph_generators.GraphGenerators.EllinghamHorton78Graph -- 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 post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
