Francesco Banconi

Closed by the merged pull request that implements the new API. But it's fair that this can be used for further v2 API discussion.

`v2` for quicktest is essentially https://github.com/go-quicktest/qt That includes an API redesign that takes advantage of compile time checks thanks to Go generics. As no backward compatible constraints are in place,...

@dnephin very interesting, thanks for pointing us to that!

This looks great! It would be nice to try to improve how the strategy is provided. One option is to make `Eventually` return a concrete type implementing `Checker` (rather than...

Conversation started at https://github.com/frankban/quicktest/pull/96

Closing for grouping all the `qt` related considerations at https://github.com/go-quicktest/qt/issues/7

Yes, that was an intentional design decision. When you read `qt.Assert(t, x, qt.Equals, "foo", qt.Commentf("bar"))` it is very apparent what args are part of the check and what is a...

Yes, and I think we are now using the concept of wallet.

Good catch! We should not show that as a link before the charm is actually exposed. Thanks.

Note: this requires us to register and keep track of whether the app is exposed in Juju even after a change has been made but not committed by a GUI...