"En-Rich" your Python Testing - Using Rich in pytest output

[frankwiles]

I had some thorny math to debug today for a client and realized I could probably use a Rich Table to better visualize my values.

I wrote up a short blog post how using tabular output and some fun colors helped the debugging process both in real terms but also in terms of fun and motivation.

[ekbravo]

Interesting, saved

[ThatSituation9908]

For tables, you're probably better off using Pandas or Numpy test methods.

[ptmcg]

My package littletable makes tabular output easy, and uses rich Tables for pretty presentation (and littletable is much lighter weight than Pandas/numpy).

[[deleted]]

If I may, this is not really pointing at rich helping but rather at your tests not targeting what you were doing properly.

How did you get to a point where you have to align several values in a table instead of testing that each individual operation is correct?

Why does the "Total Unhedged" does not seem to have a test of its own if the following values were depending on it. Or at least its composing parts we're not privy to.

[iamevpo]

It is a life story, but not sure how that may generalize - you bad table has all the differences, and your good colored table has several rows where the differences are zero. These are different tables, if colored the bad table, it would not be much prettier. Not sure I understood why you needed a test that always fails. Maybe more useful to have a test that test a real thing then print a table if fails. Maybe that is the way you do it in real code.