On Fri, 2022-02-25 at 09:26 -0800, 'Markus Zimmermann' via golang-nuts wrote: > Would appreciate your feedback on the style and extension. Would be > also interesting to hear other approaches and conventions that could > help others to write better tests.
I'm struggling to understand how you capture stack traces that are meaningful to the tested code in any general kind of way — ignoring for a moment the reduced utility of stack traces in concurrent code. Surely you get stack traces for the assertion, by which time the interesting code has passed. Are you doing more than that? -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/fa6bdd0efd62787d01b2776916f2c4ea8c5d6554.camel%40kortschak.io.
