First change for github.com/stretchr/testify has been pushed as a PR https://github.com/stretchr/testify/pull/1161: "Include locations of subtests in test failure stack traces". Please give your emoji-support if you agree that this is a good behavior change.
More open source changes are coming. Takes some time because we need to alternate between product work. On Friday, 25 February 2022 at 19:48:19 UTC+1 Markus Zimmermann wrote: > Hi Gophers! > > We were unhappy with the common unit test styles and we think we found a > style that has clear advantages. An in-depth comparison can be found here > https://symflower.com/en/company/blog/2022/better-table-driven-testing. > > We also added support for maintaining such tests in our VS Code extension > https://marketplace.visualstudio.com/items?itemName=symflower.symflower. > You can either use the command or the context menu item to maintain tests. > Here is a short introduction video > https://www.youtube.com/watch?v=mgWLY9DDyDE&ab_channel=Symflower > > There are some changes necessary to have better stack traces for > github.com/stretchr/testify because "t.Run" calls the test function from > another location. We are in the process of upstreaming them. Until then you > can find them in our fork at https://github.com/symflower/testify. > > 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. > > Cheers, > Markus > -- 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/dadfaff4-fb49-4953-80df-075f923c9032n%40googlegroups.com.
