Hi everyone There have been cases with me while solving bugs in SmyPy in certain cases that i feel the need to follow certain rules for writing cases. I think that there are no hard and fast rules to write test cases for everything in genral for `new implementation`(for any software). For example when i made the PR https://github.com/sympy/sympy/pull/10079 for fixing a bug, i think i wrote too many test-cases but i thought it is better to have more test-cases since nothing similar to that was done before in SymPy. But if i write too many test cases i fear that overall time of tests suite would increase(i think that is bad), so i am very concerned about the increasing test-suite testing time . But for bugs solving i feel that every new line has to be tested. My question is: "We as in SymPy, do we follow rules for writing test-case(hard and fast rules)?, for both the new implementation and for bug fixing?"
Even if there is no wiki about that. It would be great if i could have the link to some blog (which is very similar to rules we follow in SymPy). I remeber when Joachim Durcholz(@toolforger) mentioned about that something, writing clever test cases but may be skipping some lines of code from testing. Like on this comment https://github.com/sympy/sympy/issues/9660#issuecomment-120720283 Thanks -- You received this message because you are subscribed to the Google Groups "sympy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sympy+unsubscr...@googlegroups.com. To post to this group, send email to sympy@googlegroups.com. Visit this group at http://groups.google.com/group/sympy. To view this discussion on the web visit https://groups.google.com/d/msgid/sympy/a5ef6de8-1e83-4ea6-bdb6-ec351d9011b9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
